All posts
Guide 30 June 2026Updated 2 November 2026 9 min read

ENSv2: what changes for name holders (and what doesn't)

ENSv2 is live on Ethereum mainnet: a hierarchical registry, role-based permissions, USDC pricing with multi-year discounts, a 28-day grace period and an optional upgrade for existing names.

Updated 27 October 2026: ENSv2 is live on Ethereum mainnet. New .eth registrations are ENSv2 names, paid in USDC in the official ENS App. Names you haven’t upgraded keep working and can still be renewed. Upgrading is optional and has no deadline. The Sepolia sections below describe the earlier public testing period.

ENSv2 is the largest protocol change in ENS history. It keeps resolution compatible while replacing the flat registry, shared ownership model and optional NameWrapper with hierarchical registries, per-account resolvers and granular roles.

One correction matters because older explainers still circulate: ENSv2 was originally planned for a dedicated L2 called Namechain. ENS Labs cancelled that plan in February 2026. ENSv2 launched directly on Ethereum mainnet in October 2026, after public testing on Sepolia.

What the Sepolia Public Beta tested

The Beta is a fresh Sepolia deployment. Names created during the earlier Alpha do not appear in the new registry, so Alpha testers start again. The official ENS App and ENS Explorer now support:

  • the first public ENSv1-to-ENSv2 upgrade flow for eligible Sepolia names;
  • new registration and renewal flows with test USDC or mockUSDC;
  • permissioned resolvers with per-name and per-record roles;
  • hierarchical subname creation and deletion;
  • primary-name changes, flexible expiry dates and renewal reminders;
  • a price-cooldown view for recently expired names; and
  • richer registry, token, contract and transaction inspection.

The contracts remain experimental. The normalization upgrade framework is not in this Beta, and payment tokens have no monetary value. Use the official testing surfaces for transactions.

What changes under the hood

Hierarchical registries

ENSv1 records every name in one flat registry. ENSv2 lets each name point to its own subregistry. A parent can choose the ownership, renewal and transfer rules for its namespace without forcing those rules on unrelated names.

Permissioned resolvers replace broad manager access

Standard ENSv2 accounts get their own resolver proxy. Roles can be scoped across a resolver, to one name, or to one record type. A company could let finance change payment addresses while a communications team changes only the avatar and description.

Names become ERC-1155 tokens in per-name registries

ENSv2 token IDs can change when roles change, preventing old approvals from leaking into a new permission state. Marketplaces and indexers must key names by labelhash and registry context, not assume one stable token ID in a single collection.

A shorter lifecycle and new prices

Upgraded names receive 28 days of grace; legacy names retain 90 days. The upgrade adds 62 days to the recorded expiry, preserving the release deadline. ENS.Tools reads that expiry directly and does not add another adjustment. The 21-day price cooldown follows grace.

Published launch rent is $8 annually for names of five or more characters, $160 for four and $640 for three. Adding two full years receives a 12.5% discount; three to five years receive 31.25%, and six or more 43.75%. Premium charges are separate. Mainnet transaction quotes remain authoritative. Payment uses supported stablecoins. Gas included by the official ENS App is specific to that service; ENS.Tools shows its own route and fees.

Read the official launch pricing and lifecycle guidance.

What does not change for app developers

Forward resolution, text records, avatars and primary names keep the same public interfaces. Apps using current versions of viem, ethers, ENSjs, web3.py or web3j automatically query the canonical Universal Resolver. CCIP-Read remains essential for offchain and L2-backed records.

ENSv1 names that have not upgraded continue resolving through a mirror resolver. Read-only apps generally do not need to detect whether a name has migrated. Write flows do: the app must look up the name's current resolver and respect its roles instead of assuming one shared Public Resolver address.

How migration actually works

Existing names are premigrated into ENSv2 as RESERVED slots. The owner later claims the slot by transferring the v1 token to the appropriate migration controller. Unwrapped and unlocked names use one controller; locked NameWrapper names use another so their burned fuses can be converted into equivalent v2 roles.

Migration is not purely cosmetic. Most names choose a new v2 resolver and may need records copied; locked names with CANNOT_SET_RESOLVER preserve their v1 resolver under special rules. Use the official upgrade interface, which can inspect the token and construct the correct path.

There is no need to upgrade immediately, but “do nothing forever” is not a sound plan. Since launch, new v1 registrations and normal v1 renewals are disabled. You can’t upgrade during the grace period, so renew first. Upgrading adds 62 days to the expiry to offset the shorter 28-day grace period. Reserved names renew through a dedicated compatibility renewer and continue resolving until they eventually expire.

What ENS.Tools supports since the mainnet launch

  • USDC renewals for ENSv1 and ENSv2 names in one checkout. Each name is routed to the contract that renews it, the multi-year discount is applied, and ENS.Tools adds no fee. How it works.
  • An ENSv1 / ENSv2 badge on every domain page, with that name's grace period, how it renews and whether it can be traded.
  • Reminders that know the grace period. Notifications, calendar exports and calendar feeds use 28 days for ENSv2 names and 90 only for confirmed ENSv1 names. Why it matters.
  • Our own ENSv2 index. ENS.Tools indexes the ENSv2 registry directly, and Market Pulse counts registrations through the new ETHRegistrar.
  • Safer trading. When a name upgrades, its ENSv1 token is retired, so existing listings and offers on it end automatically.
  • Canonical resolution. Current viem and ethers, the Universal Resolver proxy and CCIP-Read are all in place.
  • Official handoff. Registration and upgrades run in the official ENS App. Advanced roles and subnames use ENS Explorer.

New prices and discounts are in our ENSv2 pricing guide.

Renew your names in USDCInspect a name in ENS.ToolsOpen the ENS App

Related — also tagged Guide