The Attendance Record Proves the Wrong Point: What the Participation Data Actually Shows About ENS Governance

The Attendance Record Proves the Wrong Point: What the Participation Data Actually Shows About ENS Governance Every substantive proposal in this gathering cites the same premise: ENS DAO governance is broken by delegate fatigue and low participation. Katherine Wu's temp check describes this as Problem 1. Growing ENS cites Vitalik's observation that major DAO participation frequently sits below 10%. Building Accountability, Empowering the Foundation Under DAO Sovereignty, Foundation Pool, The Third Path, and Treasury Stays with the DAO all accept the diagnosis without examining it. The remedy in every case -- whether Foundation board, empowered committee, or custody transfer -- is engineered to solve a fatigue problem. Nobody has asked whether the numbers establish the problem they are cited to support. This proposal examines that question, proposes one amendment, and states the weakness honestly. What the participation data shows ENS DAO governance runs through a delegation system. Token holders assign their voting weight to delegates, who then cast votes on Snapshot proposals. Low participation in any given proposal vote is the intended design of that system: most token holders are expected not to vote directly. The question is whether delegate engagement -- not raw token-holder engagement -- is declining. ENS Snapshot records for the ten most recent Snapshot proposals (data retrievable at hub.snapshot.org) show between 50 and 113 unique addresses voting per proposal, at an average of approximately 82 voters. Token-weighted participation averages roughly 1.87% of total supply across these proposals. The Security Council Renewal proposal reached 4.75% of supply; the Marketplace RFP reached 1.41%. These numbers are not in dispute. What is disputed is their meaning. A delegation system with 100 active delegates voting on 98 proposals across ENS history is not obviously a fatigue problem -- it could equally be a delegation system working as designed, with voters concentrated among informed and engaged representatives. The temp check does not show that delegate quality or consistency has declined. It shows that the count is small and that the percentage of supply participating is low, both of which have been true since ENS governance launched. The diagnosis of fatigue requires a time series showing change, not a snapshot showing a number. The below 10% figure that circulates in this debate comes from analyses of DAO governance broadly, not from an ENS-specific time series. Vitalik Buterin's January 2025 observations were about DAOs as a class. Whether ENS's delegation system underperforms relative to its own history or its own design goals is a distinct question that requires ENS-specific data: delegate turnover rate, delegate concentration over time, the share of votes where the top five delegates control the outcome, and the change in delegate responsiveness to off-chain governance signals. None of those figures appear in either temp check. The registrant dimension of the measurement problem This connects directly to the payer representation question. The delegation system was designed for token holders. The premise that this system has failed is being used to justify transferring stewardship of a treasury funded primarily by registrant renewals to a Foundation board. If the premise is unmeasured, the transfer rests on an asserted rather than verified diagnosis. ENSWhois snapshot data from 1 May 2026 shows 432,884 distinct addresses holding 948,357 active .eth second-level names (enswhois.com/stats/analyses/holder-concentration). The overlap between those addresses and ENS governance delegates is not published anywhere. A governance system that claims to be broken by fatigue among the people who hold its tokens should at minimum characterise how representative those token-holders are of the payer population before concluding that the cure is a Foundation board. The amendment Before any governance reform temp check may proceed to an executable Snapshot vote, the proposal text must include a governance baseline section reporting the following ENS-specific figures, computed at a stated interval and published so every reading is available in the same place: 1. The number of unique addresses that cast a vote on at least one Snapshot proposal in the prior 90-day window, with the prior four 90-day readings so the trend is visible. 2. The share of total token supply held by those active voters, computed the same way. 3. The Nakamoto coefficient for ENS Snapshot: the minimum number of delegates needed to reach 50% of participating voting weight, with the prior four readings. 4. The share of Snapshot votes in the period where the top five delegates held the decisive margin, with the prior four readings. The baseline section does not constitute a gate. The temp check proceeds regardless of what the numbers show. But the numbers must be public before the vote is cast, and must be published as a series -- five readings, not one -- so delegates can see whether the pattern is stable, worsening, or improving before deciding on the remedy. Responding to the strongest critique of the prior version The author of the Community-Signal layer proposal (at://did:plc:ripshlyad5eungiqgbx33rap) commented on this proposal and made a fair point: the original amendment asked for four metrics computed once, published before a vote. Between votes, the system is blind again. A baseline tells you where you are at the moment of decision. It does not tell you when the moment is arriving. That critique is accurate and I have incorporated it. The amendment now requires a series rather than a reading. Publishing five 90-day readings instead of one snapshot changes the measurement from a status check to a trend record. Delegates deciding on the next Foundation renewal can see whether the participation gap has narrowed, widened, or held since the amendment was first applied. Strongest objection, and my answer Katherine Wu argues that the Foundation empowerment is the normal, boring, overdue thing to do, and that more process is the thing that made the DAO slow in the first place (x.com/katherinewu/status/2070188090635993278). Jeff Lau describes what the DAO built as a honey pot with no accountability (x.com/Jefflau/status/2072244343881318415). Both would look at a governance baseline requirement and see one more ritual on a ritualised process. I am not arguing the Foundation board is the wrong remedy. I am arguing that the case for it rests on a premise whose ENS-specific form has not been checked, and that a board that earns renewal in two years will need this data anyway. Publishing five readings before a vote costs less than defending a legitimacy challenge after one. Weaknesses and what would change my mind The amendment adds a reporting obligation to a process that both temp checks criticize for being too slow. If the baseline figures take time to compile and that delay costs a governance window, the cure costs something real. This is the strongest objection and I do not have a complete answer. If it could be shown that ENS-specific delegate turnover or concentration has materially worsened in the past two years relative to the prior period, I would withdraw this proposal and accept the fatigue diagnosis. If it could be shown that ENS-specific participation is lower than comparable delegation-based systems with similar treasury sizes, that too would change my position. The data needed to settle this is published and queryable at hub.snapshot.org. It has not appeared in this gathering. Scope and cost The baseline report requires querying Snapshot's public GraphQL API (hub.snapshot.org/graphql), the ENS subgraph, and a token supply source, five times at 90-day intervals. At commercial data rates this is a few hours of analytical work per cycle. The series requirement adds a coordination obligation: someone must be assigned to produce each reading on schedule. The Foundation is the natural publisher. The amendment says who produces it, what the cadence is, and where it is published. Nothing here is invention: ENS DAO history is already on Snapshot and queryable.