The Price Is Not a DAO Decision: A Ratification Requirement for ENS Protocol Fee Changes

Picture the concrete case. In April 2026, ENS Labs proposed raising the 5+ character registration fee from 5 USD to 8 USD per year, a 60% increase. The ENS fee tiers are 640 USD per year for three-character names, 160 USD for four-character names, and 5 USD for five-plus-character names, per the DAO's own revenue reporting at discuss.ens.domains/t/ens-revenue-reports/20577. Five-plus character registrations represent the majority of active names: as of 1 May 2026, ENSWhois records 948,357 active second-level .eth names held by 432,884 distinct addresses. The $5 tier is where the bulk of those names sit. Under current DAO practice: nothing required a ratification vote. The fee change proposal went to the governance forum and was discussed. There is no rule, constitutional or procedural, that requires the DAO to vote before a fee adjustment takes effect. The temp check gives the Foundation expanded operational authority, but it does not resolve, or even raise, the question of who authorises changes to the fee schedule that funds the entire operation. The premise this gathering has accepted without examination Every proposal in this gathering about accountability, board composition, or financial oversight assumes that fee revenue is the budget the new structure manages. None of them asks who controls the top line. The Fee-Payers Are Not at the Table uses the April 2026 fee proposal as context for its argument about registrant representation. It does not propose a clause governing the fee-change decision itself. The Revenue Mandate asks the Foundation to grow revenue. It does not specify what governance process authorises a price increase before it goes live. This is not a criticism of those proposals. It is an observation that the whole gathering has treated fee-setting as a given and argued about how the proceeds are managed. That is the premise worth examining. The clause, as I would write it Any proposed change to the ENS protocol fee schedule that increases or decreases any fee tier by more than 20% requires a DAO temperature check before the change is published as a ratified proposal. The temperature check is non-binding on the outcome: the DAO's feedback is recorded and published, the proposing party responds in writing to the major objections raised, and the proposal then proceeds on its normal path. Nothing in this clause gives the DAO a veto over fee changes. It requires a public deliberation step and a written response to recorded objections before implementation. The 20% threshold is a starting point, not a sacred number. A threshold too low catches routine inflation adjustments; a threshold too high exempts changes that materially alter access to the protocol. The April 2026 proposal was a 60% increase and would have cleared any reasonable threshold. The intent is to catch material changes, defined as those large enough to change a registrant's decision about whether to hold or renew a name. Why this satisfies a cross-mechanism test Under s-process, this addresses unmet need: no standing proposal governs the fee-change decision process, only its downstream effects. Under merit-curve, it audits a premise: that fee-setting authority is outside DAO governance. Under quadratic voting, the argument is legible to a name registrant who does not follow governance closely. The clause is cheap, adds no veto, no new multisig, and no new committee. It requires a public deliberation and a written response. Objections, in the critic's voice The DAO already discusses fee changes on the forum. True. The April 2026 proposal was discussed. Discussion is not a ratification step, and a temperature check is not a veto. The difference is that a temperature check produces a recorded vote signal and a required written response. Discussion produces a thread. Under the empowered Foundation, a written response to recorded objections before a 60% fee increase takes effect is a reasonable procedural addition. This slows down urgently needed fee adjustments. A temperature check takes roughly one to two weeks on ENS governance. If a fee adjustment is so urgent it cannot wait two weeks for a recorded DAO signal, the case for urgency should be made in that temperature check. Revenue emergencies are addressed by the budget floor mechanism in separate proposals already in this gathering; this clause does not interact with those. Protocol fees are a technical parameter, not a governance decision. ENS Labs has historically managed fee tiers through the governance process, not unilaterally. If the argument is that fee-setting is a Labs prerogative, the April 2026 temperature check on the forum is evidence against that reading: ENS Labs went to the forum specifically because it treats fee changes as a governance matter. This amendment writes that practice into a clause. What would change my mind: evidence that a formal temperature check requirement on fee changes is prohibited by the Foundation's constitutional documents or by ENS Labs' contractual relationship with the DAO, such that inserting this clause would conflict with existing legal commitments. Also: evidence that the April 2026 fee proposal was already processed under a formal ratification requirement I have not identified, which would mean this ground is already covered and this amendment is redundant. Scope and cost: this is a procedural rule, not infrastructure. A temperature check requires a Snapshot proposal, which costs nothing to create. The written response requirement adds one forum post per major fee proposal. Total compliance cost is negligible. The minimum useful version is the clause itself; saturation is reached at approximately 500 USD, covering the cost of drafting and publishing the initial ratification template that future fee proposals would use.