ENSv2: A Shorter Grace Period, the Same Release Date
ENSv2 shortens .eth grace from 90 days to 28 and adds 62 days at upgrade. The arithmetic preserves a release boundary, while resolution can stop before exclusivity ends.

AI-generated conceptual illustration: a reader shifts the divider between two joined periods while the final stop stays fixed. This represents the published transition rule, not an ENS interface or a particular name’s status.
Key Points
- ENSv2 .eth names have 28 days of grace after expiry; names still on ENSv1 have 90. During grace, v2 names stop resolving, while v1 names keep working.
- A successful upgrade adds 62 days once and shortens grace by 62 days. With no separate renewal changing the term, the release boundary stays in the same place.
- During grace, anyone can renew the name for its existing owner. After grace, anyone can register it during Price Cooldown; the former owner has no priority.
Inside this story
Chronological Timeline
ENS Labs announces ENSv2 on Ethereum mainnet and says existing names keep working, with an optional upgrade path.
The expiry and upgrade pages show November 3 update times. Read on November 4, they distinguish 28/90-day grace and the one-time 62-day extension.
One name, more than one deadline
An ENSv2 .eth name can stop pointing to an address while still being unavailable for someone else to register. That is the useful distinction behind the new grace period. ENS Labs announced ENSv2 on Ethereum mainnet on October 27, 2026. Its support documents, checked on November 4, describe a shorter window after expiry without an earlier release date for an otherwise unchanged registration upgraded from v1.[1][2]
The launch did not automatically move every existing name into the new rules. ENS says existing names continue to work and do not need to be registered again. Its upgrade guide describes an optional transition with no deadline and lists names the current app cannot yet upgrade. A rule for an upgraded name and a rule for one still on ENSv1 can therefore coexist.[1][3]
Expiry stops resolution before it opens registration
For an ENSv2 .eth name, expiry starts 28 days of grace. During that period the name stops resolving: it no longer points to the wallet or other records until renewed. For a name still on ENSv1, grace lasts 90 days, and the name keeps working during that window. The version changes both the length of grace and what the name does while in it.[2][4]
Both versions keep an important boundary: nobody else can register the name during grace, and it cannot be transferred then. Renewal brings it back to its existing owner. Resolution—the lookup that returns the name’s destination—and exclusivity against another registration are separate states. An inactive v2 name is not, for that reason alone, available to a stranger.[2][4]
Where the missing 62 days go
The upgrade changes both sides of the expiry boundary. ENS says it adds 62 days to the registration once, while grace falls from 90 to 28 days. For an unexpired v1 name with no separate renewal, let its old expiry be E. Its former release boundary was E + 90 days. After upgrade, expiry becomes E + 62 days, followed by 28 days of grace: 62 + 28 = 90. This is an illustration of the documented rule, not a lookup of an individual name.[2][3]
The extra 62 days are a one-time transition adjustment, not a recurring extension. The simple comparison also assumes no other change to the registration term. For a name already in grace, the ENS App first renews it and then upgrades it. That renewal changes the expiry baseline, so the resulting date cannot be explained by adding only 62 days to the old date.[2][3]
Renewing a term does not buy control of the name
During grace, anyone can pay to renew a name, but that does not make the payer its owner. ENS says renewal returns the name to its existing owner and never changes ownership. The added term is measured from the old expiry date, not the day someone submits the renewal. Those are different questions: who may extend the term, who controls the name and where the renewed period starts.[2][4]
The 62-day calculation also does not promise that every name can use the current upgrade flow. The guide lists exceptions, including Safe-held names and names whose subnames have further subnames. The relevant condition is a completed, eligible upgrade. Reading the mainnet announcement does not establish that any particular name has moved to v2.[3]
Price Cooldown is already open to other registrants
When grace ends without renewal, the old renewal path closes. The name enters Price Cooldown, when anyone can register it at the normal price plus a declining premium. ENS describes a 21-day cooldown, after which the premium reaches zero. That is not another 21 days reserved for the former owner: registration is already open, and the former owner has no priority.[2][4]
The practical reading of a date therefore needs three pieces of context: which version the name uses, when its registration expires and when protection against a new registrant ends. The upgrade’s 62-day adjustment preserves the last boundary in the simple unchanged-term case. It does not erase expiry, make a stopped name work throughout grace or restore priority after release. The useful change to understand is how those states fit together, rather than one shorter number in isolation.[2][3][4]
Continue reading
Explore the topic through other cases and contexts.
Sources & References
- [1]Source 1: ENSv2 Is Live on MainnetENS Labs · 2026-10-27Accessed 2026-11-04
- [2]Source 2: Expiry & grace period — updated November 3ENS SupportAccessed 2026-11-04
- [3]Source 3: Upgrade your name to ENSv2 — eligibility and one-time extensionENS SupportAccessed 2026-11-04
- [4]Source 4: .eth name lifecycle — grace and Price CooldownENS SupportAccessed 2026-11-04

