---
title: "ENS DAO"
url: "https://caper.network/wiki/daos/infrastructure/ens-dao"
updated: 2026-09-03
license: CC-BY-4.0
license_url: "https://creativecommons.org/licenses/by/4.0/"
---

# ENS DAO

|  |  |
| --- | --- |
| **Name** | ENS DAO |
| **Type** | Protocol DAO (naming / identity) |
| **Governs** | The Ethereum Name Service (.eth names and identity) |
| **Protocol roadmap** | [ENSv2](https://ens.domains/ensv2) — deploying on Ethereum mainnet after the [Feb-2026 Namechain L2 cancellation](https://www.coindesk.com/tech/2026/02/06/ethereum-s-ens-identity-system-scraps-planned-rollup-amid-vitalik-s-warning-about-layer-2-networks) |
| **Governance token** | ENS (airdropped November 2021) |
| **Structure** | Working groups + a Cayman-based [ENS Foundation](https://docs.ens.domains/dao/foundation/); an endowment managed by Karpatkey |
| **Treasury** | Roughly $350 million including ENS tokens (~$88M excluding them), July 2026 |
| **Primary sources** | [discuss.ens.domains](https://discuss.ens.domains/), [docs.ens.domains](https://docs.ens.domains/) |
| **Related** | [What is a DAO?](/wiki/dao-governance/concepts/fundamentals/what-is-a-dao), [Governance models](/wiki/dao-governance/concepts/fundamentals/dao-governance-models), [Uniswap](/wiki/daos/dexs/uniswap-dao) |

The **ENS DAO** governs the [Ethereum Name Service](https://ens.domains/), the dominant naming and identity layer for Ethereum, which maps human-readable _.eth_ names to wallet addresses and other records. Since a November 2021 airdrop of the **ENS** token, the protocol's treasury, working groups, and parameters have been governed on-chain by token holders and their delegates. ENS governance is frequently cited as a benchmark — and, in 2026, as a cautionary tale about [voting-power concentration](/wiki/dao-governance/concepts/fundamentals/dao-governance-models).

## Structure

The DAO funds work through **working groups** (such as Public Goods and Ecosystem) and holds an **endowment** managed by the asset manager Karpatkey to give it a self-sustaining runway. Its legal interface is the **ENS Foundation**, a Cayman Islands nonprofit that provides limited liability and lets the DAO contract with the real world; the Foundation's directors handle day-to-day operations while remaining removable by token-holder vote. ([ENS Foundation — ENS docs](https://docs.ens.domains/dao/foundation/))

## The 2026 governance battle

In June 2026 ENS became the year's most-discussed governance dispute, and the record of it is unusually complete: every step ran through the DAO's own forum, Snapshot space, and governor contract.

On 19 June a proposal introduced by the delegate katherine.eth sought to transfer operational control, grants, and treasury management – the operational wallet, the DAO's ENS holdings, and the Karpatkey-managed endowment – to a five-seat ENS Foundation board. In parallel, the DAO was voting on whether to renew its [Security Council](/wiki/dao-governance/concepts/fundamentals/security-councils), the 4-of-8 multisig whose single power is to cancel a proposal already sitting in the timelock. The two questions were inseparable: a council empowered to cancel a passed proposal could, in principle, cancel that one.

The [advisory Snapshot vote](https://snapshot.box/#/s:ens.eth/proposal/0x9ed89cf79760eb92d220fee2da08896bf027317f394aab87863011f964e19453) on renewal (23–28 June, 73 voters) read as a clear pass: 1,274,195 ENS for to 85,204 against. It also carried 3,386,139 ENS abstaining – 71% of everything cast – of which 3,261,042 came from a single voter, ENS lead developer [nick.eth](https://api.ensdata.net/0xb8c2C29ee19D8307cb7255e1Cd9CbDE883A267d5), whose self-delegation that month was itself the subject of the dispute ([The Defiant](https://thedefiant.io/news/defi/ens-dao-delegates-governance-attack-johnson-self-delegates)).

The binding vote went the other way. Read from the [ENS Governor](https://etherscan.io/address/0x323A76393544d5ecca80cd6ef2A560C6a395b7E3), the executable that would have granted the renewed council its cancel role opened at block 25,424,114 (29 June 2026, 15:07 UTC) and closed at block 25,469,932 (6 July 2026, 00:34 UTC), and it was [defeated](https://www.tally.xyz/gov/ens/proposal/45402179622316441394139979097514597399865468312011562941203078514615705423505) 3,859,981 ENS against to 1,137,702 for. The DAO's advisory instrument and its binding one had pointed in opposite directions.

The replacement was tabled while that vote was still running, not after it. On 30 June katherine.eth posted a [framework for a new council](https://discuss.ens.domains/t/draft-social-proposal-for-a-new-security-council/22219): eight members, the threshold for any cancellation raised from 4-of-8 to 5-of-8, a tighter written mandate, a public pledge each nominee must affirm, a removal mechanism for members who act outside it, and an Appointment Agreement with the ENS Foundation drafted by counsel – with the scope of authority deliberately unchanged, “cancellation of timelocked proposals, nothing more”. Nominations were open to anyone and closed on 6 July. Eight of fifteen candidates were elected in a [Copeland-method vote](https://snapshot.box/#/s:ens.eth/proposal/0x3e7acd4a47b246382bf9a3aeb71d0fd1562d38dbb9f7b7760445cf9731229b9d) (7–12 July, 50 voters), and the [executable seating them](https://discuss.ens.domains/t/executable-establishing-a-new-security-council/22272) passed 4,228,716 to 94,526.

As of 8 August 2026 the outcome is verifiable on-chain: the new [council contract](https://etherscan.io/address/0x2acBf518b3759f6e1fA163294eda55bF1d0ae051) holds `PROPOSER_ROLE` on the [DAO timelock](https://etherscan.io/address/0xFe89cc7aBB2C4183683ab71653C4cdc9B02D44b7), its owner [Safe](https://etherscan.io/address/0x7101B78638e34444F0a5AdE9e1149fbEeC029931) reports a threshold of 5 over 8 owners, and the term runs to 16 July 2028, when the same expiry logic fires again. ENS did not lose its veto and did not simply renew it; it made the body re-argue its mandate in public and wrote the answer down.

## Why it matters

The episode is a textbook live case study in **plutocracy and capture**. One delegate, Lefteris Karapetsas, wrote that Johnson had "delegated ~50% of the voting supply to himself, essentially becoming the DAO," and Security Council member Brantly Millegan called the Foundation proposal "the equivalent of treasury capture by ENS Labs." It crystallizes the core problem of [token-weighted voting](/wiki/dao-governance/concepts/fundamentals/dao-governance-models): when one party can marshal a majority of active votes, the decentralized form offers little protection for everyone else — the same dynamic documented across large DAOs in 2026. ([EtherWorld](https://www.etherworld.co/ens-dao-weighs-major-governance-shift-to-empower-ens-foundation/))

## ENSv2 and the scrapped Namechain L2

Beyond governance, 2026 also reset ENS's technical roadmap. **ENSv2** — a [ground-up rewrite of the ENS contracts and architecture](https://ens.domains/ensv2) for better usability, flexibility, and developer tooling — was originally meant to live on **Namechain**, a dedicated ENS Layer-2 that ENS Labs and the [Linea Association agreed to build](https://linea.build/blog/ens-labs-and-linea-association-to-build-namechain) in December 2024. On [5 February 2026](https://www.coindesk.com/tech/2026/02/06/ethereum-s-ens-identity-system-scraps-planned-rollup-amid-vitalik-s-warning-about-layer-2-networks) ENS Labs scrapped the L2 entirely and moved ENSv2 to **Ethereum mainnet**. Nick Johnson's framing: "the landscape has changed between when we first decided to pursue an L2" — the base layer had scaled enough (ENS reports [~99% lower registration gas costs over the prior year](https://www.theblock.co/post/388932/ens-labs-scraps-namechain-l2-shifts-ensv2-fully-ethereum-mainnet) alongside Ethereum's 2025 gas-limit rise) to make a separate rollup's cost savings no longer worth its complexity, echoing Vitalik Buterin's renewed emphasis on scaling L1 itself. ENS Labs says roughly [80% of development effort](https://www.theblock.co/post/388932/ens-labs-scraps-namechain-l2-shifts-ensv2-fully-ethereum-mainnet) can now go to ENSv2's core features rather than maintaining custom chain infrastructure. It is a notable case of a DAO-governed protocol reversing a flagship architectural bet as the surrounding ecosystem shifted under it.

## How Caper approaches this

ENS shows what happens when a dominant voter can override a DAO and minority members have no clean way out. A [caper](/wiki/foundations/what-is-a-caper) responds with two design choices described on its governance pages: voting weight that grows with demonstrated [participation](/wiki/governance/voting), not stake alone, so influence is harder to simply buy or delegate to oneself; and a built-in [exit](/wiki/foundations/leaving-a-caper) right that lets any member who has voted or traded redeem a treasury share sized by that same participation-weighted vote weight rather than be locked in under a controlling party. Those mechanics are stated neutrally on the linked Caper pages.

## References

- [ENS DAO Governance Forum](https://discuss.ens.domains/).
- [ENS docs: The ENS Foundation](https://docs.ens.domains/dao/foundation/).
- [The Defiant](https://thedefiant.io/news/defi/ens-dao-delegates-governance-attack-johnson-self-delegates) — ENS delegates call the Foundation proposal a governance attack as Johnson self-delegates.
- [Cryptopolitan](https://www.cryptopolitan.com/ens-dao-governance-reform-proposal-drama/) — ENS DAO governance reform proposal drama.
- [EP 6.45 — Renewal of the Security Council](https://discuss.ens.domains/t/6-45-renewal-of-the-security-council/22145), the renewal thread carrying the mandate argument in full.
- [Establishing a new Security Council](https://discuss.ens.domains/t/executable-establishing-a-new-security-council/22272) — the executable, with the deployed contract and Safe addresses.