The Ethereum Name Service (ENS) has established itself as one of the most successful decentralized applications, boasting approximately 800,000 owners across more than 161,000 domains. Its portable, decentralized identity solution has gained significant traction, integrating seamlessly with various applications and platforms. Now, the ENS team is pushing the boundaries further with the development of ENSv2 and Namechain, a dedicated Layer 2 (L2) solution built on Linea's zkEVM technology. This upgrade aims to enhance user experience, reduce costs, and introduce groundbreaking features for onchain identity management.
The Evolution to ENSv2 and Namechain
ENSv2 represents a new protocol architecture designed to address the limitations of the current system. Coupled with Namechain, an L2 rollup, this upgrade focuses on providing cheaper and faster transactions through dedicated blockspace. The initiative is currently in development, with the ENSv2 Hub serving as the central info center for updates and FAQs.
Key Objectives of the Upgrade
- Cost Efficiency: By leveraging Layer 2 technology, ENS aims to significantly reduce transaction fees.
- Speed: Namechain will offer faster processing times for domain registrations and management.
- Flexibility: New features like per-name registries and crosschain resolution will enhance usability.
Based Rollup Architecture
Namechain is being developed as a custom instance of Linea's rollup infrastructure. However, the ENS team is exploring a based rollup model, which utilizes Ethereum for transaction sequencing instead of a dedicated sequencer. This approach offers several advantages:
- Reduced Costs: Eliminating the need for a bespoke sequencer lowers operational expenses.
- Enhanced Security: Leveraging Ethereum's robust security framework provides stronger guarantees.
- Future Potential: The team is considering a transition to a native rollup model, which would integrate tightly with Ethereum's core transaction rules for even greater efficiency.
This architectural choice underscores ENS's commitment to scalability and user-centric design.
Per-Name Registries
One of the most significant changes in ENSv2 is the introduction of standalone registry smart contracts for every .eth name. Unlike the current system, which relies on a single central registry contract on Ethereum, this hierarchical approach offers:
- True Ownership: Users gain contract-level control over their domains.
- Custom Permissions: Easily set permissions, delegate subname issuances, or restrict access as needed.
- Simplified Management: Ideal for communities, DAOs, and users managing multiple names.
This shift empowers users with unparalleled flexibility and control over their digital identities.
Crosschain Resolution
ENSv2 introduces a Universal Resolver mechanism based on CCIP-Read, enabling crosschain resolution of ENS names. This means:
- Interoperability: Resolve .eth names offchain, on Ethereum, Namechain, or other L2s.
- Streamlined Integration: Apps no longer need chain-specific logic to fetch ENS records.
- Portable Identity: Your ENS name becomes universally accessible, enhancing its utility across the ecosystem.
This feature eliminates fragmentation and ensures seamless identity resolution wherever you go.
Stablecoin Payments
To make ENS more accessible, ENSv2 will support USD-denominated stablecoin payments for registrations and renewals. Key benefits include:
- Predictable Pricing: Avoid the volatility associated with ETH payments.
- User-Friendly: Lower barriers for newcomers unfamiliar with crypto volatility.
- Broad Support: USDC is expected from day one, with potential integrations for other stables like USDT or USDe.
This move aligns with ENS's goal of creating a more inclusive and user-friendly experience.
Migration and Next Steps
The ENSv2 roadmap is currently in Phase 2, focusing on finalizing smart contract designs. Future phases include:
- Phase 3: Deployment of Namechain.
- Phase 4: Rollout of ENSv2 contracts on Ethereum and Namechain, along with data migration from legacy contracts.
Migration Options for Users
- Do Nothing: Your names will remain on Ethereum but cannot be renewed after expiration.
- Partial Migration: Migrate to ENSv2 on Ethereum to renew without moving to Namechain.
- Full Migration: Move names to Namechain to access all new features.
Users are encouraged to monitor the ENSv2 Hub for documentation and updates. The transition promises to usher in a new paradigm for onchain identity, offering enhanced flexibility, interoperability, and cost efficiency.
👉 Explore migration strategies and tools
Frequently Asked Questions
What is ENSv2?
ENSv2 is an upgraded protocol architecture for the Ethereum Name Service, designed to improve scalability, reduce costs, and introduce new features like per-name registries and crosschain resolution. It is being developed alongside Namechain, a dedicated Layer 2 solution.
How does Namechain reduce transaction costs?
Namechain leverages Layer 2 technology and a based rollup model, which uses Ethereum for transaction sequencing. This eliminates the need for a dedicated sequencer, reducing operational costs and passing savings to users.
Can I keep my existing .eth name without migrating?
Yes, but you will not be able to renew your name after it expires. To continue using ENS features, consider partial or full migration to ENSv2 or Namechain.
What are the benefits of per-name registries?
Per-name registries provide true domain ownership at the contract level, allowing custom permissions, delegated subname management, and enhanced control. This is particularly useful for users managing multiple names or communities.
Will ENSv2 support stablecoins other than USDC?
While USDC is expected at launch, ENS may integrate additional USD-denominated stablecoins like USDT or USDe in the future, depending on user demand and technical considerations.
How does crosschain resolution work?
Crosschain resolution uses a Universal Resolver and CCIP-Read protocol to fetch ENS record information across different chains, including Ethereum, Namechain, and other L2s, without requiring custom integration code.