Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →You cannot migrate a real Ethereum Mainnet ENS name to ENSv2 yet. As of October 2026, ENS identifies the v2 app and explorer as a Sepolia testnet beta. Real names remain managed through the ENS App on Ethereum Mainnet. ENS announced the beta on August 12, 2026, and says mainnet timing will depend on public-test results, so there is no confirmed production migration date or official Mainnet transaction walkthrough to follow.
The useful work today is preparation: identify your name’s type, wrapper and fuse state; check its parent and expiry; understand which v2 route it will use; and test only with Sepolia accounts or names. ENS’s own guide says, “Migration is not required immediately.”
As an Amazon Associate I earn from qualifying purchases.
What ENSv2 migration is supposed to do
ENS describes migration as a two-phase process rather than a simple contract upgrade. First, the protocol automatically reserves eligible existing names in the v2 ETH Registry. A reservation creates a slot without assigning a v2 owner. While that slot is reserved, an ENSV1Resolver fallback keeps the name resolving through v1.
Second, the current v1 token owner, or an approved operator, authorizes a transfer to the controller or registry appropriate to the name. That transfer promotes the reservation to a registered v2 name. The v1 token is then sent to the Graveyard. The v2 owner does not have to be the same address as the v1 owner, so migration can move control to a new wallet or a smart account.
#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.
Migration is one-way. ENS’s command-line documentation calls the tool not production-ready and specifically advises testing on Sepolia before migrating valuable names. A Sepolia test is a rehearsal; it is not evidence that the same operation is available for a Mainnet name.
Current status: Sepolia beta, not a Mainnet procedure
ENS Support currently describes the v2 app and explorer as Sepolia testnet tools. They are intended for testing and do not manage real Mainnet names. The ENS App on Ethereum Mainnet remains the place to manage existing production names until ENS announces a live v2 deployment and migration interface.
ENS announced in February 2026 that ENSv2 would deploy exclusively on Ethereum Layer 1 and that development of Namechain had ceased. Older material that presents Namechain as the migration destination is therefore obsolete. The August 12, 2026 public-beta announcement describes beta as the final major public testing phase before Mainnet, but gives no launch date; timing will follow the test results.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Do not sign a purported Mainnet “ENSv2 migration” transaction unless ENS has announced production availability and the link comes from its current official documentation or support pages. A third-party page can imitate the beta interface while directing an approval or token transfer to an unrelated contract.
Identify your name before choosing a migration route
The correct controller depends on whether the name is a second-level .eth name or a subname, and on whether wrapping, locks or fuses are present. The following routes come from ENS’s documented migration design.
| 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 set. The name is unwrapped to the Graveyard during migration. |
| Locked .eth second-level name | LockedMigrationController | v1 fuses are converted to v2 roles and a WrapperRegistry is deployed as the subregistry. |
| Locked emancipated subname (3LD or deeper) | Transfer to the parent’s WrapperRegistry after the parent migrates | Fuses become 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 likewise cannot migrate through the migration controllers. |
Why locked names need extra checking
For a locked name, a burned v1 fuse that blocks an action becomes the corresponding restriction in v2: the related role is not granted. That conversion makes the exact fuse set decisive. Before signing any future transaction, confirm whether the name is locked, which fuses are burned, whether it is emancipated or detached, and which roles the destination registry will grant.
Two documented conditions can make a locked migration fail. A burned CANNOT_TRANSFER prevents migration. A burned CANNOT_APPROVE combined with a non-null token approval can also cause a revert. Clear an incompatible approval only through an official, verified interface and only after checking the final ENS instructions.
Compare the routes by the questions that affect ownership
There are not competing ENSv2 products to choose between. The practical comparison is between migration paths. Start with the token state, then check the name level, fuse restrictions, parent dependency, resolver behavior and expiry status.
| Question | Why it matters |
|---|---|
| Is the name a 2LD or a 3LD-plus name? | Second-level names can use a migration controller; many subnames instead require direct v2 registration or a parent WrapperRegistry. |
| Is it wrapped, locked, emancipated or detached? | Those states determine whether unwrapping is required, which controller applies and which v2 roles are created. |
| Has the parent migrated? | Emancipated and detached children cannot complete their documented route until the parent has a v2 registry. |
| Can the token be transferred and approved? | CANNOT_TRANSFER blocks a locked migration, while an incompatible approval can trigger a revert when CANNOT_APPROVE is burned. |
| What happens to the resolver? | Most names receive the resolver supplied in migration data; locked names with CANNOT_SET_RESOLVER preserve the existing resolver instead. |
| Is the name active or in grace? | A name in v1 grace must be renewed through ETHRenewerV1 before it can migrate. |
What happens to ownership, subnames and registries
Premigration reserves registered or in-grace v1 names in batches. Reservation alone does not assign a v2 owner. The reservation remains linked to the v1 name through the ENSV1Resolver fallback until the owner completes the transfer.
For a second-level locked name, ENS converts the v1 fuse state into v2 roles and uses a WrapperRegistry as the subregistry. For an emancipated subname, the parent must migrate first because the child’s destination is the parent’s WrapperRegistry. An unlocked or non-emancipated 3LD-plus name is not moved by the migration controllers; it must be registered directly in v2 after a v2 registry exists for its parent.
The v2 owner may be a different address from the v1 owner. Decide that destination deliberately: it can be a replacement wallet, a multisignature account or another smart account, provided the eventual production interface supports it.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsRank #2
- Seedless by design, nothing to steal: Your private key is generated inside the EAL6+ chip and never leaves it. No seed phrase is shown or typed at setup, so a tampered device, keylogger, or phishing site has nothing to capture. 9+ years, millions of card.
- Tap once to manage your entire crypto wallet across 90 blockchains - no USB cables or Bluetooth, no batteries, no setup. Access 16,100+ coins & tokens, DeFi, NFTs, and staking instantly from your phone
- Backup without a seed phrase: Your wallet is copied to 2 backup cards with end-to-end encryption, so there are no words on paper to lose or leak. Keep them in separate places; if one card is lost, the others restore full access. Optional seed phrase for advanced users.
- Engineered to last up to 25 years: Waterproof (IP69K), shockproof and tested for extreme temperatures from −25°C to 50°C. A durable cold wallet with long‑term protection and independently audited security.
- Trusted by 6 million users worldwide - buy, sell, swap, stake, and spend cryptocurrency directly. The secure offline storage wallet designed for how people actually use crypto wallets
Names that cannot yet migrate do not simply disappear. Under the documented transition design, unmigratable names remain functional on v1, with v1 ownership, resolver and fuse behavior unchanged. Their renewals continue through ETHRenewerV1 while the reservation is active. That continuity is useful, but it is not a promise that the name can be renewed forever without action; an unmigrated name that is not renewed eventually expires.
Resolver and record continuity is not automatic
For most names, the migration data clears the v1 resolver and sets the v2 resolver. The resolver can also be configured after migration. You should therefore record the current resolver address and important records before any future Mainnet operation.
Locked names with CANNOT_SET_RESOLVER burned are an exception. Their existing resolver is carried over and the resolver supplied in migration data is ignored. If that carried resolver is a known PublicResolver, ENS replaces it with PublicResolverV2.
ENS warns that records may need to be copied separately. Do not assume that address records, text records, content hashes, reverse resolution, wildcard behavior or subname resolution will all appear unchanged immediately after a migration. Plan a post-migration verification pass rather than treating a successful token transfer as proof that every application-facing record survived.
Record continuity has two separate questions: whether a name still resolves, and whether each record is present in the v2 resolver. The ENSV1Resolver fallback can preserve resolution during reservation, but applications may read individual records from a different resolver after migration. Save the records you actually use, including chain-specific addresses and text metadata, instead of checking only the primary Ethereum address.
Expiry, grace periods and renewal timing
Expiry status determines whether a name is active, in v1 grace, reserved or at risk of expiring. ENS’s current migration guide documents these protocol time constants:
| Window | Documented value | How it affects an owner |
|---|---|---|
| v1 post-expiry grace period | 90 days | A v1 name can remain in the documented grace state during this period. |
| v2 post-expiry grace period | 28 days | This is the corresponding post-expiry window in the v2 design. |
| Premigration bonus | Approximately 62 days | Added to a v1 expiry when creating a v2 reservation so reservation availability aligns with the end of v1’s longer grace period. |
These are ENS-documented protocol constants; the guide does not show a publication date, so they should not be read as rules introduced specifically in 2026.
If the name is already in v1 grace
The migration guide says a name in the v1 grace period must first be renewed through ETHRenewerV1 to become active before migration. Check the exact expiry and grace status in the official interface when a production migration is announced; do not infer eligibility from the name resolving in a wallet or browser.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Renewal after reservation or migration
Under the documented transition design, a migrated name renews through ETHRegistrar. A reserved but not-yet-migrated name renews through ETHRenewerV1, which synchronizes its expiry to v1. An unmigrated name that is not renewed eventually expires, and the guide says it cannot be re-registered through v1.
The approximately 62-day bonus is not extra ownership time that an owner can freely spend today. It is a protocol adjustment made when a v2 reservation is created, intended to align reservation availability with the end of v1’s longer grace period. Treat the 90-day and 28-day windows as separate rules rather than adding them together.
Preparation checklist for owners
Use this checklist while ENSv2 remains in beta. It prepares you for the eventual production interface without treating testnet actions as Mainnet migration.
Rank #3
- Unparalleled Security: Protect your assets with EAL 6+ Secure Element, offering robust defense and complete transparency
- Simple & Secure Interface: Manage your digital assets easily with a clear OLED screen for secure on-device confirmations
- Supports 1000s of Coins & Tokens: Securely handle thousands of assets, including Bitcoin, Ethereum, and more, all in one wallet
- Effortless Asset Management: Monitor and transact seamlessly with Trezor Suite, our intuitive desktop and mobile app
- Enhanced Backup Solution: Multi-share Backup eliminates single points of failure for secure cold wallet recovery
- Classify the name. Record whether it is an unwrapped second-level .eth name, an unlocked wrapped name, a locked name, or a 3LD-plus subname.
- Inspect wrapper and fuse state. For wrapped names, determine whether
CANNOT_UNWRAP,CANNOT_TRANSFER,CANNOT_APPROVE,CANNOT_SET_RESOLVERor other fuses are burned. Note whether a subname is emancipated or detached. - Check the parent. A 3LD-plus name that depends on a parent’s WrapperRegistry cannot follow its child route until the parent has a v2 registry.
- Check token control. The v1 token owner or an approved operator must be able to authorize the eventual migration transaction. Review existing approvals, especially where
CANNOT_APPROVEis burned. - Check expiry and grace. If the name is in v1 grace, plan the ETHRenewerV1 renewal required by the guide before migration.
- Choose the intended v2 owner. Confirm the address that should receive v2 ownership; it may differ from the current v1 owner.
- Plan resolver and records. Save the current resolver and export or otherwise document important records. Decide which v2 resolver and subregistry the future transaction should specify.
- Test on Sepolia only. Use test accounts and test names with the official beta tools. Never use a valuable Mainnet name as a first attempt.
- Verify after any eventual Mainnet migration. Check owner, resolver, ETH and non-ETH records, reverse resolution, content hash and relevant subname behavior separately.
What a future owner-authorized migration will contain
ENS’s owner-facing guide says a frontend migration tool will be available when the time comes. Until that tool is released for Mainnet, the safest description is conceptual rather than a click-by-click procedure.
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 & 11For an unwrapped or eligible unlocked second-level name, the transfer data includes the label, the new owner, the resolver and the subregistry. For a locked second-level name, the LockedMigrationController interprets the fuse state, converts applicable restrictions to roles and establishes the WrapperRegistry. For a child name, the destination is the parent’s WrapperRegistry and the parent migration must already be complete.
The transaction can be sent only after the name has been reserved. The signer must be the v1 token owner or an approved operator. A wallet prompt that asks for an unrelated unlimited approval, sends the token to an address other than the documented controller, or runs on an unsupported network is a reason to stop.
There is no confirmed production fee schedule in the current ENS material. Owners should expect the eventual interface to display network and contract costs, but should not rely on a Sepolia gas estimate as a Mainnet price. Mainnet contract addresses, final transaction batching and any fee changes remain pending until launch documentation is published.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Common failure modes and how to diagnose them
“The v2 app shows my name, but I cannot manage it.”
You are probably viewing the Sepolia beta or a reservation without a v2 owner. Confirm the wallet network and remember that a reservation is not completed migration.
“The transaction reverts for a wrapped name.”
Check whether CANNOT_UNWRAP is set. An unlocked wrapped name must be unwrap-able for the documented unlocked route. For a locked name, inspect CANNOT_TRANSFER, CANNOT_APPROVE and the current token approval.
“My subname has no migration button.”
Determine whether it is an unlocked or non-emancipated 3LD-plus name. Those names are registered directly in v2 after the parent has a v2 registry rather than migrated through the controllers. If it is emancipated or detached, verify that the parent migrated first.
“The name resolves, but records are missing.”
Resolution through the ENSV1Resolver fallback or a carried resolver does not prove that every record was copied. Compare the old record set with the v2 resolver and complete any required record-copy operation through the official interface.
“The name is expired.”
Identify whether it is within the documented 90-day v1 grace period. If so, the guide requires renewal through ETHRenewerV1 before migration. If the name has passed the applicable recovery window, wait for ENS’s production rules rather than assuming v1 re-registration remains possible.
“The parent migrated, but the child still cannot move.”
Confirm that the parent has a v2 registry of the type required by the child route, not merely a reservation. Then verify whether the child is emancipated or detached and whether its token is being transferred to the parent’s WrapperRegistry.
How to treat Sepolia testing safely
The CLI repository labels its migration tool “Not production-ready.” A responsible test uses a separate wallet, testnet funds, nonvaluable names and a written record of the expected owner, resolver and subregistry. Test the route that matches the name state instead of assuming an unlocked example represents a locked or child name.
Rank #4
- UNPARALLELED SECURITY: Protect your assets with Trezor Safe 5's NDA-free EAL 6+ Secure Element, offering robust defense and complete transparency.
- EFFORTLESS NAVIGATION: Experience seamless crypto management with the vibrant color touchscreen, designed for intuitive and user-friendly interactions.
- ENHANCED USER EXPERIENCE: Enjoy tactile confirmation with Trezor Touch Haptic Engine, making each interaction precise and engaging.
- SUPPORTS 1000s OF COINS & TOKENS: Securely handle thousands of assets, including Bitcoin, Ethereum, and more, all in one wallet.
- EASY ASSET MANAGEMENT: Monitor and transact seamlessly with Trezor Suite, our user-friendly desktop and mobile app
After a Sepolia transaction, inspect the resulting owner, resolver, roles, registry and records. A successful test demonstrates that the beta contracts accepted that test case; it does not establish Mainnet contract addresses, gas costs, launch timing or final user-interface labels.
Keep a transaction log for each test: network, contract address, name state, signer, destination owner, resolver and observed records. That makes it easier to distinguish a route-specific failure from a beta-interface change and prevents accidentally repeating a test with a valuable wallet or name.
Recommended Free Tools
What remains unknown
ENS has not published a confirmed Mainnet launch date in the material currently available, and current support still identifies the v2 tools as Sepolia beta. The final production migration frontend, Mainnet contract addresses, transaction fees and any changes made after public testing should therefore be treated as pending. Recheck ENS’s launch announcement, support page and production app immediately before taking action.
Until that announcement, keep the name in its existing v1 management flow, renew it on time and do not migrate a valuable Mainnet name through an unverified interface. The documented design provides a clear preparation model, but it is not yet an open production procedure.
Frequently Asked Questions
Can I migrate my real ENS name on Ethereum Mainnet now?
No. ENS currently identifies ENSv2 apps as Sepolia beta tools. Wait for an official Mainnet launch announcement and production interface.
Does migration happen automatically after a name is reserved?
No. Reservation creates a v2 slot without an owner. The v1 owner or approved operator must authorize the one-way transfer that completes migration.
Free tools Windows power users keep installed
One-click scans. No signup required.
Can the new v2 owner be a different wallet?
Yes. The documented migration data can specify a new owner, so migration can move control to another wallet, multisignature account or supported smart account.
What if my name is in the v1 grace period?
Renew it through ETHRenewerV1 first. The guide says a name must be active before it can migrate.
Will all my records copy automatically?
Do not assume so. Resolver behavior depends on lock and fuse state, and ENS warns that records may need to be copied separately. Verify each important record after migration.
Can an unlocked subname use the unlocked migration controller?
No. Unlocked and non-emancipated 3LD-plus names must be registered directly in v2 after their parent has a v2 registry.
Free tools Windows power users keep installed
One-click scans. No signup required.
What blocks a locked-name migration?
A burned CANNOT_TRANSFER fuse prevents migration. A burned CANNOT_APPROVE fuse combined with a non-null token approval can also cause a revert.
Is a hardware wallet required?
No documented migration requirement calls for one. Hardware-wallet use is an optional personal key-management choice, not a condition of ENSv2 migration.
The Bottom Line
Bottom line: ENSv2 migration is still a Sepolia beta exercise, not an open Mainnet operation. Classify the name, inspect fuses and approvals, confirm parent and expiry status, preserve resolver records, and test only with nonvaluable Sepolia accounts. When ENS publishes the production launch and interface, follow that documentation rather than an old Namechain guide or an unverified transaction link.
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.
