> ## Documentation Index
> Fetch the complete documentation index at: https://docs.namespace.ninja/llms.txt
> Use this file to discover all available pages before exploring further.

# Namespace ENSv2 migration

> What ENSv2 changes for your names and subnames.

## What is ENSv2?

[ENSv2](https://ens.domains/blog/post/ensv2-live-on-mainnet) is the new version of ENS, now live on Ethereum mainnet. New `.eth` names are registered on ENSv2. Names registered before it are ENSv1 names, and they keep resolving. See the [ENSv2 overview](https://docs.ens.domains/ensv2/overview) in the ENS docs.

## Do I need to do anything for my existing offchain subnames?

No. Offchain subnames work with ENSv1 and ENSv2 names. Namespace stores them and their records, and ENS clients resolve them through CCIP Read.

## What happens if I upgrade my name to ENSv2?

Upgrading resets the name's resolver. If the name has offchain subnames, [set the Namespace resolver again](https://docs.namespace.ninja/user-guide/dev-portal.md#configure-the-resolver) so they keep resolving. Your subnames, API keys, and SDK code don't change.

## Do my onchain listings move to ENSv2?

No. Listings on ENSv1 names stay on ENSv1, keep working, and can still be edited. See [ENSv1 listings](https://docs.namespace.ninja/user-guide/app.md#ensv1-deprecated) in the Namespace App guide.

## I'm using Mint Manager, Indexer Manager, or the Mint API. What now?

They're deprecated. They keep working for existing ENSv1 listings but don't support ENSv2 names. See [Mint Manager](https://docs.namespace.ninja/developer-guide/sdks/mint-manager.md), [Indexer Manager](https://docs.namespace.ninja/developer-guide/sdks/indexer-manager.md), and the [Mint API reference](https://docs.namespace.ninja/api-reference/mint-manager/estimate-mint-params.md).

## Which products work with ENSv2?

| Product | ENSv1 names | ENSv2 names |
| - | - | - |
| [Offchain subnames](https://docs.namespace.ninja/user-guide/dev-portal.md) in the App, SDK, and API | Yes | Yes |
| [Onchain subnames](https://docs.namespace.ninja/user-guide/app.md) in the Namespace App | Existing listings only | Yes, on Ethereum (L1) |
| [Resolvio](https://docs.namespace.ninja/user-guide/resolvio.md) | Yes | Yes |
| [ENS Widget](https://docs.namespace.ninja/user-guide/ens-widget.md) and [Subpages](https://docs.namespace.ninja/user-guide/subpages.md) | Existing listings only | No |
| Mint Manager, Indexer Manager, and the Mint API | Existing listings only | No |

## What about L2 subnames?

New L2 subnames are coming soon. Subnames already minted on Base and Optimism keep resolving, and their owners don't need to do anything.

## Where do I start with a new name?

Pick offchain subnames for gasless, high-volume issuance: use the [Namespace App](https://docs.namespace.ninja/user-guide/dev-portal.md), the [SDK](https://docs.namespace.ninja/developer-guide/guide/create-offchain-subnames.md), or the [API](https://docs.namespace.ninja/api-reference/introduction.md). Pick onchain subnames on Ethereum when users should own them: [activate your name](https://docs.namespace.ninja/user-guide/app.md#activate-your-ens-name) in the Namespace App.

## Continue where you left off

> [card] [Developer quickstart](https://docs.namespace.ninja/developer-guide/quickstart.md)
>
> Pick your first Namespace integration.

> [card] [Create offchain subnames](https://docs.namespace.ninja/developer-guide/guide/create-offchain-subnames.md)
>
> Go from API key to a resolved name with the SDK.

> [card] [Offchain subnames](https://docs.namespace.ninja/user-guide/dev-portal.md)
>
> Configure the resolver and manage subnames in the Namespace App.

> [card] [Namespace App](https://docs.namespace.ninja/user-guide/app.md)
>
> Activate your name and issue onchain subnames.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.