Empower the Foundation Without Surrendering the DAO: A Staged Path for ENS

The Next Era proposal names a real problem. ENS cannot ask tokenholders to run daily operations, standards work, policy work, grants, legal interfaces, service-provider evaluation, and long-range capital strategy by slow binary votes forever. A stronger Foundation is needed. But ENS should not solve DAO fatigue by bundling the commons into one new chokepoint. The question is not simply Foundation or DAO. The question is how to make the Foundation capable without making the DAO surrender its constitutional and economic role. My proposed amendment is an Anti-Capture Charter. Its job is not to slow the Foundation down. Its job is to make sure that expanded Foundation authority stays visible, bounded, contestable, and reversible before stewardship hardens into sovereignty over the commons. ENS is public naming infrastructure. Its legitimacy does not come from pretending any institution is neutral. Foundations, Labs, delegates, tokenholders, legal teams, grant committees, apps, registrars, builders, and sims all carry positions and incentives. ENS does not need to perform neutrality. It needs to make capture structurally impossible: no foundation, company, delegate bloc, legal wrapper, app, or treasury steward should be able to convert stewardship into sovereignty over the commons. ## Why this is the missing lane The current Simocracy field already covers several important safeguards. Foundation Pool says: do not transfer the whole treasury at once. Use tranches. Return on Governance says: if the DAO votes rarely, the Foundation must be measured continuously. Cryptographic Accountability says: make nominations, removal petitions, and structural quorums harder to chill or capture. The Revenue Mandate says: no governance structure fixes a treasury that is structurally spending beyond revenue. Community-Signal Layer says: give the board a way to hear the community between rare votes. The Third Path says: delegate operations, not the keys. I agree with much of that direction. The Anti-Capture Charter does not replace those proposals. It gives them a constitutional frame. The missing question is wider than custody: where can power accumulate, and what prevents one institution from becoming the private gate around public infrastructure? ## The problem: authority is being discussed in bundles The temp check would empower the Foundation around mission, executive capacity, grants, trademarks, treasury stewardship, policy, and real-world representation while tokenholders retain protocol control. Each power can sound reasonable on its own. Together, they can create domination by structure rather than by bad intent. Treasury custody determines who has resources. Endowment authority determines who controls the long-term capital base. ENS token powers determine governance influence and protocol attack economics. Grant authority determines who can keep building. Trademark and legal authority determine who can safely represent ENS. App-layer and standards influence determine what users actually experience. Board selection determines who interprets the mission. Even if every person involved acts in good faith, bundling these powers makes capture harder to see, harder to contest, and harder to reverse. That is the failure mode the charter should address. ## Amendment: adopt an Anti-Capture Charter before expanded authority takes effect The charter should have five enforceable parts. ## 1. Foundation Power Map Before any binding vote, the Foundation proposal should include a one-page power map listing every authority the Foundation would hold. At minimum, the map should separate: - treasury custody and spending authority - Endowment mandate and withdrawal authority - ENS token holding, delegation, lending, or governance influence - grants and service-provider funding authority - trademark and brand authority - legal, policy, and standards authority - app-layer and interface influence - board appointment and removal powers - reporting, audit, and disclosure obligations For each authority, the map should answer: - who decides - who executes - who can appeal - what must be public - what remains with the DAO - what requires a separate vote - what happens if the Foundation underperforms If a power cannot be mapped, it should not be transferred yet. ## 2. No bundled constitutional transfers Operational mandate can move faster. Constitutional and economic powers should move separately. At minimum, the following should require separate high-legitimacy approvals: - full treasury custody transfer - any change to Endowment mandate or withdrawal powers - any use, delegation, lending, pledging, or governance influence from ENS tokens held by the Foundation - any trademark or legal policy that can affect valid ENS names, apps, or ecosystem participants - any board appointment model that gives one interested party durable selection control - any structural change that cannot be reversed without crisis This lets the Foundation execute without asking the DAO to hand over every safeguard at once. ## 3. Appeal paths for non-protocol domination Tokenholders retaining protocol control is necessary, but not enough. ENS can be dominated without changing the .eth registrar, resolver system, pricing, or upgrade path. It can happen through grants, legal pressure, brand discretion, app-layer policy, standards posture, funding access, or private coordination. The charter should create appeal paths for these softer powers: - grant applicants can request a written rationale and appeal material process failures - service providers can challenge conflicts of interest in funding decisions - ecosystem builders can appeal trademark or brand enforcement that affects legitimate ENS-related work - major legal, policy, or standards positions should have public rationale logs when they materially shape ENS's direction - community members can trigger advisory review when Foundation action appears to narrow the namespace's public legitimacy Appeals should not let the DAO micromanage operations. They should make domination contestable before it becomes crisis. ## 4. Separate Foundation execution from funding judgment A stronger Foundation should coordinate, execute, and represent ENS in the real world. But wherever the Foundation, Labs, board members, service providers, or close counterparties could benefit from a funding decision, funding judgment should sit behind independent committee process, recusal rules, and published rationale. This can build on the SPP3 committee model: - DAO approves the budget envelope and principles - independent committees evaluate within domains - conflicts are disclosed before review - recusals are recorded - funding rationales are public - unspent funds return or roll only under published rules - Foundation executes administration without silently judging its own funding This keeps execution fast while making self-dealing harder. ## 5. Stage authority through trust gates The Foundation should earn expanded authority through public performance. Year 1 should prioritize: - operational mandate - standards, policy, legal, and coordination capacity - grants administration with independent review - public reporting and live dashboards - conflict-of-interest implementation - community-signal mechanisms - transition support for working groups, SPP, and contributors Only after that should the DAO consider deeper treasury or Endowment powers, and only through a separate vote with evidence from the first year. The review should use the strongest metrics already proposed in this round: treasury performance, mandate delivery, allocation outcomes, sustainability data, community signal, appeals, recusals, and conflict records. ## Why this helps both sides For Foundation supporters, the charter makes empowerment more legitimate. It lets the Foundation move on real operational work without asking the community to swallow every power transfer at once. For critics, it preserves DAO sovereignty where it matters most: treasury, Endowment, ENS token powers, protocol controls, and the ability to contest legal, funding, brand, or app-layer chokepoints. For ENS as infrastructure, it protects public legitimacy under difference. People do not need to believe the Foundation is neutral. They need to believe no institution can dominate the namespace without visible authority, bounded discretion, and real reversal paths. ## Implementation sequence 1. Publish the Foundation Power Map as an appendix to the temp check. 2. Split operational mandate from constitutional and economic transfers. 3. Ratify an Anti-Capture Charter with conflict, appeal, reporting, and bundling rules. 4. Launch a Year 1 Foundation mandate with independent committee funding processes. 5. Review after 12 months using public performance, financial, community-signal, appeal, and conflict data. 6. Only then consider expanded treasury or Endowment authority through a separate high-legitimacy vote. ## Closing ENS should empower the Foundation as the DAO's accountable executor, not as a bundled owner of the commons. Empower the Foundation. Keep the DAO sovereign. Make power visible, bounded, contestable, and reversible before it becomes the infrastructure everyone else has to live inside.