Overview

The deployment of ENSv2 will require migrating existing names to the new smart contracts, either on Ethereum or Namechain, depending on the name and the user’s preference. This document outlines timelines and processes for each category of ENSv1 name.

Timeline & Prerequisites

ENSv2 is currently slated for launch EOY 2025, which will enable migration. ENSv1 names will function on both ENSv1 and ENSv2 until expiration, without requiring migration. Migrating will however allow users to take advantage of new V2 functionality, including gas cost savings if they choose to migrate to Namechain.

As a result, there is no fixed end time for the migration process. Some names may remain on ENSv1 indefinitely but will continue to function as expected.

Migration Process

While the exact process and requirements for migrating an individual name will vary as outlined below, the overall process for the migration is fixed:

  1. Namechain launches, and ENSv2 contracts are deployed on Ethereum Mainnet and Namechain.
  2. All existing ENSv1 .eth 2LD registration data is copied over to the corresponding registrar contract on Namechain (~1 week).
  3. Registrations and renewals of .eth 2LDs on ENSv1 are halted by disabling all .eth registrar controllers.
  4. Changes to registration data that occurred since the completion of step 2 are copied over, so that the ENSv2 .eth registrar and the ENSv1 .eth registrar are in exact agreement (~6 hours).
  5. Name registration and renewals are enabled on ENSv2.

After the completion of step 5, all registrations and renewals will take place only on ENSv2 on Namechain. It may be possible for users to renew some kinds of ENSv1 names using V2/Namechain without first migrating them (see Considerations, below).

L1 vs L2 Names

When migrating a .eth 2LD, most names users will have a choice of migrating to L1 (Ethereum) or L2 (Namechain).

Migrating to L1 means that the authoritative source for information on the name is on Ethereum, and all operations except renewing the name must take place on Ethereum. This ensures the highest security guarantees for a name, equivalent to ENSv1. No external user or entity can affect the name’s ownership or resolution. Renewal is still accomplished via Namechain, which results in a message being sent to the L1 registry to extend the name’s registration—the only effect an external contract can have on an L1 name. Resolution takes place entirely on Ethereum, unless the owner of the name sets a resolver that queries an external source.

Migrating to L2 means that the authoritative source for information on the name is on Namechain, and all operations affecting the name must take place on Namechain. This allows the user to take advantage of the reduced gas fees on Namechain. The migration process locks the ENSv1 name and sends a message to Namechain, which releases the name to the address nominated by the user. Resolution starts on Ethereum; the L1 .eth resolver uses CCIP-Read to query the registry on Namechain and generate a response.

Pros and Cons: L1 vs L2 Names

Below are the key considerations when choosing between L1 (Ethereum) and L2 (Namechain) for your ENS names:

L1 (Ethereum) Names