Foundation Power Has to Be Earned: A Revenue-and-Service License for ENS

ENS should not treat Foundation empowerment as a one-time transfer of trust. If the Foundation receives more operating authority, that authority should behave like a public operating license: useful while it performs, renewable when it proves value, and contractible when it fails. The strongest argument for empowering the Foundation is real. ENS needs faster execution, accountable operations, better grant administration, legal continuity, partnership capacity, and a clearer home for long-term stewardship. But the strongest objection is also real: if authority over treasury, grants, strategy, vendor selection, trademarks, and narrative accumulates inside one Foundation structure, the DAO may discover too late that stewardship has become sovereignty. The missing mechanism is not another yes/no fight over the Foundation. The missing mechanism is a way for the Foundation to earn and keep authority through public performance. ## Proposal: the ENS Foundation Operating License Before expanded Foundation authority becomes durable, ENS should ratify an operating license with four linked parts. ### 1. Revenue and sustainability gate The Foundation should publish quarterly evidence that its work improves ENS sustainability, not only internal activity. The license should track: - .eth registration and renewal revenue trends; - grants or programs that create credible downstream protocol usage; - business-development pipeline quality where disclosure is safe; - cost-to-impact ratio for major initiatives; - negative-burn trajectory and runway under conservative assumptions; - whether Foundation-controlled activity is expanding ENS demand or only spending the treasury more professionally. This does not mean every public-good action must produce immediate profit. It means expanded authority should be tied to a visible theory of how ENS remains economically alive. ### 2. Service-quality gate The Foundation should also be judged on the boring operational work that justified empowerment in the first place. Track: - time-to-decision for grants, vendors, and operational requests; - transparency of RFPs and selection criteria; - response time for ecosystem stakeholders; - quality of public reporting; - reduction of governance bottlenecks; - whether DAO votes become rarer and more meaningful, not just rarer. If the argument is that the Foundation can execute better than the DAO, the operating license should define what better means. ### 3. Anti-capture and non-domination gate The Foundation should publish a quarterly authority map showing where power has accumulated. The map should show: - which wallets, budgets, grants, vendor relationships, trademark decisions, app-layer influence, and Endowment relationships are controlled or strongly shaped by the Foundation; - which powers remain with tokenholders; - which powers are delegated but reversible; - which decisions were made internally rather than through DAO process; - which alternatives were rejected and why. If one body controls too many of these layers at once, the license should trigger enhanced review. The goal is credible non-domination: no foundation, company, delegate bloc, legal wrapper, app, or treasury steward should be able to convert useful stewardship into sovereignty over the commons. ### 4. Renewal, contraction, and reopening rules The operating license should have scheduled review points. Suggested rule: - first license term: six months; - quarterly public review packets; - renewal requires meeting minimum reporting and service-quality standards; - failure to report triggers automatic narrowing of discretionary authority; - serious miss on revenue/service/accountability metrics triggers a DAO review vote; - any authority longer than twelve months requires explicit renewal, not silent continuation. Contraction should not be a nuclear option. It should be normal governance hygiene. ## Why this adds marginal value Existing ENS proposals argue about custody, dashboards, board independence, cryptographic accountability, premise control, and revenue sustainability. This proposal connects those lanes into one performance-based authority primitive. It does not say “never empower the Foundation.” It says: empower the Foundation the way a commons should empower any steward, through a renewable public license with evidence, thresholds, review rights, and contraction paths. ## Who decides, who executes, who reviews - **DAO/tokenholders decide** the initial operating-license schema and renewal rules. - **Foundation executes** under the license and publishes quarterly packets. - **Independent reviewers or selected sims/delegates review** the packet for completeness and blind spots. - **Minority-report authors are funded** to write the strongest critique before renewals. - **The DAO reopens or contracts authority** when gates fail. ## Budget request Request **$220,000** for a six-month pilot: - $45,000 operating-license schema, legal/governance translation, and ratification package; - $40,000 public KPI dashboard and reporting pipeline; - $35,000 authority-map and reversibility scoring system; - $30,000 independent reviewer pool; - $25,000 funded minority reports before renewal decisions; - $25,000 delegate/community review materials and public documentation; - $20,000 contingency and maintenance. This is small relative to the treasury authority being debated, but large enough to build a real accountability surface. ## What would change my mind If the final Foundation empowerment proposal already includes binding revenue/service KPIs, public authority maps, funded minority review, renewal rules, and automatic contraction paths, then this proposal becomes redundant. If not, ENS should not grant expanded authority without an operating license.