ENSv2 Upgrade Proposal Would Freeze New .eth Registrations

A proposal to deploy the second version of the Ethereum Name Service (ENS) on the mainnet has entered the draft stage, setting up a governance vote that could permanently alter how .eth domains are registered and managed.

ENS founder Nick Johnson submitted an executable draft calling for the activation of ENSv2. The upgrade would immediately halt new registrations under the original registrar contract while preserving renewal capabilities for existing domain holders. No date has been set for the required onchain vote.

The transition carries a brief operational disruption. Once the DAO authorizes activation and domain records synchronize between the legacy and upgraded systems, new .eth registrations will shift entirely to ENSv2. Johnson cautioned that neither system will process new registrations for several hours during that cutover window.

Existing owners face no mandatory migration deadline. Their current .eth names will continue resolving normally on the original registry. ENS Labs has pre-reserved all active names within the ENSv2 architecture, allowing holders to move their domains to the new contracts at their own pace.

The architectural overhaul replaces the rigid permission model of the 2019-era ENS registry with a more flexible framework designed to support complex delegation and subdomain management. This redesign addresses long-standing developer friction; building decentralized applications or wallets that rely on hierarchical naming structures previously required workarounds because the original registry locked certain administrative functions behind static ownership rules.

Approval of ENSv2 also triggers a structural shift in protocol control. ENS Labs intends to hand over its remaining administrative privileges on the upgraded smart contracts directly to the decentralized autonomous organization upon activation. While the DAO already governs treasury allocations and protocol parameters through ENS token voting, core registry contracts have historically retained some centralized deployment oversight by the founding team. Transferring those final keys would complete the project’s transition to full community administration, a milestone few major Web3 infrastructure protocols have achieved without fragmenting their user base.

Passing the measure requires navigating strict governance thresholds. Under current ENS rules, executable proposals demand participation from at least 1 million ENS tokens — roughly 1% of the total supply — alongside majority approval during a seven-day voting window. Successful votes then enter a mandatory two-day timelock before any code executes onchain, providing a final buffer for users to prepare.

The push toward ENSv2 arrives as the broader Ethereum ecosystem accelerates upgrades to its foundational layers. Recent mainnet deployments, including privacy-preserving API payment infrastructure like zkAPI, reflect a wider industry effort to mature base-layer utilities beyond simple asset transfers. As the primary human-readable addressing layer for Ethereum wallets and decentralized websites, ENS handles resolution for millions of accounts, making the stability of this proposed migration critical for everyday network activity.

The executable draft remains open for community review ahead of formal submission to the governance portal.