What Is ENS? Ethereum Name Service, .eth Domains, and ENSv2, Explained

Every crypto address is a wall of hexadecimal — 42 characters no human can read, verify, or remember, and one typo sends money into the void. ENS, the Ethereum Name Service, is the fix that stuck: it maps a name you can actually read, like alice.eth, to that address, and to a whole profile of records behind it. It launched in 2017, it's now built into virtually every wallet and dApp, and in 2026 it made one of the year's more contrarian infrastructure calls — cancelling its own Layer 2 to move back onto Ethereum mainnet. This is how ENS works, what the token does (and doesn't do), and what actually changed this year.

What ENS is and who built it

ENS is a decentralized naming and identity protocol on Ethereum. Its job is simple to state: translate human-readable names into the machine identifiers computers use — primarily Ethereum addresses, but also addresses on other chains, website content hashes, and arbitrary profile data like an avatar, an email, or a social handle. The headline product is the .eth name, but ENS also resolves imported DNS names and subnames.

It was created by Nick Johnson, a former Google site-reliability engineer, and went live in May 2017. Development is led by ENS Labs (the entity formerly known as True Names Ltd, a Singapore non-profit), and since late 2021 the protocol has been governed by the ENS DAO. That lineage matters: ENS is one of the oldest continuously-run applications on Ethereum, and it has spent nearly a decade becoming the default rather than chasing a token narrative.

The mental model most people reach for is "DNS for Web3," and it's close enough to be useful. The key difference is ownership: a .eth name lives in your wallet as an NFT you control, not as an entry rented from a registrar that can seize it.

How ENS works: registry, resolvers, and namehash

Under the hood, ENS resolution runs through two kinds of contracts. Getting this distinction right is the whole game.

• The Registry. A single, central smart contract that stores, for every ENS name, three things: the owner, the resolver it points to, and a caching TTL. The Registry is deliberately dumb — it does not store your address or profile. It only knows who owns the name and which resolver to ask.
• Resolvers. These are the contracts that hold the actual data. Point a name at a resolver, and the resolver answers questions: what's the ETH address for alice.eth? The content hash for the website? The avatar text record? Resolvers are pluggable, which is why ENS records can grow new capabilities without changing the Registry.

So a lookup is a two-step dance: a wallet asks the Registry, "what resolver does alice.eth use?", then asks that resolver, "what's the address record?" Names are organized hierarchically using an algorithm called namehash, which recursively hashes each label. That hierarchy is what makes subnames — pay.alice.eth, blog.alice.eth — work natively, each independently ownable and configurable.

Registration of .eth names goes through a registrar contract using a commit-reveal flow (you commit a hashed intent, wait, then reveal) to stop front-runners from sniping the name you're buying. The resulting .eth name is an ERC-721 NFT, which is why you can see it, transfer it, or sell it on marketplaces like any other token.

Going cross-chain with CCIP-Read

ENS resolution always starts on Ethereum mainnet, but the data doesn't have to live there. CCIP-Read (EIP-3668) lets a resolver defer a lookup to an off-chain gateway or an L2, fetch the answer, and then verify it on-chain — trustlessly. This is the plumbing that lets ENS names carry addresses for dozens of chains, and it's how L2-native naming systems plug into the ENS namespace without every user paying mainnet gas. In ENSv2, a Universal Resolver contract wraps this whole process so clients call one entry point instead of orchestrating the steps themselves.

The ENSv2 rewrite goes further than a Universal Resolver, though. It re-architects the namespace into a hierarchical registry where each name can run its own registry contract for its subnames, rather than every subname living under one monolithic contract. In practice that means a project issuing thousands of subnames — a DAO, an exchange, an app — gets direct, programmable control over how those subnames are owned, transferred, and gated. It's the difference between renting shelf space and owning the shelf.

The ENS token: governance, not fees

Here's the part people most often get wrong. The ENS token launched in November 2021 as the governance token of the ENS DAO. Its supply is fixed at 100 million, distributed as:

• 25% airdropped to accounts that held a .eth name as of 31 October 2021,
• 25% to core contributors and ecosystem partners (on vesting schedules),
• 50% to the DAO treasury.

The token's function is governance: one token equals one vote, and holders are encouraged to delegate their voting power to active community delegates. That's it. ENS is not a fee token, not a staking token, and not a claim on revenue.

That last point is the crucial one for anyone eyeing the token as an investment. You pay for names in ETH, not in ENS, and those registration fees flow to the DAO treasury — they do not accrue to token holders. Fees scale by name length to discourage squatting: roughly $5/year for a five-plus-character name, ~$160/year for four characters, and ~$640/year for three characters, all denominated in ETH plus gas. The fee's stated purpose is anti-spam first, treasury funding second. So ENS the token captures no direct cash flow; its value is a bet on governance rights over the most-used identity layer on Ethereum, and on whatever the DAO decides that role should be worth.

The numbers: scale and market position

ENS's real moat is usage, not price. As of early 2026 there are roughly 2.8 million active .eth names, and the protocol services millions of name lookups a day across the wallets and apps that integrate it. Active-name growth has cooled from the 2022–2023 frenzy to a steadier single-digit monthly pace, which is what maturity looks like.

On the market side, the ENS token trades as a mid-cap. In July 2026 it sits around $4.20, with a circulating supply near 40.9 million and a circulating market cap in the ~$170 million range (roughly rank #139 by market cap), against that fixed 100M total supply. Treat those figures as a snapshot — price moves, and the gap between circulating and total supply reflects treasury and vesting allocations that unlock over time.

The more durable "number" is distribution: ENS name resolution is a default feature of MetaMask, Coinbase Wallet, Rainbow, and effectively every serious Ethereum wallet, plus dApps like Uniswap. That ubiquity, not the ticker, is the asset. A naming standard is only as valuable as the number of clients that honor it, and by that measure ENS has no real competitor on Ethereum — it is the schema everything else reads and writes against, which is precisely why L2s and even AI-agent standards choose to extend it rather than fork their own.

The ecosystem: Basenames, DNS, and AI agents

ENS increasingly operates as shared infrastructure other projects build on rather than a standalone destination.

• Base and Basenames. Coinbase's L2, Base, runs Basenames (name.base.eth) as ENS subnames resolved via CCIP-Read from Base L2 back to mainnet. They've become the default way to send and receive on Base, and Coinbase migrated its earlier cb.id identities toward base.eth. Coinbase has cited a meaningful drop in failed transactions once human-readable names replaced raw addresses — the exact problem ENS was built to solve, at scale.
• DNS convergence. ENS supports importing traditional DNS names (.com, .xyz, .ai) so they resolve like native ENS names, historically via DNSSEC and, more recently, via tokenized-DNS integrations that skip the manual DNSSEC step. And in a notable role reversal, ENS is applying for its own .ens top-level domain in ICANN's 2026 gTLD expansion round (it can't claim .eth, which collides with Ethiopia's ISO country code), bringing the two naming worlds closer together.
• AI agent identity. ERC-8004, which went live on Ethereum in January 2026 to give autonomous AI agents on-chain identity, reputation, and validation, treats ENS names as first-class identifiers — an agent's ENS name is its human-readable handle, resolved before any reputation check. As agents proliferate, this positions ENS as their naming layer too.

How to actually use ENS

Getting started is deliberately mundane:

1. Register a name. Go to the official ENS app (ens.domains), connect a wallet, search for an available name, and register it. You'll pay the yearly fee in ETH plus gas, confirming across the two-step commit-reveal flow. Pick a duration — longer registrations save on repeat gas.
2. Set your primary name (reverse record). This is the step people skip. Setting a primary name tells apps to display alice.eth instead of your 0x… address across wallets and dApps. Without it, others can send to your name but you won't appear as it.
3. Add records. In your name's profile, set the addresses you want it to resolve to (ETH and other chains), a website content hash, and text records like an avatar, description, or social links. This is what turns a name into a portable identity.
4. Create subnames if you need them. Issue pay.alice.eth or team.alice.eth for sub-wallets, organizations, or users — each independently controllable.
5. Renew before expiry. Set a reminder. Your name is rented; if it lapses past the grace period it can be re-registered by anyone.

Risks and what to watch

ENS is mature, but "mature" is not "risk-free," and most of the danger is operational rather than protocol-level.

• Expiry is the silent killer. .eth names are rented NFTs. Miss a renewal, and after the grace period your identity — and anything that depended on it — is gone and re-registerable by someone else. This is the single most common way people lose an ENS name.
• Homoglyph phishing. Unicode look-alikes (a Cyrillic character standing in for a Latin one) let attackers register names that look identical to a trusted one. Always verify the literal characters before sending, and be wary of names shared in DMs.
• Wrong records and bad approvals. Setting a resolver record incorrectly, or approving a malicious contract over your name, can misdirect funds or hand over control. Double-check what you sign.
• Off-chain resolution dependencies. Names that resolve via CCIP-Read gateways (including many L2 subname systems) depend on those gateways being available. It's a trust-minimized design, but liveness still matters.
• Governance and token questions. ENS is DAO-governed, so voting-power concentration and delegate participation are real variables. And because the token captures no fees today, its long-term value thesis leans on future governance decisions rather than current cash flow.
• Migration risk in 2026. ENSv2 is a full contract rewrite rolling out on mainnet. Upgrades of this size carry execution risk; follow official ENS channels for migration steps and beware of fake "upgrade your name" prompts.

Bottom line

ENS won the naming layer the boring way: it shipped in 2017, made itself the default in every wallet, and let network effects compound. Its 2026 decisions reinforce that discipline — scrapping the Namechain L2 to ride Ethereum's own scaling (with ENS gas costs down ~99%), moving ENSv2 to mainnet, and reaching toward the traditional DNS world with a .ens ICANN bid rather than walling itself off. Just keep two facts straight: the token is governance, not revenue, and your name is rented, not owned forever. Understand those, and ENS is one of the clearest, most useful pieces of infrastructure in crypto.

For related reading: what is DeFi, best Ethereum L2s, account abstraction explained, and what is a crypto wallet.

Related guides

• What Is Base?
• Coinbase Wallet Guide
• Rainbow Review
• Trust Wallet Guide
• Crypto Wallets in 2026

Not financial advice. The ENS token is volatile and captures no protocol fees; always verify names, renewals, and upgrade steps on official ENS channels.