Browse all documentation
Documentation home
Get started
Platform overviewConnect a walletSafety, simulation, and signing
Find names
Expiry ExplorerAI domain searchDiscover and collectionsBulk searchENS lookup and domain details
Trade names
Browse the marketplaceBuy a listed nameList a name for saleBulk list namesActivity and collectionsMake, manage, and accept offersLeaderboard and market analyticsLive market pulse and network activity
Manage names
Portfolio dashboardPublic Portfolio 2.0Renewals and gas planningBulk edit records and resolversTransfers and subnamesSet a primary ENS nameWatchlist and notificationsLive calendar subscriptionsSaved-search monitorsUnified action inboxPublic profiles and share cards
Agent platform
Agent platform overviewLaunch an ENS-native agentAgent directory and profilesCapability health checksIntent routingPolicy-bound agent sessionsAgent jobs, quotes, and escrow evidenceCreate and control agent fleetsControl-plane canary evidence
Developers
MCP quickstartComplete MCP tool catalogueDeveloper accounts, sandbox, quotas, and Base subscriptionsUnsigned transaction plansAgent identity standardsPublic APIs and manifestsMarketplace integration
Reference
ENSv2 public betaENS lifecycle and status meaningsFees and displayed totalsTroubleshooting
Reference · 1 of 4

ENSv2 public beta

Switch safely between Ethereum mainnet ENSv1 and the Sepolia ENSv2 beta.

betaENSv2 public beta · SepoliaVerified 2026-08-14Owner: ENS.Tools Protocol Integration
Open this feature

ENS.Tools can inspect the public ENSv2 beta on Sepolia without changing the default Ethereum mainnet experience. The selected protocol and network are explicit, use separate deployment addresses, and must never be inferred from a name alone.

Ethereum mainnet ENSv1 remains the default production network.
The header network control exposes the Sepolia ENSv2 beta as an explicit opt-in.
Domain detail identifies protocol version, registry, registrar, resolver, ownership chain, and migration state.
Hierarchical registry and resolver diagnostics show the root-to-leaf chain instead of flattening ENSv2 into one object.
Mainnet and beta caches, clients, contract addresses, and transaction preparation stay network-scoped.
Production contract

Before you run this workflow

Networks

  • Ethereum mainnet ENSv1
  • Sepolia ENSv2 public beta

Prerequisites

  • An explicit network selection
  • Sepolia test ETH only for beta transactions

Wallet permissions

  • None for reads
  • A separately reviewed Sepolia signature for beta state changes

Expected result

  • Network-scoped registry, registrar, resolver, ownership, and migration evidence

Errors and recovery

  • Confirm the protocol badge
  • Clear stale network selection by switching explicitly
  • Never reuse a beta contract target on mainnet
Workflow

How to use it

  1. 1

    Choose the beta deliberately

    Use the network control and confirm Sepolia ENSv2 beta is visible before interpreting a result or preparing an action.

  2. 2

    Read the protocol badge

    Confirm the page reports the intended chain and protocol version; the same label can have unrelated state across deployments.

  3. 3

    Inspect the resolution chain

    Check every parent, registry, resolver, and leaf result. A missing link should remain explicit rather than being replaced by mainnet data.

  4. 4

    Switch back for production

    Return to Ethereum mainnet before managing production .eth names or reviewing mainnet marketplace and portfolio evidence.