ENS prints cash in ETH. ENS the token prints governance votes.

Ethereum Name Service is one of the rare “real product” protocols in crypto that charges straightforward fees for a service people actually use. The service is the .eth registrar plus a broader set of naming and resolution contracts. The token, ENS, sits in a different lane. It is a governance instrument for the ENS DAO, not a usage token.

ENS names are registered and renewed by paying fees in ETH, with pricing expressed in USD terms via an onchain pricing oracle. Those protocol fees are routed to the ENS treasury rather than to tokenholders. The ENS token’s economic exposure is therefore indirect: it governs the machinery that sets parameters and allocates the treasury, but it does not come with an explicit claim on fees or profits.

Official docs are clear about what the token is meant to do: each ENS token maps to a single governance vote, and tokens must be delegated before they can be used in a vote, per the ENS token docs.

From a TradFi realist angle, that split matters. If you want to value ENS like an equity, you immediately hit a wall. Fee revenue accrues to a treasury controlled by governance. It does not automatically accrue to tokenholders. If you’re mapping those value flows to a token model, our guide to design components is a useful checklist.

Supply, distribution, and the quiet inflation lever

ENS launched its DAO and token on November 8, 2021. At launch, 100,000,000 ENS were minted.

Some market data sites list a max supply of 100,000,000. Treat that as “initial minted supply” rather than a guaranteed hard cap, because ENS DAO documentation also states the DAO can mint more under a governance-controlled policy.

Initial allocations (as documented by ENS DAO):

The airdrop itself is useful context for today’s holder base and governance dynamics. ENS states over 137,000 addresses were eligible, the claim window ran from November 8, 2021 to May 4, 2022, and 19.6 million ENS were claimed by 103,000 eligible addresses during that window. For a practical framing on how teams communicate these mechanics (without overpromising), see our guide on how to launch a token.

Unclaimed airdrop tokens did not disappear. ENS DAO documentation says the remaining 5.4 million ENS were transferred to the DAO treasury after the claim window closed.

The part many investors gloss over is inflation optionality. ENS DAO documentation states that, as owner of the ENS token contract, the DAO has the right to mint up to 2% of the current total supply, once per year, with a one-year wait between mint actions. That is not runaway emissions. It is still a meaningful governance-controlled dilution lever, and it weakens “fixed supply” narratives.

Revenue engine: .eth registration, renewals, and premium auctions

ENS protocol revenue primarily comes from the .eth registrar, via registration fees and premium name fees, as described in the protocol revenue docs.

Two structural points are doing most of the work here.

1) Pricing is “USD-denominated” but paid in ETH. The ETH registrar docs describe registration fees paid in ETH, routed to the ENS treasury, and also document the pricing oracle mechanism used to express pricing in USD terms.

2) Short names are intentionally expensive. ENS DAO documentation lists annual prices of $640 for 3-character names, $160 for 4-character names, and $5 for 5+ character names. ENS documentation also states the minimum length is 3 characters.

Expired names do not immediately become free-for-all loot. ENS DAO documentation describes a 90-day grace period after expiry. After that grace period, a name enters a temporary premium auction with a declining premium over 21 days, starting at $100,000,000 and decaying to zero.

ENS provides some historical revenue figures in its own DAO documentation. It states ENS started generating revenue from name registrations on May 4, 2019, generated 2,000 ETH in 2019, and that as of October 2024 ENS had generated 43,800 ETH in revenue since launch. Those figures are explicitly time-stamped in the documentation. They should not be treated as “current” as of March 5, 2026.

The tokenomics implication is simple. ENS has a real fee stream. It is not paid in ENS, and it is not algorithmically shared with ENS tokenholders. For another example of how token design choices shape who captures value, see our SNX tokenomics review.

Treasury plumbing: controllers, wallet.ensdao.eth, and the endowment

ENS’s fiscal flows are contract-mediated, which is good. It reduces “trust me bro” risk, and it makes treasury policy legible onchain.

ENS DAO documentation states that all revenue generated by the registration of .eth ENS names goes to smart contracts that are controlled by the ENS DAO. The ETH Registrar documentation describes the path more mechanically (controller contracts that forward funds to the treasury), with anyone able to call a withdrawal function to trigger transfers.

The contracts documentation also describes wallet.ensdao.eth as the treasury contract, and states that ETH is sourced from controller contracts that handle registrations and renewals, with Ether only withdrawable from controllers to the DAO treasury contract.

That flow has a governance consequence. If governance can change controllers, fee routing, or withdrawal permissions through executable proposals, ENS tokenholders are effectively steering the protocol’s cash flows. They are not receiving them by default.

ENS has also taken steps to professionalize treasury longevity via an endowment structure. ENS DAO documentation states the endowment was initiated on March 7, 2023 with an initial tranche of 16,000 ETH, transferred from the DAO wallet to the endowment wallet after an executed proposal. The same documentation states the endowment wallet is controlled by the DAO and managed by Karpatkey.

If you are trying to model ENS as an asset, this endowment move is double-edged. It lowers operational tail risk for the protocol. It also further cements that fee revenue is treated as public-goods funding capacity, not as distributable earnings to tokenholders.

Governance: delegated voting, execution, and the Security Council veto

ENS governance is token-weighted and delegation-first. Mechanically, tokens must be delegated prior to the start of a vote to count, and each ENS equals one vote.

Mechanically, ENS uses two primary voting surfaces:

Social proposals run offchain via Snapshot. ENS DAO documentation states social proposals are open for 5 days and are gasless, and that a delegate needs 10,000 ENS delegated to put a social proposal forward.

Executable proposals are binding and happen onchain. ENS governance docs state executable proposals have a 1% quorum and require 50% approval to pass, and that after submission there is a 7-day voting period followed by a 2-day timelock before execution. The same docs specify that you must ensure at least 100,000 ENS is delegated to your address to submit an executable proposal (or use a delegate who meets the threshold).

ENS also constrains itself via a constitution. For example, the ENS constitution states governance must not impose a fee for claiming DNS domains inside ENS because it would be “purely an income generating measure” rather than an incentive mechanism. That kind of constraint matters for token valuation. It limits governance’s ability to opportunistically maximize fee extraction, which can be philosophically coherent and financially limiting at the same time.

The biggest practical governance risk in DAOs is voter apathy against a large treasury. ENS explicitly acknowledges this by adding a veto layer.

ENS DAO documentation describes the Security Council as a 4-of-8 Safe multisig with a limited mandate to cancel malicious proposals that threaten the DAO, particularly those that would compromise the treasury. Its cancel authority is also explicitly time-limited and can be permanently disabled after expiration via an onchain call.

Risk register (ranked) and dominant risk

The ENS protocol has a clean revenue model and a defensible product moat. The ENS token has a different profile: it is governance on top of that machine, without direct cash flow rights. The risks below are ranked by how quickly they can impair the asset’s value proposition or the protocol’s ability to operate.

Top 3 risks

  1. Governance capture against a large, visible treasury. Trigger: sustained low voter participation and concentrated delegation, especially around contentious executable votes. Mechanism: an attacker or cartel accumulates voting power (spot holdings, delegated blocs, or borrowed influence where possible), passes an executable proposal, and uses governor-controlled execution paths to redirect treasury assets or alter critical contract permissions. ENS has a mitigation layer, but the Security Council’s role is narrow and time-limited. Who bears it: ENS tokenholders (governance credibility premium collapses), ENS users/nameholders (protocol instability), and the DAO treasury itself. Indicators: proposal vote participation rates, delegate concentration, frequency of close-margin executable votes, and monitoring whether the cancel role remains active or gets renounced after expiration.
  2. Revenue volatility versus fixed governance spend. Trigger: downturns in .eth registration and renewal demand, or prolonged ETH price drawdowns that reduce real purchasing power of treasury inflows. Mechanism: ENS revenue is generated from registrations and premium fees on .eth names and is used to fund development and other public goods, so a revenue shock can pressure budgets and slow delivery. Who bears it: primarily the DAO’s operating capacity (working groups, grants, core development), secondarily tokenholders via reduced “governance franchise” expectations. Indicators: protocol revenue dashboards cited by ENS (Looker Studio / Dune), renewal rates, and DAO treasury runway assumptions embedded in budget proposals.
  3. Pricing/oracle and parameter risk. Trigger: misconfigured price parameters, oracle malfunction, or governance-driven price policy swings for short names and premiums. Mechanism: ENS prices are derived via a pricing oracle and length-based schedule, and paid in ETH. If oracle inputs or parameters are wrong, rent can become too cheap (inviting squatting) or too expensive (choking adoption), and the user experience can degrade due to ETH/USD volatility and slippage expectations. Who bears it: name registrants (unexpected costs, failed registrations), the DAO (revenue instability), and the ENS brand (trust hit). Indicators: sudden divergence between expected USD pricing and actual paid ETH, abnormal premium auction outcomes, and emergency governance actions around controllers/oracles.

Dominant risk: governance capture is the one that can break everything fast.

ENS has real assets worth stealing. The protocol routes registration funds to DAO-controlled smart contracts, and those controller contracts can withdraw ETH to the DAO treasury. That treasury is then spendable via governor-enabled execution.

So the attack surface is not theoretical. It is the same one that has haunted every large-token DAO since 2020: low attention, high stakes. ENS’s own documentation frames the Security Council as a response to vulnerabilities stemming from low voter participation relative to treasury size.

The mitigation is helpful but imperfect.

First, the Security Council is not a general “guardian.” It cannot initiate governance actions. It can only cancel malicious proposals. That is intentionally narrow, but it also means you are relying on timely detection and coordinated action by eight individuals under pressure.

Second, the cancel authority is time-limited and can be permanently disabled after expiration via an onchain call. That is philosophically aligned with decentralization. It also reopens the classic risk if governance participation does not improve structurally.

Third, even without outright theft, capture can express itself as slow corrosion. Governance can redirect spend to insiders, fund pet initiatives, or set policies that weaken protocol legitimacy. Those outcomes do not always violate a constitution. They can still impair the token’s perceived “franchise value,” which is most of what ENS represents financially because it does not automatically receive fees.

In practice, ENS tokenholders are underwriting a governance system that controls a revenue-producing public good. The upside is influence over one of the most important identity primitives in Ethereum. The downside is that governance itself becomes the product. When governance fails, the token has little else to fall back on.

If you’re building or revising a protocol token economy design, the ENS case is a useful reference point for how to separate protocol revenue from tokenholder payouts without pretending they are the same thing. If you need help stress-testing that design trade-off, that’s squarely in the lane of tokenomics design services from an advisor who models fiscal flows as financial claims rather than vibes.



This article is part of our Tokenomics Deep Dive series.