ENS Subname Delegator

WHAT IT DOES

This tool delegates ownership of ENS subnames to another address. It reads and displays the parent ENS name, subname label, subname owner, subname resolver address, subname expiration date, delegation eligibility (whether the caller is the owner), account balance, chain ID, and delegation history. Beyond read-only access, the tool lets you execute the five key actions: delegate subname ownership to a new address, approve a subname delegation (if required), batch delegate multiple subnames in one transaction, claim delegation confirmation, and cancel a pending delegation.

HOW TO USE

Connect your wallet and select the network (ENS is primarily on Ethereum mainnet). Enter the parent ENS name, the subname label (e.g., "sub" for sub.myname.eth), the delegate address, and the ENS registrar contract address. Click "Load State" to fetch the subname owner, resolver, expiration, and delegation history. Review the current owner, subname, delegate address, and eligibility status. If you are the owner and have sufficient balance, click "Delegate" to transfer subname ownership to the delegate address. If the contract requires explicit approval, click "Approve" first. To delegate multiple subnames at once, click "Batch." Click "Claim" to confirm a completed delegation, or "Cancel" to cancel a pending delegation. Each transaction shows confirmation and gas cost reporting.

TECHNICAL MECHANISM

The tool interacts with an ENS registrar contract that supports subname delegation. The delegateSubname() function transfers ownership of a subname (e.g., sub.myname.eth) to another address. The contract validates that the caller is the owner of the parent name or subname. The approveSubnameDelegation() function allows approval of a delegation before execution. The tool fetches subname details via subnameOwner(), subnameResolver(), and subnameExpiration(). Delegation history is tracked via delegationHistory(). Batch delegation uses delegateBatch() with arrays of parent names, labels, and delegates.

WHAT IT CANNOT SEE

Cannot verify that the delegated address is valid or that the subname is appropriate. Relies entirely on the ENS contract's verification and the destination chain's final state. Cannot detect if the delegate address is a contract that may reject ownership, if the subname has expired, or if the parent name is not owned. Does not validate the delegate's ability to manage the subname.

PLEASE NOTE — EVM CHAINS ONLY

Supports Ethereum mainnet primarily (ENS is Ethereum-native) and other EVM chains with ENS support. The registrar contract must implement subnameOwner(), subnameResolver(), subnameExpiration(), delegateSubname(), approveSubnameDelegation(), delegateBatch(), claimDelegation(), cancelDelegation(), and delegationHistory(). The tool is read-write: it signs transactions for delegation, approval, batch delegation, claiming, and cancellation. Always verify the contract address and subname details before submitting.