Deployments

ENS is multichain (read more here) and can be used in any application. In addition to being able to query many address formats and record types, data can be stored practically anywhere. However, resolution needs to start somewhere, so the entrypoint for resolution is Ethereum Mainnet, alongside the most popular testnets.

Deployments

Below you will find an abbreviated list of our latest contract deployments. The source of truth for ENS contract deployments is the ensdomains/ens-contracts repository.

Mainnet

Interact with ENS on Ethereum Mainnet via app.ens.domains.

Sepolia (ENSv2 Beta)

For name resolution to use the hackathon deployment, the Universal Resolver address built into viem and ethers must be overwritten once in your code with the hackathon Universal Resolver (UpgradableUniversalResolverProxy in the table below):

import { createPublicClient, http } from 'viem'
import { sepolia } from 'viem/chains'
 
// Sepolia with the hackathon Universal Resolver instead of the built-in one
const hackathonSepolia = {
  ...sepolia,
  contracts: {
    ...sepolia.contracts,
    ensUniversalResolver: {
      address: '0xd26f2040d083af1cd2962ba303f4bea0c4faf142',
    },
  },
} as const
 
const client = createPublicClient({
  chain: hackathonSepolia,
  transport: http(),
})
 
// getEnsAddress, getEnsName, getEnsText, ... now resolve
// against the hackathon deployment

Sepolia (Legacy)

Holesky

Interact with ENS on the Holesky testnet via holesky.app.ens.domains.

But what about multichain?

While the core ENS protocol lives on Ethereum Mainnet, it can be used to resolve data for any chain!