Deep Dive
1. L2 Network Selection & Core Upgrades (Q3 2026)
Overview: The immediate focus is completing Phase 1 (L2 Selection) and advancing to Phase 2 (Write New Contracts) as outlined in the ENSv2 Project Plan. This involves finalising research on which Layer 2 network to migrate to and developing new smart contracts for both Ethereum mainnet (L1) and the chosen L2. The goal is to establish a foundation for a hierarchical registry system, giving each .eth name its own personal registry for greater user control.
What this means: This is bullish for ENS because it addresses core scalability and cost barriers. Successfully selecting a suitable L2 could significantly reduce future gas fees for users, making .eth names more accessible. However, delays in technical research or contract audits are key execution risks.
2. Deploy New Contracts on L1 & L2 (H2 2026)
Overview: This corresponds to Phases 3 & 4 of the project plan: deploying the new ENS contracts on both networks and beginning to sync existing registrations and renewals to the L2 (ENSv2 Project Plan). It marks the technical launch of the ENSv2 architecture, enabling features like role-based permissions for granular name management.
What this means: This is neutral-to-bullish for ENS. A smooth deployment demonstrates technical execution and moves the protocol toward its next generation. For users, it lays the groundwork for enhanced customization and security. The bearish risk is potential smart contract vulnerabilities or migration complexities that could disrupt service.
3. Full Migration to ENSv2 (2026-2027)
Overview: The final Phase 5 involves switching the global resolution process to the new contracts and restarting registrations on the new system (ENSv2 Project Plan). This completes the migration, making L2 the primary layer for .eth management. The vision is to create a "foundation for names" that supports integrations and subnames at scale, as highlighted in the ENSv2 announcement.
What this means: This is bullish for ENS because it aims to unlock mainstream adoption by drastically improving speed, cost, and cross-chain interoperability. If successful, it could catalyze a new wave of registrations and solidify ENS as Web3's identity layer. The long-term risk is competition from other naming services and the challenge of driving user adoption post-migration.
Conclusion
ENS's trajectory hinges on the successful, multi-stage rollout of ENSv2, which promises to transform it from a niche tool into scalable, user-friendly infrastructure for decentralized identity. How quickly will user adoption follow the technical upgrade?