Transfers and subnames
Move registration authority or create child identities safely.
A transfer changes control of a name asset; a subname creates a new label beneath a parent. Wrapped and unwrapped names use different contracts and authority paths, so the UI resolves the current state before preparing actions.
Before you run this workflow
Networks
- Ethereum mainnet
Prerequisites
- Connected controlling wallet
- Correct owner, manager, registrant, or resolver authority
Wallet permissions
- Only the transaction or typed-data signature shown for the selected operation
Expected result
- A confirmed onchain update with per-name status for bulk operations
Errors and recovery
- Inspect authority and wrapped-name state
- Retry only failed items after refreshing chain state
How to use it
- 1
Verify the recipient
Resolve ENS recipients carefully, compare the final address, and consider sending a small unrelated test transaction when appropriate.
- 2
Check the asset path
Wrapped names transfer the wrapper token; unwrapped .eth registrations use the Base Registrar NFT while registry manager state may differ.
- 3
Review fuses and permissions
Subname fuses and emancipation can permanently restrict the parent. ENS.Tools does not burn fuses by default in fleet preparation.
- 4
Confirm the final authority
After confirmation, refresh owner, manager, resolver, and wrapped state rather than relying only on a transaction success status.