Skip to main content

What ENS does

ENS turns blockchain addresses into names. yourbrand.eth resolves to your addresses across chains, your website, and your public profile, all from one name you own.

What subnames unlock

ENS gives one readable name to one owner. Subnames turn that name into a namespace: whoever owns brand.eth can issue alice.brand.eth to a user, pay.brand.eth to a payment endpoint, agent.brand.eth to an AI agent, and thousands more. ENS profile showing Ethereum, Base, Bitcoin, and Solana address records for one name

Subnames become

  • Readable payments: Replace copying addresses with typing names.
  • Branded identity: Users carry your brand name identity everywhere onchain.
  • Portable profiles: Public addresses and text records all ENS-integrated clients can resolve.
  • Agent identity: Agents get a name, a wallet, and more records other agents can check.
  • Decentralised hosting: Point a subname to content hosted on IPFS or other decentralised storage to serve websites and other static content.
See Use cases for examples across wallets, payments, AI agents, chains, games, and communities.

Benefits

  • Better UI/UX: Users send to a readable name instead of a 42-character hex string.
  • Smoother onboarding: Users claim a name at signup, not a wallet address.
  • Higher retention: A name is an identity users own. An address is not.
  • Existing network: No integrations to chase. 1,000+ apps already support ENS.
  • Portable identity: Profiles and addresses resolve in any ENS-compatible app.
  • Optional revenue: Charge for renewals or premium names, or keep issuance free.
  • Stronger security: Showing a name and avatar helps users verify a recipient, which can reduce address-poisoning and lookalike-address scams.
  • Brand distribution: Users carry your brand into every app they touch, and every transaction becomes a brand impression.

Offchain or onchain

Namespace issues subnames in two ways. Both resolve in ENS apps, and both work under the same parent name. Start with offchain subnames unless users need to hold the subname themselves.

Offchain subnames

Namespace stores offchain subnames and their records, and ENS clients resolve them through CCIP Read. Creating or updating one needs no blockchain transaction. Offchain subnames aren’t NFTs. The parent-name owner controls issuance and updates through the Namespace App or with an API key. Compatible ENS clients read their address, text, and content-hash records through the Namespace resolver.

Create offchain subnames—no code

Create and manage offchain subnames and their ENS records in the Namespace App.

Integrate offchain subnames into your product

Use the Offchain Manager SDK to issue gasless subnames and manage their records.

Onchain subnames on Ethereum

Onchain subnames are minted in the ENSv2 registry on Ethereum (L1). The wallet that mints a subname owns it as an onchain asset and can transfer it. You set the rules when you activate your name: a one-time or yearly price in dollars, paid in USDC or DAI, plus optional pricing tiers, reservations, a mint window, a whitelist, or token gating. Minters pay your price plus Ethereum gas. Activation needs an ENSv2 name.

Enable onchain subname minting—no code

Activate your ENS name, set prices and rules, and let people mint subnames through Namespace.

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. See Getting started for the no-code and developer paths for each model.