No Appointed Opposition: An Independence Test for the ENS Foundation Board

The strongest argument for empowering the ENS Foundation is real: token-vote governance is not a good tool for every operational decision. ENS needs legal capacity, long-horizon execution, standards work, grants operations, vendor management, and faster coordination than a full DAO process can provide. But that argument does not settle who gets to become the trusted operating layer. The current debate keeps returning to treasury custody, spend rates, and conflict-of-interest policy. Those matter. But the sharper question is board independence. A Foundation can be operationally useful and still become captured if the board that checks it is independent only in form. The fresh frame is this: **Do not ask the DAO to trust appointed opposition. Make independence a testable public condition of expanded authority.** ### Mechanism: Board Independence Test and Challenge Window Before the Foundation receives expanded authority, ENS adopts a Board Independence Test. Every proposed director, and every continuing director after a material mandate expansion, is mapped against a public matrix of independence criteria. The matrix does not accuse anyone. It asks whether the role can credibly check the people, entities, vendors, and funding flows it is meant to oversee. The test has five components. ### 1. Independence matrix **Who decides:** ENS DAO ratifies the matrix as part of the empowerment package. **Who executes:** The Foundation publishes a director-by-director disclosure against the matrix before the mandate starts. **Who reports:** A public reviewer or rotating reviewer pool publishes a short independence memo. Minimum criteria: - current or recent employment, contractor, investor, grant-recipient, vendor, or major commercial relationship with ENS Labs, the Foundation, or any entity expected to receive material funding; - family or close business relationship with current directors or executives; - compensation dependency or expected future role created by the new mandate; - ability to vote independently on Labs funding, vendor selection, treasury strategy, and executive review; - public reason why this person adds a distinct oversight perspective rather than merely ratifying the proposer’s context. ### 2. Challenge window **Who appeals:** Delegates, working groups, major service providers, and ordinary tokenholders may submit a challenge during a fixed 14-day window. **Who executes:** Challenges must cite a criterion in the matrix and a public source or direct disclosure. Anonymous vibes do not count. **Who reports:** The reviewer publishes: valid challenge, invalid challenge, or needs cure. This protects directors from smear campaigns while still giving the DAO a real way to test independence before authority moves. ### 3. Cure path **Who reverses or repairs:** If a director fails one criterion, the default is not automatic removal. The Foundation can cure the issue by adding disclosure, recusal rules, a non-voting observer, a replacement candidate, or a limited mandate for that director. **Who decides:** The DAO ratifies any cure if the failed criterion touches treasury custody, Labs funding, vendor selection, grants, or board self-appointment. This avoids purity politics while preventing quiet capture. ### 4. Independence floor for board decisions Major decisions require an independence floor, not just a headcount threshold. For example, any decision that materially affects Labs funding, Foundation treasury strategy, director compensation, vendor selection, or the scope of the Foundation mandate should require approval from at least two directors who pass the relevant independence criteria for that decision. If the board cannot meet the independence floor, the decision routes back to the DAO or to a narrower temporary authority. ### 5. Sunset review **Who reports:** Every 12 months, the Foundation publishes a board-independence report alongside its normal operating report. **Who reverses:** If the independence floor fails for two consecutive quarters, any expanded authority tied to discretionary spending, mandate expansion, or board self-renewal pauses until the DAO ratifies a cure. The pause does not shut down basic operations. It stops new authority from compounding while the check is broken. ## Adoption path 1. Add the Independence Test as an amendment to the ENS Foundation temp check. 2. Run it once before any expanded Foundation authority begins. 3. Treat the first cycle as a `$150,000`, 90-day pilot for the full independence-test packet, public review process, reviewer pool, legal/governance review, dashboard/attestation layer, and reusable templates. 4. After one cycle, keep only the parts that changed a decision, surfaced a material conflict, or increased confidence in the board. 5. If the test proves noisy or redundant, sunset it. ## Why this is not duplicative This does not replace the custody proposals. It works whether treasury custody stays onchain, moves to the Foundation, or is tranche-gated. This does not duplicate the conflict-of-interest policy proposal. COI policy governs transactions and recusals after the board exists. This proposal asks whether the board itself is independent enough to receive expanded authority in the first place. This does not duplicate the measurement dashboard proposals. Dashboards measure performance after execution. This is an ex-ante legitimacy test before concentrated power begins. This does not repeat Lovepunks' earlier Anti-Capture Charter. It turns one part of the charter into a concrete primitive: no institution's position should quietly become everyone’s infrastructure through an untested board. ## What would change our mind We would support a lighter version if the Foundation publishes a stronger board-selection process that already includes public independence criteria, a challenge window, recusal/cure paths, and a DAO-ratified independence floor for major decisions. We would also narrow this proposal if the DAO keeps treasury custody fully onchain and gives the Foundation only a small, capped operating mandate. The larger and less reversible the authority, the stronger the independence test should be. ## Closing ENS can empower the Foundation without pretending power disappeared. The point is not to block operational capacity. The point is to make sure the people holding operational capacity can be checked by someone other than the same institution that benefits from it. Credible non-domination means no side gets to quietly write the rules for everyone else. If the Foundation is going to become the operating layer, its board independence should be visible, testable, appealable, and reversible. ---