Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteiTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
You cannot perform a production migration of a real ENS name to ENSv2 yet. As of October 17, 2026, ENS identifies the v2 app and explorer as Sepolia testnet tools. Real names remain managed through the ENS App on Ethereum Mainnet, and ENS has not announced a mainnet launch date or final production migration interface. The safe course is to prepare your name, test only on Sepolia, and wait for an official ENS launch announcement before signing a mainnet transaction.
ENS announced the public beta on August 12, 2026, calling it the last major public testing phase before mainnet and saying timing would depend on the results. In February 2026, ENS also said ENSv2 would deploy exclusively on Ethereum Layer 1 and that development of Namechain had stopped. Older guides that describe Namechain as the destination are therefore obsolete.
What ENSv2 migration is—and why the timing matters
ENSv2 changes the registry and controller architecture used by ENS names, but the documented migration is not an automatic conversion of every name at a single launch moment. It is a two-phase process: ENS first reserves eligible v1 names, then the current owner or an approved operator authorizes a one-way token transfer that completes migration.
That distinction matters because a reservation is not ownership. During reservation, a name has a slot in the v2 ETH Registry but no v2 owner. An ENSV1Resolver fallback keeps the reserved name resolving through v1 while it remains in that state. Ownership, resolver behavior, fuse restrictions, expiry, and parent-name status all affect what happens next.
#1 Best Overall
- Effortlessly build your crypto portfolio via the all in one Ledger Wallet app: buy, sell, send, receive, swap, stake and more across popular blockchains. 15,000+ coins & tokens in a single dashboard. Keep a close eye on the market. Compare service providers. Track performance. Get timely alerts. Build your portfolio with confidence.
- Enjoy Bluetooth connectivity, iOS access, and hours of battery use with this mobile-first, secure backup signer. Freedom you can depend on.
- Genuine Check: confirm your signer is authentic during setup with the Ledger Wallet app.
- Protect your signer: keep it in mint condition at all times with a bespoke Pod or Case to avoid scratches and everyday wear and tear.
ENS Docs states, “Migration is not required immediately.” That does not mean an owner can ignore expiry. A name in the v1 grace period has a specific renewal requirement, and an unrenewed reserved name can eventually expire. It means there is no need to rush a valuable mainnet name into an unfinalized production path.
Current availability: Sepolia beta, not a mainnet procedure
ENS Support currently describes the ENSv2 app and explorer as Sepolia testnet services. Sepolia transactions use testnet assets and test registrations; they do not migrate or manage the corresponding real name on Ethereum Mainnet. The existence of a beta interface is not evidence that a production migration contract or mainnet frontend is open.
- Real mainnet names: continue to be managed through the existing ENS App on Ethereum Mainnet until ENS announces otherwise.
- ENSv2 beta: use Sepolia for testing and learning the flow. Treat the beta as experimental, not as a way to move a valuable mainnet name.
- Launch date: ENS has not published a confirmed date. The August 12, 2026 announcement says timing will follow public-testing results.
- Production UI: the owner-facing guide says a frontend migration tool will be available when the time comes, but current support does not establish that a mainnet tool exists.
Before taking any mainnet action, check a current ENS launch announcement, the ENS Support status for the v2 app, and the production ENS interface. Do not rely on an old tutorial that presents a Namechain destination or gives a mainnet transaction sequence.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
How the documented two-phase migration works
Phase 1: automatic premigration reservation
Premigration batch-reserves registered v1 names and names that are in the v1 grace period in the v2 ETH Registry. The reservation records the slot but does not assign a v2 owner. While the reservation is active, ENSV1Resolver provides wildcard fallback so the name continues resolving through v1.
The reservation also adds approximately 62 days to the v1 expiry when the v2 reservation is created. This bonus is designed to align the reservation’s availability with the end of v1’s longer grace period; it is a protocol time constant documented by ENS, not a promotional extension or an independent statistic.
Phase 2: owner-authorized token transfer
After reservation, the current v1 token owner—or an approved operator—transfers the v1 token to the controller appropriate to the name’s type. The controller promotes the reservation to a registered v2 name and sends the v1 token to the Graveyard. The v2 owner can be a different address from the v1 owner, so migration can move control to a new wallet or a smart account.
Migration is one-way. ENS’s CLI documentation labels the tool not production-ready, requires the name to be reserved first, and advises testing on Sepolia before migrating valuable names. There is no documented rollback that returns a migrated name to its former v1 state.
Rank #2
- Simply & securely take control of your digital assets and identity with the all-in-one Ledger Wallet crypto app and Ledger Flex touchscreen signer.
- Digital asset control at your fingertips: manage 15,000+ crypto across multiple chains. Earn rewards. Top up & share with ease. Explore DeFi with confidence. Collect and showcase NFTs. Make informed choices with clarity.
- Connect effortlessly with Ledger Wallet: pair your secure Ledger signer with the all in one Ledger Wallet crypto app to manage thousands of digital assets across multiple devices and accounts with Ledger Sync from a single, secure dashboard.
- Cutting-edge design: monitor the market, compare rates, and Clear Sign transactions on the secure, high resolution, 2.8'' E Ink touchscreen.
- This is what security feels like: Ledger touchscreen signers all come with a private, offline, PIN-protected backup, Ledger Recovery Key, to never lose access to your assets.
Identify your name type before choosing a route
The controller and required checks depend on whether the name is wrapped, locked, a second-level .eth name, or a subname. The following table summarizes the documented routes.
| Name state | Documented route | Important conditions |
|---|---|---|
| Unwrapped .eth second-level name | UnlockedMigrationController | Migration data specifies the label, new owner, resolver, and subregistry. |
| Unlocked wrapped .eth second-level name | UnlockedMigrationController | CANNOT_UNWRAP must not be burned. The name is unwrapped to the Graveyard during migration. |
| Locked .eth second-level name | LockedMigrationController | V1 fuses become v2 roles and a WrapperRegistry is deployed as the subregistry. A burned CANNOT_TRANSFER prevents migration; a burned CANNOT_APPROVE combined with a non-null token approval can make the transaction revert. |
| Locked emancipated subname (3LD or deeper) | Transfer to the parent’s WrapperRegistry after the parent migrates | V1 fuses convert to v2 roles. The parent must already have a v2 registry. |
| Detached emancipated subname (3LD or deeper) | Transfer to the parent’s WrapperRegistry after the parent migrates | The subname is unwrapped to the Graveyard. CAN_EXTEND_EXPIRY adds renewal roles. |
| Unlocked 3LD or deeper name | Direct v2 registration after the parent has a v2 registry | It cannot use the unlocked migration-controller path. |
| Non-emancipated 3LD or deeper name | Direct v2 registration after the parent has a v2 registry | It also cannot migrate through the migration controllers. |
Unwrapped and unlocked second-level .eth names
An unwrapped .eth second-level name follows the UnlockedMigrationController route. The transfer data identifies the label, intended v2 owner, resolver, and subregistry. An unlocked wrapped .eth name uses the same controller, but only when CANNOT_UNWRAP is not set. The documented flow unwraps that name to the Graveyard as part of migration.
Locked second-level .eth names
A locked .eth second-level name uses the LockedMigrationController. ENS converts v1 fuses into v2 roles and deploys a WrapperRegistry as the subregistry. A burned CANNOT_TRANSFER fuse blocks migration outright. Another edge case is a burned CANNOT_APPROVE fuse together with a non-null token approval; ENS warns that this combination can cause the migration to revert. Review both fuses and the token’s approval state before signing.
Locked and detached subnames
A locked emancipated subname cannot migrate independently. Its parent must migrate first, creating the parent’s v2 registry; the subname token is then transferred to that parent’s WrapperRegistry, with fuses converted to roles.
Free tools Windows power users keep installed
One-click scans. No signup required.
A detached emancipated subname follows the same parent-first dependency. The documented flow unwraps the subname to the Graveyard. If CAN_EXTEND_EXPIRY is present, it contributes renewal roles in v2. A subname owner should therefore verify the parent’s migration state, the parent WrapperRegistry address, and the resulting roles before attempting a transfer.
Unlocked and non-emancipated subnames
Unlocked 3LD-or-deeper names cannot use the unlocked second-level controller path. ENS says they must be registered directly in v2 after the parent has a v2 registry. Non-emancipated subnames likewise require direct v2 registration after the parent is ready. They are not handled by the migration controllers described for second-level names.
What to check before you do anything
Use this checklist to classify the name and prepare the information that the documented migration data requires. It is preparation for the eventual official interface, not a substitute for that interface.
Rank #3
- More than just crypto: confirm your device is authentic with Genuine Check, manage all your logins with Ledger Security Key, detect common scams with Transaction Check and more.
- Industry-defining security: battle-tested by the Donjon's white hat hackers, protected by the Secure Element, and powered by Ledger OS.
- Connect effortlessly with Ledger Wallet: pair your secure Ledger signer with the all in one Ledger Wallet crypto app to manage thousands of digital assets across multiple devices and accounts with Ledger Sync from a single, secure dashboard.
- Playful, user-friendly design: monitor the market, compare rates and Clear Sign all transactions on the secure 2.8'' anti-glare, scratch-resistant touchscreen.
- This is what security feels like: Ledger touchscreen signers all come with a private, offline, PIN-protected backup, Ledger Recovery Key, to never lose access to your assets.
- Confirm the network and name. Make sure you are looking at the intended mainnet name or a deliberately disposable Sepolia test name. Never assume a beta page is connected to mainnet.
- Determine the name level. A .eth second-level name has a different route from a 3LD-or-deeper subname. For a subname, identify the exact parent and whether that parent already has a v2 registry.
- Check wrapping and fuses. Record whether the name is unwrapped, unlocked wrapped, locked, emancipated, or detached. For wrapped names, inspect
CANNOT_UNWRAP,CANNOT_TRANSFER,CANNOT_APPROVE, and any other burned fuses that will become role restrictions. - Review approvals. The current v1 token owner or an approved operator must authorize the transfer. For locked names, inspect the existing token approval carefully because a non-null approval can conflict with a burned
CANNOT_APPROVEfuse. - Check expiry and grace status. Determine whether the name is active, in the v1 grace period, or already beyond the documented recovery window. A name in v1 grace must be renewed through ETHRenewerV1 before migration.
- Choose the intended v2 owner. The v2 owner may differ from the v1 owner. Decide whether control should remain with the current wallet or move to another wallet or smart account.
- Plan resolver and subregistry values. The migration data can supply a resolver and subregistry. Have a deliberate destination in mind rather than accepting an unreviewed default.
- Inventory records. Export or otherwise record important records and subname expectations. ENS warns that records may need to be copied separately; do not assume every record and subname behavior transfers unchanged.
- Test first. Follow ENS’s advice to test on Sepolia before considering a valuable name. Use a test name and a wallet you can safely use for experimentation.
Expiry, renewal, and grace-period rules
Expiry is the timing issue most likely to invalidate an otherwise correct migration plan. ENS’s current migration guide documents these protocol constants; the page does not show a publication date.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11| Window | Documented meaning | Owner action |
|---|---|---|
| 90 days | V1 post-expiry grace period | A name in this state must be renewed through ETHRenewerV1 to become active before migration. |
| 28 days | V2 post-expiry grace period | Once a name is migrated, apply the v2 renewal and expiry rules. |
| About 62 days | Bonus added to a v1 expiry when creating a v2 reservation | This aligns reservation availability with the end of v1’s longer grace period; it does not remove the need to monitor expiry. |
Under the documented transition design, migrated names renew through ETHRegistrar. Reserved but still-unmigrated names renew through ETHRenewerV1, which syncs their expiry to v1. If an unmigrated name is not renewed and eventually expires, the guide says it cannot be re-registered through v1. Treat the expiry date and renewal route as separate checks: a reservation does not replace a renewal.
Resolver and record behavior after migration
For most names, migration clears the v1 resolver and sets the v2 resolver supplied in the migration data. The resolver can also be configured afterward. This means a technically successful token transfer does not by itself prove that every expected record is already available.
Locked names have an important exception. If CANNOT_SET_RESOLVER is burned, the existing resolver is carried over and the supplied resolver is ignored. When that carried resolver is a known PublicResolver, ENS replaces it with PublicResolverV2. Because resolver handling depends on lock and fuse state, inspect the resulting resolver rather than assuming the general case applies.
ENS specifically warns that records may need to be copied separately. Plan to verify address, text, content, profile, and other records after migration, and check any subname resolution that matters to your applications. During the reservation period before migration, ENSV1Resolver fallback keeps unmigrated reserved names resolving through v1; that fallback should not be confused with final v2 record placement.
What a safe future production workflow should look like
ENS has not published a production UI path, so the following is a decision sequence rather than a mainnet click-by-click walkthrough. When ENS announces the production tool, its labels and transaction prompts should be treated as authoritative.
- Start from an official ENS entry point. Verify that the page is the production ENS interface announced by ENS, not a similarly named site or an old beta bookmark.
- Confirm reservation. Migration is documented to work only after the name has been reserved. If the interface does not show a reservation, stop rather than signing a transfer.
- Review the detected route. Confirm that the controller matches the name’s state: unlocked controller for eligible second-level names, locked controller for locked second-level names, or parent WrapperRegistry/direct registration for subnames.
- Review every transaction field. Check label, new owner, resolver, subregistry, parent, and any role or fuse interpretation before approving a wallet request.
- Check approvals and expiry again. Wallet state can change between preparation and signing. For a locked name, make sure the approval state does not trigger the documented
CANNOT_APPROVEfailure. - Sign only after confirming irreversibility. The transfer sends the v1 token to the Graveyard and cannot be undone through the documented process.
- Verify the result independently. Confirm the v2 owner, resolver, subregistry, roles, expiry, and important records. Test resolution from more than one resolver-aware application if the name supports a production service.
Testing on Sepolia without risking a valuable name
The official CLI repository calls its tool not production-ready and explicitly recommends testing on Sepolia first. Use that advice as a safety boundary:
Rank #4
- All your digital assets in one place. You can manage thousands of crypto including Bitcoin, Ethereum, Solana, Tether and more.
- Connectivity: USB-C cable connection only. No Bluetooth.Compatible with the Ledger Wallet crypto app, both desktop (Windows, macOS, Linux) and mobile (Android only). Not compatible with iOS.
- Protect your digital assets with the industry's best security: keep your private keys offline in your private signer, battle-tested by the Donjon's white hat hackers, CC EAL 6+ certified Secure Element, constantly updated Ledger OS.
- Effortlessly build your crypto portfolio via the all in one Ledger Wallet app: buy, sell, send, receive, swap, stake and more across popular blockchains. 15,000+ coins & tokens in a single dashboard. Keep a close eye on the market. Compare service providers. Track performance. Get timely alerts. Build your portfolio with confidence.
- Choose the colors that match your style: express your personality and your crypto management mood, color code your signers, one for each use (trading, staking, HOLDing...).
- Use a testnet name and testnet wallet that do not hold valuable mainnet assets.
- Confirm that the wallet is connected to Sepolia before interacting with the beta app or explorer.
- Exercise the route that matches the test name’s wrapping, lock, fuse, and parent state.
- Observe whether reservation precedes migration and whether the resulting owner, resolver, subregistry, and roles match the inputs.
- Try record verification after the transfer, because record copying and resolver setup are distinct from ownership transfer.
- Do not infer that a successful Sepolia transaction proves the mainnet contracts, addresses, UI, or launch process are final.
Common failure modes and how to diagnose them
The name is not reserved
The documented migration controllers require a reservation first. If the interface or transaction reports that no reservation exists, do not repeatedly submit the same transfer. Confirm the name’s eligibility and wait for the official premigration process or instructions.
A locked name cannot transfer
Check whether CANNOT_TRANSFER was burned. That fuse is an intentional restriction and prevents the migration route described for locked names. Also verify that you are using the LockedMigrationController rather than the unlocked path.
The transaction reverts around approval
For a locked name, inspect the combination of CANNOT_APPROVE and the current token approval. ENS documents that a burned CANNOT_APPROVE together with a non-null approval can cause migration to revert. Clear or correct the approval only through the official procedure and only after confirming the wallet is the authorized owner or operator.
A subname has no valid destination
Subnames depend on their parent. Confirm that the parent has migrated and that its v2 registry or WrapperRegistry exists before attempting a child transfer. Unlocked and non-emancipated 3LD-or-deeper names require direct v2 registration rather than a migration-controller transaction.
The resolver or records look different
First check whether the name was locked with CANNOT_SET_RESOLVER, which preserves the existing resolver and can trigger replacement of a known PublicResolver with PublicResolverV2. Then check whether records were copied separately. A successful ownership migration does not guarantee identical record state.
The name is in v1 grace
Renew through ETHRenewerV1 before migration, as required by the guide. Do not assume the approximately 62-day reservation bonus makes a lapsed name active or removes the need for renewal.
Recommended Free Tools
What remains unknown
The public beta announcement does not provide a mainnet date, and current ENS Support still identifies the v2 applications as Sepolia tools. The final production frontend, contract addresses, exact wallet prompts, and any changes made after beta testing are therefore not established here. Use the eventual ENS launch announcement and production documentation for those details rather than copying a testnet procedure.
The practical decision today is straightforward: keep managing a real name through the existing mainnet ENS interface, prepare its state and expiry carefully, and use Sepolia only to learn and test. When ENS announces production availability, recheck the route, resolver, records, approvals, parent status, and irreversible transfer warning before signing.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
