Ethereum Name Service has queued an upgrade that would shut its old registry to new name registrations, moving all new activity onto a replacement system. The migration is irreversible once executed and carries no deadline. Some names aren't included in the automatic reservations that would carry them over to the new system.
A one-way door with no closing time
The absence of a deadline is the detail that stands out. Most protocol migrations come with a countdown attached — a window in which users are expected to move, after which the old system goes dark. ENS isn't doing that here. The old registry simply stops accepting new names at a point of the protocol's choosing, and there's no going back once the upgrade executes.
That leaves existing registrations in an odd limbo. They aren't being deleted, per the facts available, but the door to the old system is being pulled shut behind them. Anyone expecting a grace period to migrate at their own pace should read the proposal carefully.
The names left out of reservations
Not every name crosses over automatically. Some are excluded from the reservations that would otherwise carry them into the new registry, which means the holders of those names may need to act for themselves. ENS hasn't specified which names fall into that bucket in the material available.
Reservations are the quiet plumbing of any namespace migration. When they work, users never notice. When a set of names is left out, the affected holders are the ones who find out the hard way — usually after the cutoff has passed.
What the registry actually does
ENS names are how wallets, dapps, and increasingly other chains resolve human-readable addresses. The registry is the contract layer that records who owns what. Swapping registries is less a cosmetic change than a rewiring of the ownership books, which is why an irreversible cutover draws attention from anyone holding a name they consider permanent.
The upgrade has been queued, not executed. That distinction matters: queued changes can still be adjusted before they go live, and the reservation list is the most likely place for that adjustment to happen.
What holders should watch
The practical question for ENS holders is whether their name sits in the excluded set. ENS hasn't published a definitive list in the facts available, so the answer isn't yet clear for everyone. Names registered through the standard flow are the least likely to be affected; the edge cases are the ones to check.
There's also the timing question. With no deadline attached, there's no obvious moment at which holders are forced to move — which sounds generous until you realise it also means there's no warning bell. The old registry closes when it closes.
ENS is expected to publish further detail on the reservation exclusions before the upgrade executes. Until then, the safest read is that the cutover is coming, it's permanent, and the list of names that won't cross over automatically is the thing to pin down first.
