Unchanged Is the Problem: The DAO's Removal Right Sits in Articles It May Not Amend (s.10) and Cannot Enforce as a Beneficiary (s.7(4)(e))

**What this is, and is not.** This is not an argument that the Foundation should stay weak, nor a claim that anyone intends to strip the DAO of its removal power. It is narrower and, I think, harder to answer. The temp check hands the Foundation the treasury and keeps for tokenholders exactly one legal hook: the power to appoint and remove directors. It then locates that hook in a document it declines to touch. Read against the statute that governs that document, the single retained power is defeasible by an instrument the DAO has not been shown to control, and enforceable — on the Act's default — only by persons the DAO is not. The word doing the damage is "unchanged." **The sentence the whole delegation rests on.** As rendered in the forum temp check (t/22175, read 2026-08-08): "Director appointment, term renewal, and removal also remain with tokenholders, under the Foundation's Articles of Association, unchanged by this proposal." Everywhere else the proposal gives the board mission, trademarks, grants and treasury custody. This is the counterweight. So its strength is not a detail; it is the whole reversibility case. Note precisely where the drafters placed the hook: in the **Articles**, not the memorandum. That placement decides which statute applies, and I read the statute verbatim before arguing from it. **Step one — Section 10 controls who may rewrite the removal clause.** The ENS Foundation is a Cayman foundation company under the Foundation Companies Act (Law 29 of 2017; I quote the 2025 Revision, section text unchanged). Section 10, in full: "A foundation company's articles can only be altered if and to the extent authorised under its constitution, or by an order under Part 5." That is the entire section. The removal right lives in the Articles; s.10 therefore tells us that whoever the *constitution* names as holder of the alteration power can alter — or delete — the removal clause. The temp check does not say the DAO holds that power. It says the Articles are "unchanged," which is precisely the exposure: the one instrument that would have to reserve alteration of the removal clause to a passed DAO vote is the instrument left untouched. **Step two — the Articles carry no default entrenchment; nothing protects the clause unless drafted to.** Here is the correction to an earlier version of this reading, and it strengthens the finding rather than weakening it. The self-entrenchment safeguard — "unless expressed to do so, a provision of the memorandum authorising an alteration does not authorise an alteration of the provision itself" — is s.9(2)(b), and s.9 is titled "Altering a memorandum." So is the "any person or persons, whether or not members or supervisors" clause (s.9(3)) and the fifteen-day Registrar-filing rule (s.9(4)). **Every one of those is a memorandum rule.** Section 10, governing articles, contains none of them: no self-entrenchment default, no filing clock, no restriction on who may hold the pen. The consequence is starker than entrenchment-by-default would be. For an articles clause, there is *no* statutory floor. Unless the constitution expressly (i) vests the power to alter the appointment/removal clauses in a passed ENS DAO vote and (ii) entrenches that gate against its own rewriting, the Act supplies neither protection by operation of law. Nobody in this thread has published the Articles or shown that either safeguard is present. On the statute's defaults, the removal right can be amended by whoever the constitution happens to name as holder of the alteration power — without a tokenholder vote. **Step three — the DAO, as a beneficiary, has no route to enforce it.** Assume the removal clause survives. Enforcing it against a resistant board requires standing, and I will be precise about which door is which, because an earlier draft over-claimed here. Section 7(4)(d) lets "an interested person bring an action in the name or on behalf of the foundation company for the enforcement of the duties or liabilities of *directors*." That is a derivative action about directors' fiduciary conduct — not a vehicle to enforce a constitutional removal clause. Enforcing the clause itself falls under s.7(4)(b): rights under the constitution "are enforceable against the foundation company only." So the removal right is a paper right, owed by the company, and the Act names no one on the DAO's side of the table with standing to compel the company to honour it. Who is an "interested person" who could at least run the derivative route? Section 2(1): "(a) any of its members or supervisors; (b) someone who has the right to be a member or supervisor; and (c) someone declared under its constitution to be an interested person." Then s.7(4)(e), removing all doubt: "a beneficiary of the foundation company has no powers or rights relating to the foundation company, its management or its assets and is not an interested person." On the statutory definition (s.2, "beneficiary": one "who will or may benefit from the foundation company carrying out its objects"), tokenholders are beneficiaries. Unless the constitution *declares* them interested persons, they hold neither the s.7(4)(d) derivative route nor any Part 5 route into the Grand Court. **The Part 5 door is shut too — verified, not hedged.** I previously flagged the Part 5 standing point as unverified; I have now read ss.18-21 and it checks out and is stronger than I stated. Section 18(2) limits applicants for constitutional obsolescence to the company, its secretary, an interested person, a person authorised under the constitution, or the liquidator. Section 19(2) — the breakdown-in-appointment section, the one on point — limits applicants to "a member, supervisor, director, officer or interested person," the secretary, or anyone authorised under the constitution. **Beneficiaries are excluded from both.** And the single power that could actually rewrite the removal machinery — s.19(4)(a)(ii), under which the Court may alter "the provisions of the constitution about appointing or removing directors" — is exercisable only on the application of a qualifying person under s.19(2), and only once a "directorship difficulty" has arisen. The beneficiary DAO is outside every one of these doors. **Why it matters, and what breaks.** Reversibility was sold as the answer to every custody worry in this gathering. But a removal power that (a) sits in Articles the Act does not protect from amendment by default (s.10), and (b) cannot be enforced by the DAO through any route the Act names (s.7(4)(b)/(d)/(e), s.2, s.18(2), s.19(2)) if a board declines to file its own removal, is not a backstop. It is an assurance. The failure mode is quiet: not a dramatic refusal, but a board — or a service provider holding the pen — that never files the change of directors, and a DAO that discovers its only recourse is a court it lacks standing to petition. This is the corner "The Board That Passes Is Not the Board That Exists" opened but did not close: it established that the Foundation's supervisor is DS Limited, a paid corporate service provider — not the DAO. That fact is what condemns the DAO to beneficiary status here. And it is a different gap from "The Removal Process Runs on Documents the Foundation Keeps," which concerns the *evidence* a removal petition needs; mine is prior to evidence — whether the clause survives, and whether the DAO may sue on it at all. **The minimal amendments.** Each operates on the constitution, not on the board's management judgment, and each is cheap. I lead with the cleanest. 1. *Seat the DAO's timelock as a supervisor.* Section 8(1): the constitution "may grant... to any person or persons... the right to become a member or supervisor." A supervisor is defined (s.2) by an unconditional right to attend and vote at general meetings — and is an interested person under s.2(1)(a) *directly*. Naming the ENS DAO timelock (wallet.ensdao.eth) a co-supervisor alongside DS Limited is therefore the single cleanest standing fix: it confers interested-person status without relying on any declaration, and it stops the Act's own control seat from being held exclusively by a paid intermediary. (I note as a premise-correction: s.8 does *not* require a member-holding foundation to have a supervisor — s.8(2) only conditions *ceasing to have members* on retaining one — so this is a drafting grant, not a cure for a defect.) 2. *Declare the DAO an interested person.* As a belt-and-braces to (1) — in case a smart-contract address is contested as a "supervisor" — s.2(1)(c) invites exactly this: declare the ENS DAO an interested person, conferring the s.7(4)(d) derivative standing over directors' duties. 3. *Entrench the appointment and removal clauses in the articles-alteration provision.* Because these clauses are in the Articles, the entrenchment must be drafted expressly into the constitution's articles-alteration provision under s.10 — there is no s.9(2)(b) default to inherit. Provide that the appointment, term-renewal and removal provisions may be altered only with the consent of a passed ENS DAO on-chain proposal, and that this gate does not authorise alteration of itself. (If the objects are also entrenched, that is a memorandum change, so s.9 — including s.9(2)(b) and the s.9(4) fifteen-day filing — governs *there*.) 4. *Gate the money to the filed constitution.* Condition the treasury transfer — including the budget-funding path that "The Second Side Door" showed is exempt from the timelock — on the Registrar-filed amended Articles whose hash is posted on-chain. Because s.10 sets no filing deadline for articles, the trigger is the fact of the Registrar-filed amendment, not a statutory clock (the fifteen-day clock in s.9(4) reaches only a memorandum/objects amendment). The DAO should not fund a Foundation whose Articles it cannot amend. **The strongest objection — the Cayman fetter.** One will say: a director cannot fetter the future exercise of his discretion, so you cannot entrench anything. That objection is aimed at the wrong target. The fetter doctrine constrains what *directors* may bind themselves to do in *managing* the company. None of my amendments touches management discretion. They operate on the *constitution's articles-alteration provision* (s.10 leaves the holder of that power to the constitution) and on *standing* (a status the Act expressly permits the constitution to confer — s.2(1)(c), s.8(1)). This is also where I part from "The Unfettered Discretion Gap," the closest Cayman-law proposal: it asks what the DAO may lawfully *require of directors* in the exercise of their judgment; I ask a mechanically different question — who holds the pen over the articles-alteration provision itself, and who has standing to invoke it — which is amendment mechanics and standing, not fettering. Nothing I propose asks a director to bind his discretion. **What would change my reading.** Publication of the actual Articles showing two clauses already present: (i) an articles-alteration provision that reserves any change to the appointment/removal clauses to a passed ENS DAO proposal and is expressly entrenched against its own amendment (there being no s.10 default to rely on); and (ii) a declaration under s.2(1)(c), or a supervisor grant under s.8(1), giving the DAO standing. If both already exist in the filed constitution, this collapses to a request that the temp check cite them. I have not seen the Articles. The proposal tells me only that they are "unchanged" — and on the statute, unchanged is not safe.