ENSv2 is the major infrastructure upgrade for the Ethereum Name Service. It is a rewrite of how the protocol handles name ownership, registration, and management, with the goal of making ENS cheaper to run, easier to extend, and more flexible for both individual owners and large projects.

What should I check if I hold names?

Confirm which contracts your names live on and whether any action is required on your side. Wrapped names and names you manage on behalf of a project deserve particular attention, and it is worth following the official migration guides closely.

Why does a Layer 2 matter for ENS?

Mainnet gas has historically been one of the biggest practical frictions for ENS users. Registering a name, setting records, and managing subnames all cost gas, and those actions get expensive fast when gas spikes. Moving the operational layer to a Layer 2 makes routine actions cheaper and more predictable.

ENSv2 and the Namechain: Where Name Migration Stands

Q: What is the Namechain?

The Namechain is a Layer 2 network purpose built to host the ENS registry. Moving day to day registration and management onto a Layer 2 reduces costs and congestion on mainnet, while Ethereum mainnet stays the secure root that everything ultimately resolves through.

Q: Will my existing .eth name keep working during migration?

For most holders the migration is designed to feel seamless. Names should keep working, resolution should keep working, and renewals should keep working. The complexity sits behind the scenes in how the protocol routes registration and management calls.

ENSv2Read time: 5 min

ENSv2 is the biggest infrastructure change the Ethereum Name Service has undertaken. This is a plain English look at what it is, what the Namechain does, and what migration means in practice for people who hold a name.

What ENSv2 actually is

ENSv2 is the big infrastructure upgrade for the Ethereum Name Service. It is a rewrite of how the protocol handles name ownership, registration, and management. The goal is to make ENS cheaper to run, easier to extend, and more flexible for both individual owners and large projects.

One of the most visible parts of ENSv2 is the deployment of the Namechain, which is a Layer 2 network purpose built to host the ENS registry. The idea is that moving the heavy day to day operations of name registration and management onto a Layer 2 reduces costs and congestion on the main Ethereum chain, while keeping Ethereum mainnet as the secure root that everything ultimately resolves through.

What this means for existing .eth owners

For most people holding a name like alice.eth, the migration is designed to feel seamless. Names should keep working, resolution should keep working, and renewals should keep working. The complexity lives behind the scenes, in how the protocol routes registration and management calls.

That said, any migration of this scale deserves a careful read of the official migration guides. If you hold names, especially wrapped names or names you manage on behalf of a project, it is worth confirming which contracts your names live on and whether any action is required on your side.

If wrapped names are part of your holdings, read wrapped names explained before you act.

Why Layer 2 matters for ENS

Gas prices on Ethereum mainnet have historically been one of the biggest practical frictions for ENS users. Registering a name, setting records, and managing subnames all cost gas. When mainnet gas spikes, those simple actions get expensive fast.

Moving the operational layer onto a Layer 2 changes that math. Routine actions become cheaper and more predictable. This is the same reasoning that pushed much of the wider Ethereum ecosystem toward Layer 2s, and it is why the Namechain matters for the long term health of the namespace.

What to watch

A few things worth tracking as ENSv2 rolls out:

Official migration timelines and any announced cutover dates
Whether wrapped names (ERC-1155) carry over cleanly or need an action
Subname behaviour, especially for projects that manage many subnames
Renewal and grace period mechanics under the new infrastructure
Any governance proposals that fine tune parameters after launch

For the current state of the namespace and the renewal mechanics that will carry over, see the ENS grace period.

The bottom line

ENSv2 is a change of plumbing rather than a change of purpose. The name you hold should behave the same. What changes is the cost and predictability of the actions around it, and that is the part worth following.

Next steps

Read what ENSv2 is for the fundamentals, or return to the ENS learning hub for the full set of guides.