ENSv2 migration does not produce one universal result for every subname. The outcome depends on whether the name is locked, detached, emancipated, or still non-emancipated, and on whether its parent has migrated. Migration can change the registry owner, wrapped-name status, resolver, renewal contract, and expiry behavior.
The safest approach is to identify the name state first, record the intended v2 owner and resolver, check the parent and child expiries, and then verify the v2 registry entry after the transaction. A v2 owner may be a different address from the v1 owner, and renewing a parent .eth name does not automatically renew its existing subnames.
As an Amazon Associate I earn from qualifying purchases.
What changes when an ENS name migrates to v2?
ENSv2 moves name control from the v1 system into v2 contracts. The migration data specifies the v2 owner and, where applicable, resolver information. The v1 token is routed through a migration controller and cleanup path, while the corresponding v2 registry slot is registered to the supplied v2 owner.
That means the address that owned a name in v1 is not necessarily the address that controls it in v2. The ENS Documentation states that “the v2 owner can be a different address than the v1 owner.” Treat the migration payload as the authoritative source for the post-migration owner rather than assuming the address will be copied automatically.
#1 Best Overall
- Read Before You Buy — No Video Output: These adapters support charging and USB 2.0 data transfer, but cannot transmit video signals. Except for standard USB webcams (which use USB data only), they are not compatible with HDMI/DisplayPort cables, video-capable USB-C hubs, or docking stations with video output.
- Convert USB-A Ports to USB-C: Designed to connect USB-C earphones, cables, flash drives, card readers, and other USB-C accessories to standard USB-A ports. Plug-and-play with no drivers or software required.
- Aluminum Alloy Housing: Built with a sturdy aluminum alloy shell that aids in heat dissipation and protects against daily wear and scratches. Designed to maintain a stable and secure connection.
- Compact & Travel-Friendly: The ultra-compact design allows the adapter to stay plugged into your device without blocking adjacent ports or adding bulk, reducing wear and tear on your original USB ports.
- 12-Month Warranty: Backed by a 12-month manufacturer warranty for peace of mind. Designed to meet strict quality control standards for reliable everyday performance.
Migration is state-dependent. Before submitting a transaction, determine whether the name is an unwrapped .eth second-level domain, an unlocked name, a locked name, a detached subname, an emancipated subname, or a non-emancipated three-level-or-deeper name. Each state has a different route and set of surviving controls.
Identify the subname state before you migrate
| Name state | Must the parent migrate first? | v2 destination or route | Important control result |
|---|---|---|---|
| Emancipated subname | Yes. Its parent must already be in v2. | Migration path that preserves the emancipated relationship. | The parent cannot replace the name or burn additional fuses on it. |
| Locked subname | Follow the locked-name migration requirements; parent state matters for subnames. | v2 WrapperRegistry entry. | v1 fuse restrictions are converted into v2 roles; the name cannot be unwrapped. |
| Detached subname | Use the detached migration route. | Unwrapped to the Graveyard and registered with the standard role set. | It does not retain the locked WrapperRegistry treatment. |
| Non-emancipated 3LD+ subname | Migration controllers cannot be used for this state. | Direct registration in v2. | Plan a new v2 registration rather than a controller-based migration. |
| Unwrapped or unlocked .eth 2LD | Use the applicable .eth migration and registrar flow. | v2 registry and ETH Registrar contracts. | Renewal and grace-period rules differ from those of subnames. |
The ENS Documentation specifically says that non-emancipated 3LD+ subnames cannot be migrated through the migration controllers. Trying to force that route can leave the transaction inapplicable to the name state; direct v2 registration is the supported alternative.
Why the parent requirement matters
An emancipated subname is no longer freely replaceable by its parent, but its migration still depends on the parent being migrated first. Confirm the parent’s v2 registry entry before preparing the child transaction. If the parent is still in v1, stop and migrate or register the parent through the appropriate path first.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
What happens to the old v1 token
The old v1 token is sent through the migration controller and cleanup process. The practical result is that the v2 registry slot, not the retired v1 token, becomes the record that determines the supplied v2 owner and current v2 controls.
Rank #2
- 5-in-1 USB-C Hub: Experience comprehensive connectivity featuring a Power Delivery input, two USB-A 2.0 ports, a USB-A 3.0 port, and an HDMI port. (Note: The USB-C power delivery input port is only for connecting an external wall charger to power your laptop and cannot power peripheral devices.)
- 90W Pass-Through Charging: Achieve optimal charging with 90W pass-through power to your laptop, supported by a total input of 100W, with the hub reserving 10W for operational efficiency. (Note: Wall charger not included.)
- Quick Data Transfers: Accelerate your productivity with rapid data transfers using a high-speed 5Gbps USB 3.0 port and two 480Mbps USB 2.0 ports.
- 4K HDMI Display: Enhance your visual experience with a hub capable of delivering 4K resolution at 30Hz in both mirror and extend modes. Please note that this hub is compatible with MacBook (macOS 12 and newer), Windows 10 and 11, ChromeOS, and laptops equipped with DP Alt Mode and Power Delivery. Note: This device is not compatible with Linux.
- What You Get: Anker USB-C Hub (5-in-1, 4K HDMI), welcome guide, 18-month warranty, and our friendly customer service.
Who owns an ENS subname after migration?
There are three separate concepts to check after migration:
- v2 registry owner: the address recorded in the v2 registry slot;
- wrapped-name NFT holder: the account holding any NFT representation of the wrapped name; and
- parent and fuse powers: permissions that remain available or have been permanently burned through fuse restrictions.
These can point to different practical outcomes. The registry owner may be changed in migration data, the NFT holder may reflect wrapped-name custody, and a parent may lose management abilities even though the parent-child relationship remains visible.
Parent transfers and ordinary management
Transferring a parent normally leaves its subnames linked to that parent. The new parent owner receives the parent’s ordinary management powers, subject to the fuses already burned on each child. A parent transfer therefore does not automatically transfer every child to a new independent owner or erase child-level restrictions.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsEmancipation limits the parent
An emancipated subname prevents its parent from replacing it or burning additional fuses. The child can remain attached to the parent while the parent’s ability to alter that child is restricted. Check the child’s fuse state before assuming that a new parent owner can recreate, overwrite, or further restrict it.
Rank #3
- Sleek 7-in-1 USB-C Hub: Features an HDMI port, two USB-A 3.0 ports, and a USB-C data port, each providing 5Gbps transfer speeds. It also includes a USB-C PD input port for charging up to 100W and dual SD and TF card slots, all in a compact design.
- Flawless 4K@60Hz Video with HDMI: Delivers exceptional clarity and smoothness with its 4K@60Hz HDMI port, making it ideal for high-definition presentations and entertainment. (Note: Only the HDMI port supports video projection; the USB-C port is for data transfer only.)
- Double Up on Efficiency: The two USB-A 3.0 ports and a USB-C port support a fast 5Gbps data rate, significantly boosting your transfer speeds and improving productivity.
- Fast and Reliable 85W Charging: Offers high-capacity, speedy charging for laptops up to 85W, so you spend less time tethered to an outlet and more time being productive.
- What You Get: Anker USB-C Hub (7-in-1), welcome guide, 18-month warranty, and our friendly customer service.
Locked names cannot be unwrapped
A locked name cannot be unwrapped. Its v1 fuse restrictions are translated into v2 roles on the WrapperRegistry entry. Ownership of the wrapped representation and the permissions represented by those roles must therefore be evaluated separately.
How each subname migration path works
Locked subnames: WrapperRegistry and role conversion
A locked subname moves into the v2 WrapperRegistry. Its existing fuse restrictions are converted into v2 roles, so the post-migration behavior is expressed through role permissions rather than a simple copy of the v1 fuse bits. Because the name remains locked, unwrapping is not available.
Before migration, record the intended v2 owner, the parent address, every relevant fuse, the current resolver, and both parent and child expiries. After migration, inspect the WrapperRegistry entry and confirm that the expected roles are present. A successful transaction alone does not prove that the resulting owner or resolver matches your plan.
Free tools Windows power users keep installed
One-click scans. No signup required.
Detached subnames: Graveyard route
A detached subname follows a different path. It is unwrapped to the Graveyard and then registered with the standard role set. Detached status therefore matters: do not expect the locked-name WrapperRegistry treatment or the same parent-control behavior.
Rank #4
- Dual Converters, Infinite Potential：Includes 2× USB C male to USB A female adapters and 2× USB A male to USB C female adapters. Perfect for a wide range of uses—tablets with Bluetooth keyboards, expand USB ports on macbook, and more. Two different converters for all your daily needs
- Next-Level 10Gbps & 3A Charging: No more slow 480Mbps, this usb to usb c adapter has a transfer speed of up to 10Gbps, allowing you to do more transferring in less time. This usb adapter fits both USB A and USB C charger, supporting up to 3A fast charging
- Upgraded Exquisite Craftsmanship: With an aluminum alloy housing and metal connector, the usbc to usb adapter is extremely durable and sturdy. Rigorously tested to withstand more than 10,000 times of plugging and unplugging, ensuring long-lasting performance
- Broad Compatible: The usb c to usb adapter widely supports all USB C/ USB A devices like laptops, tablets, cellphones, car chargers, and phone chargers. Such as compatible with MacBook Pro/Air 2023/2022, Thunderbolt 4/3 Devices,Apple MagSafe Watch 9/8/7/SE/Ultra, iPad Pro 2022/2021, Samsung Galaxy S23/S20/S10, and iPhone 17/16/15 Pro. Plug and play
- Please Note: To reach 10Gbps speed, keep the cable under 3.3 ft. For USB A Male to USB C adapters, try flipping the USB C connector. USB C Male to USB A adapters support bidirectional 10Gbps transfer within 3.3 ft
Verify the v2 registry owner and role set after the transaction. If the name is intended to be managed independently, the detached route should be assessed as a new v2 registration state rather than as a continuing locked wrapper.
Non-emancipated 3LD+ names: direct v2 registration
Non-emancipated subnames at three labels or deeper cannot use the migration controllers. They must be registered directly in v2. Gather the desired owner, resolver, parent relationship, expiry, and any intended permissions before registration, because this is not a controller migration that simply carries the old record forward.
Emancipated names: parent-first sequencing
For an emancipated child, migrate the parent first. Once the parent is represented in v2, process the child using the applicable migration path and verify that the parent’s remaining powers match the child’s emancipation state.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →What happens to the resolver?
Resolver treatment is conditional rather than automatic. The migration outcome depends on the name’s locked state, the CANNOT_SET_RESOLVER fuse, and whether the existing resolver is the known PublicResolver.
Best Value
- 5-in-1 Connectivity: Equipped with a 4K HDMI port, a 5 Gbps USB-C data port, two 5 Gbps USB-A ports, and a USB C 100W PD-IN port. Note: The USB C 100W PD-IN port supports only charging and does not support data transfer devices such as headphones or speakers.
- Powerful Pass-Through Charging: Supports up to 85W pass-through charging so you can power up your laptop while you use the hub. Note: Pass-through charging requires a charger (not included). Note: To achieve full power for iPad, we recommend using a 45W wall charger.
- Transfer Files in Seconds: Move files to and from your laptop at speeds of up to 5 Gbps via the USB-C and USB-A data ports. Note: The USB C 5Gbps Data port does not support video output.
- HD Display: Connect to the HDMI port to stream or mirror content to an external monitor in resolutions of up to 4K@30Hz. Note: The USB-C ports do not support video output.
- What You Get: Anker 332 USB-C Hub (5-in-1), welcome guide, our worry-free 18-month warranty, and friendly customer service.
| Condition at migration | Resolver result | What to verify |
|---|---|---|
| Locked name with CANNOT_SET_RESOLVER | The v1 resolver is preserved. | Confirm that the preserved address is the resolver you intend to keep. |
| Known PublicResolver | Replaced with PublicResolverV2. | Check that records resolve through the v2 resolver after migration. |
| Other migrated names | The v1 resolver is cleared. | Use the resolver supplied in migration data or configure a v2 resolver afterward. |
Do not infer resolver continuity from ownership continuity. A name can arrive at its intended v2 owner while its old resolver has been cleared, so inspect the resolver field and test the records that matter to you, such as address, content, and text records.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.How renewal and expiration work after migration
Migrated names renew through the v2 ETH Registrar. Unmigrated RESERVED names renew through ETHRenewerV1, which synchronizes their expiry to v1. ENS Documentation says that once ENSv2 is live, v1 .eth registrations and renewals are disabled, so the correct contract and name state must be checked immediately before any renewal transaction.
| Situation | Renewal or expiry rule | Published timing |
|---|---|---|
| Migration reservation examples | The migration examples include a temporary v2 reservation bonus. | 62 days in the documented examples; this is not a universal child-expiry guarantee. |
| v2 registration grace period | A v2 registration receives the documented v2 grace period after expiry. | 28 days in the current migration examples. |
| Legacy .eth 2LD | The .eth Registrar applies its legacy grace period. | 90 days. |
| Wrapped .eth 2LD | Name Wrapper expiry follows the .eth Registrar expiry plus the 90-day grace period. | Registrar expiry plus 90 days. |
| Other subnames | The parent chooses the child expiry; the default maximum is the parent’s expiry. | Bounded by the parent unless the relevant permissions allow an extension. |
The 62-day reservation bonus and 28-day v2 grace period are figures in the migration examples documented by ENS, accessed October 19, 2026. Treat live deployment status, registrar behavior, and the expiry displayed for a particular name as volatile and verify them before signing.
Does renewing the parent renew its subnames?
No. Renewing a parent .eth name does not automatically extend existing subnames. The parent can extend a child’s expiry separately. ENS Support states that the parent can extend an existing subname at any time, including after the subname has been emancipated.
If CAN_EXTEND_EXPIRY has been burned, the subname owner or an approved controller can extend the child. Even then, the extension cannot move the child beyond the parent’s expiry. The parent’s renewed date therefore sets the outer boundary, but a separate child-extension action is still required.
Do ENS subnames receive a grace period?
Subnames generally do not have a grace period comparable to the 90-day .eth 2LD grace period. When a wrapped subname expires, whether the holder loses ownership depends on whether the name is emancipated and on the fuses burned on that name. Review those controls before relying on a post-expiry recovery assumption.
Pre-migration checklist
- Classify the name as an unwrapped 2LD, unlocked 2LD, locked name, detached subname, emancipated subname, or non-emancipated 3LD+ name.
- Check whether an emancipated child’s parent has already migrated.
- Record the v1 owner and the intended v2 owner; do not assume they are identical.
- Record the current resolver and determine whether CANNOT_SET_RESOLVER or a known PublicResolver changes the outcome.
- Write down the parent expiry, child expiry, registrar state, and any 62-day reservation bonus shown by the migration flow.
- List the fuses and identify whether CAN_EXTEND_EXPIRY or another controller can extend the child.
- Choose the correct route: WrapperRegistry migration for locked names, Graveyard handling for detached names, or direct v2 registration for non-emancipated 3LD+ names.
Post-migration verification
- Open the v2 registry record and confirm the owner address supplied in the migration data.
- For wrapped names, check the WrapperRegistry entry, NFT custody, and converted roles.
- Read the resolver field and verify whether it was preserved, replaced by PublicResolverV2, or cleared.
- Check the parent-child relationship and compare the child expiry with the parent expiry.
- Confirm which contract handles the next renewal: v2 ETH Registrar, ETHRenewerV1 for an unmigrated RESERVED name, or a child-extension controller.
- Test the records that users depend on and keep the transaction receipt and resulting registry data for your own records.
Common mistakes and how to avoid them
- Assuming the old owner is retained: read the v2 owner from the migration result.
- Using a migration controller for a non-emancipated 3LD+ name: register that name directly in v2.
- Expecting parent renewal to cascade: schedule a separate child-extension action.
- Assuming every child has a grace period: distinguish subname expiry from the .eth 2LD’s 90-day grace period.
- Assuming resolver continuity: inspect the resolver condition, especially CANNOT_SET_RESOLVER and PublicResolver replacement.
- Ignoring fuse state: emancipation and locking can remove parent powers or prevent unwrapping even when ownership appears straightforward.
What to check immediately before signing
ENS deployments, registrar availability, and per-name expiry are operational details that can change. Confirm the live contract addresses and interface shown by the ENS application, then compare the transaction’s migration data with your recorded owner, resolver, parent, child expiry, and fuse state. If any field differs, cancel and resolve the discrepancy before submitting.
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.
