ENS and onchain domain names: ownership, resolution, and renewal
Learn how ENS ownership, resolver records, and renewal interact, with practical checks for payments, team handoffs, subnames, and maintaining an onchain identity.
TOPIC GUIDE / ENSv1 name operations
ENSv1 separates a name’s registration, management permissions, and resolver records. Learn which component controls each operation before changing a payment address or handing a name to another person. This guide specifically covers established ENSv1 mechanics; inspect the actual configuration for wrapped names and subnames instead of assuming every registration grants identical permissions.
Read the full Lab guideIn ENSv1, the registrar manages registration while the registry connects names with control information and a resolver. Standard .eth ownership and management are separate roles. The resolver supplies records requested by applications. Identify these components for the specific name so a role transfer does not become confused with a record update.
Make a responsibility table listing the registration holder, everyday manager, and intended receiving addresses. If the name uses the Name Wrapper or delegated restrictions, inspect the applicable permissions. Describe the action each account can authorize. A role label becomes useful when you can explain its practical effect.
Before editing, capture the existing record and write the intended value with its network and purpose. Review the wallet request against that plan. After the change is confirmed, look up the name through the application intended to use it and inspect the destination it actually displays.
For a hypothetical treasury handoff, transferring the registration and changing a payment record are separate tasks. Verify both, then inspect inherited profile information and manager permissions. Keep the transaction references with the intended configuration so a later maintainer can distinguish an authorized change from an unexplained difference.
Check the .eth expiry date and assign responsibility for renewal before it becomes urgent. ENSv1 renewal adds time to the existing expiry; paying for the extension does not transfer ownership. Verify the resulting date after confirmation, particularly when extending a registration that has already expired.
Track how loss of access to the everyday manager would be handled and which account can restore control. Maintain this operational record securely. The objective is dependable name administration: a known controller, reviewed records, and an active registration. Treat wrapped names and project subnames according to their own documented restrictions.
Primary reference: ENS: How do ENSv1 names work?. Read the current documentation for the exact network, asset, or product you are researching.
Keep exploring
For ENSv1 .eth registrations, renewal extends the existing registration without transferring ownership. Confirm the resulting expiry date, and do not confuse paying a fee with acquiring the name.
No. The manager controls configuration, while payment records specify destinations. Review the actual role and record values separately before assuming a management change also redirects incoming payments.
This page covers ENSv1 mechanics. Wrapped registrations, subnames, imported DNS names, and other naming systems can involve additional permissions or dependencies that require their own configuration review.
From the DeFi Altcoin Lab
Put the concepts to work with a detailed guide, concrete research steps, and the questions to ask before acting.
Learn how ENS ownership, resolver records, and renewal interact, with practical checks for payments, team handoffs, subnames, and maintaining an onchain identity.
Build an evidence-first DeFi research workflow: bound the question, verify sources and contract identities, check calculations, and preserve unresolved claims.
Design a bounded DeFi agent workflow with explicit spending permissions, transaction review, session limits, revocation, and practical tests before automation.