The Ethereum Name Service wants to move every .eth domain to a rebuilt system called ENSv2 — and once you migrate, there is no way back. An October 11 proposal would let the operators of the internet’s largest blockchain naming system upgrade to a new architecture, with existing domain holders allowed to stay put indefinitely or migrate permanently to the new network.
By Keisha Williams | October 13, 2026
The Architecture: A Tree Instead of a Filing Cabinet
If you have never heard of ENS, think of it as the internet’s phone book for crypto. Instead of sharing a 42-character wallet address, you can send money to something like “yourname.eth” — a human-readable name that resolves to the long string. Roughly the way “amazon.com” hides a numbered server address, .eth hides a numbered wallet.
The current registry dates back to 2017 and works like a single central filing cabinet: one contract holds every name and record. According to CryptoSlate, ENSv2 replaces that with a hierarchical structure where each domain can maintain its own separate registry for its subdomains — the names underneath it, like “wallet.yourname.eth”. In plain terms, the filing cabinet becomes a tree of smaller folders, each independently managed.
Why bother? Flexibility. The new structure lets owners assign fine-grained permissions, so a business could delegate control of specific names or records to specific teams without handing over the keys to everything. For companies and apps building on ENS, that is the difference between sharing one office password and giving each employee their own badge.
Consensus Mechanisms: The DAO Holds the Switch
Nothing happens until the ENS DAO — the token holders who govern the protocol — votes to activate the upgrade. The October 12 governance bulletin listed the vote as pending, and ENS has not announced a launch date. This is how major changes get made in decentralized systems: not by a company shipping an update, but by a community vote that the operators choose to honor.
- October 11 — the proposal to activate ENSv2 was published
- 2017 — the year the current ENS registry launched
- 60 percent — the fee increase for names with five or more characters, from 5 USD to 8 USD per year
- ~44 percent — the discount for registrations of six or more years
Network Health: The Irreversible Catch
Here is the part every .eth holder needs to understand. Migration is one-way. When an owner moves a domain to ENSv2, their existing token is transferred into a smart contract called the Graveyard — a contract that, by design, cannot return or transfer out the tokens it receives. It is a cryptographic incinerator for the old version of your name.
That sounds scarier than it is in practice — the domain keeps working under the new system — but it means the decision deserves care. Users who stay on ENSv1 keep access to their domains and continue renewing through a dedicated contract that also preserves their ENSv2 reservation. In other words, the old system is not being switched off; new registrations alone will move to ENSv2 once it activates.
Developer Ecosystem: Stablecoin Pricing and New Money Rules
The upgrade also rewrites how names are paid for. Registration and renewal payments would switch to stablecoins — USDC and DAI — replacing ETH-denominated payments and keeping fees fixed in dollar terms. For anyone who has watched a gas spike turn a 5 USD renewal into an unpredictable expense, that predictability is a quiet quality-of-life win.
The pricing itself shifts too. Annual fees for names with five or more characters rise 60 percent, from 5 USD to 8 USD, while three- and four-character names — the rare, premium short ones — stay unchanged. Longer registrations get rewarded with discounts of roughly 44 percent for six or more years. The message is simple: short names stay luxury goods, long-term holders get a break, and casual squatters pay a bit more.
Final Assessment: No Rush, but Read the Label
If you hold a .eth name, the correct move right now is patience. The DAO vote is pending, no launch date exists, and existing holders can stay on ENSv1 indefinitely while keeping renewing. Nothing is being taken away — the upgrade is being offered, not forced.
When migration does open, treat it like any irreversible blockchain action: verify you are on the official interface, understand that the Graveyard cannot give your old token back, and migrate only when you actually need the new features. For everyone else, ENSv2 is a tidy case study in how decentralized protocols evolve — slowly, publicly, and with the exit doors clearly marked before anyone walks through them.
The cryptocurrency market remains highly volatile. This article is for informational purposes only and does not constitute financial advice.
subdomain registries per domain is the change that matters. projects running hundreds of subnames finally get granular permissions instead of one admin key for everything
granular permissions per subdomain registry is the change that matters. running hundreds of subnames off one admin key was a disaster waiting to happen
One-way migration with no launch date and a DAO vote still pending. I hold three .eth names and I am in no rush. Indefinitely optional means the old registry stays the safety net.
three names here too and same plan, no rush. but check your subdomains before you wait, records on the old registrar do not carry themselves over
marta careful, optional now does not mean optional forever. Remember when ETH2 staking withdrawals were going to be painless. Once tooling and apps default to v2 the old chain slowly rots
exactly what happened with the old registrar. tooling defaulted to the new contract and legacy names became second class within a year. indefinite optional only lasts until wallet devs decide otherwise
the wallet dev line is the whole game. metamask snaps will default to v2 resolvers and suddenly your indefinitely optional name resolves wrong on half the apps you use
the eth2 withdrawals comparison is too real, i held through that wait while the timeline kept slipping. migrating my two active names early and letting the dusty ones sit on v1
a one way door with no rollback, on the system holding every .eth name. peak test in prod energy
and the DAO holds the switch, nothing activates until token holders vote. expect months of forum arguing before anyone moves anything
every ens upgrade ships as opt-in then becomes load bearing. id bet mainnet migration completes before half the dao notices
before the dao notices is the pessimistic read. optimistic one is tooling slowly defaults to v2 like the old registrar and migration happens by osmosis
The 2017 registry holding every name in one contract was always the fragile part. A tree of independent registries is overdue. Hope gas for migrating cheaper names is not brutal.
The indefinite opt-out is the only reason this proposal is tolerable. Forced migration would split the namespace overnight.
dao vote pending, no date, permanent migration. sounds like a chill q1 2027 problem for me honestly
q1 2027 problem until the default resolver flips and your wallet app starts nagging weekly. opting in happens to you eventually
the weekly nag scenario is exactly it. first wallet update that defaults v2 resolvers and opting in happens to everyone at once, queue the forum meltdown
Everyone argues about the one-way door and skips the actual upgrade. Per-domain subregistries mean granular permissions, the first structural fix to the 2017 single contract design.
Granular permissions are the real story here. I manage 30 subdomains and delegating them one by one today is a weekend job I keep postponing.
30 subnames under one admin key is exactly the pain v2 fixes. delegating them individually saves you that postponed weekend even if the parent name never migrates
granular permissions yes, but the migration tooling better support bulk moves. doing 30 subnames by hand is that postponed weekend job again with extra steps
bulk tooling decides this whole thing honestly. per name migration for anyone running dozens of subnames means v2 stays half empty for a year no matter what the dao votes
same 30 subname backlog here. my plan is scripting the record export now while v1 still resolves everything, dao vote or not
one way door plus a pending dao vote plus no launch date. correct move is doing nothing until wallets start warning you, then migrate the names you actually use first
the indefinite opt out only protects you if the old registrar keeps getting patches. watch the commit activity on v1, the day it goes quiet the door starts closing itself