Universal Usernames

Your usernames, in every wallet that reads ENS

Your users already have names. Make each one work in other wallets and apps as an ENS name like alice.brand.eth. No minting, no migration, no cost per user.

10M+ subnames25M+ resolutions35+ partnersBacked by ENS DAO

How Universal Usernames work

Universal Usernames makes every username in your app work as an ENS name. Users keep their wallet, address and username. @alice in your app also resolves as alice.brand.eth anywhere ENS works. You add one read-only endpoint, and Namespace runs the gateway and signs the answers. Nothing is minted or copied out of your database.

FreeNo migrationNo gas per user.eth or DNS namesEVM, BTC and SOL addresses
01The problem

@alice in your app is0x4A7D…31da everywhere else.

Say your wallet address from memory. Nobody can. Your users remember @alice, but no other wallet can look it up.

The username is real. It's locked in your database.

Inside your app, @alice is how people find, pay, and follow each other. It's on profiles, history and leaderboards. But outside your app, no wallet or app can look it up, so your users can't use it.

Nobody can send to @alice from another wallet.

Type @alice into MetaMask and nothing comes back, so the sender copies a 42-character address and checks the first and last four characters. One wrong paste, or one poisoned address in their history, and the funds are gone for good.

Every username you issued is reach you're not getting.

Your users transfer, mint and trade all over the chain, and every bit of it shows up as 0x4A7D…31da. With alice.brand.eth, that activity would put your brand in front of everyone they deal with.

02How a lookup works

Wallets don't read your database.They read ENS.

Lookupwhat the wallet asks for
Wallet
Name
Address
  1. MetaMask → ENSresolve
  2. ENS → MetaMaskOffchainLookup
  3. MetaMask → GatewayCCIP-Read
  4. Gateway → Your APIGET /alice
  5. Your API → Gateway200 OK
  6. Gateway → MetaMasksigned answer
  7. MetaMask → ENSverify
  8. ENS → MetaMask0x4A7D…31da
Lookupwhat the wallet asks for
Wallet
Name
Address
MetaMasklooks up alice.brand.eth
Ask ENSresolve the name
Call the gatewaywhere ENS pointed it
Verify through ENSchecks the gateway’s signature
ETH—
Mintednothing
Gas paidnone
ENSyour name’s resolver
Namealice.brand.eth
Resolverwildcard
Answer—
Gatewayhosted by NamespaceCCIP-Read
Receivethe wallet’s CCIP-Read call
Find your endpointsaved in the Namespace App
Call your APIread-only, over HTTPS
Sign the answerno key for you to hold
Your APIapi.brand.com, read-onlyyour database
RequestGET /alice
Usernamealice found
AddressETH · 0x4A7D…31da
Profileavatar, url
Response200 OK
Pick a wallet, a name and an address, then run it. Try zoe, who isn't one of your users.

One resolver for every name

Wildcard resolution (ENSIP-10) means one resolver answers for every username under your name, including users who sign up tomorrow.

Signed, then verified

The gateway signs each answer and the wallet checks it through the ENS resolver (EIP-3668), the same way it checks any CCIP-Read name.

Nothing for you to run

Namespace hosts the gateway and holds the signing key. Unknown usernames get a 404 from your API and don't resolve.

03How it works

How to turn your usernames into ENS names

One endpoint and one transaction. Nothing to deploy.

01

Bring one read-only endpoint

GET {base}/{username} returns the user's addresses and text records, and 404 for unknown usernames. A bearer token is optional.

02

Save it in the Namespace App

Add your endpoint in the Namespace App. Namespace hosts the gateway, so there is nothing to deploy.

03

Switch the resolver once

One transaction on your parent name. Its own records are copied before the switch. Every existing and future username resolves immediately.

Your usernames today, and with Universal Usernames

In-app usernames
Universal Usernames
Where @alice works
Only inside your app
Your app, plus wallets and apps that support ENS
Getting paid from another wallet
Copy and paste a hex address
Send to alice.brand.eth
What other apps show
0x4A7D…31da
alice.brand.eth, with avatar and profile
Your brand outside the app
Nowhere
In every name and transaction
Where the usernames live
Your database
Still your database, nothing copied
Cost
Nothing
Free, no gas per user, sponsored by ENS DAO
04Who it's for

If your users already have a username and a wallet in your app, this is for you.

Neobanks and payment apps

Users get paid as alice.yourbank.com from any wallet, with your brand on every payment.

Trading and prediction apps

The names on your profiles and leaderboards become names anyone can send to.

Wallets with in-app handles

The handle a user picked in your wallet works in other wallets too.

Games and social apps

Player and creator @handles that anyone can pay, tip or look up from any wallet.

Chains and name services with a registry

Bring your registry to ENS, like Rootstock: alice.rsk resolves as alice.rsk.eth, through a gateway built by Namespace.

05Why Namespace

Why builders choose Namespace

Namespace is the ENS DAO-backed service provider. We run the gateway, so your side of Universal Usernames is one read-only endpoint.

In-house
Namespace
CCIP-Read gateway
You build, host and monitor it
Hosted and monitored by Namespace
Signing key
You hold, secure and rotate it
Nothing to hold
Wildcard resolver
You write, audit and deploy it
Already deployed. Switch once
Standards work
You track EIP-3668 and ENSIP-10 yourself
Follow and actively contribute
Engineering to production
Weeks of plumbing
One endpoint and one transaction
Lock-in
None, but you maintain it all
None: your parent name stays yours and you can switch its resolver back at any time
10M+Subnames issued
25M+Resolutions served
35+Partnerships and integrations
221Namespaces issuing subnames with us
Trusted byCeloFilecoinPOAPUnicorn
ENS DAO Service Provider

The business case

Every username you already issued becomes a name people can pay from any wallet, and your brand travels with it.

  • Users get paid by name from outside your app
  • Your brand in every wallet that resolves alice.brand.eth
  • Roll out to your whole user base at no per-user cost

Our pricing

Universal Usernames is free. No per-user fee and no gas per user. The only cost is the gas for the one-time resolver switch on your parent name.

FreePer username, existing and new
0Transactions per sign-up
1Setup transaction on your parent name
FAQ

Questions teams ask us

What are Universal Usernames?

Universal Usernames makes every username your app already issued work as an ENS name. A user called alice in your app resolves as alice.brand.eth. ENS asks a gateway hosted by Namespace, the gateway calls your API, and the wallet verifies the signed answer. Nothing is minted and nothing leaves your database.

Is it free?

Yes. There is no per-user cost and no gas per user. The only transaction is the one-time resolver switch on your parent name.

Is it onchain? Do users get an NFT?

Your parent name and its resolver are onchain. The usernames are not. They resolve offchain through CCIP-Read (EIP-3668) and wildcard resolution (ENSIP-10), so there is no NFT per user, no minting and no record syncing. To a wallet, alice.brand.eth works like any other ENS name.

Can we use a DNS domain instead of a .eth name?

Yes. Use a .eth name or a DNS domain imported into ENS, so alice can resolve as alice.brand.id.

Who owns the names?

Your app does. The usernames live in your database and resolve under your name, so users can't take them elsewhere. For the same reason, never recycle usernames: if a new user gets an old username, every wallet that looks it up gets the new user's address.

Which wallets resolve Universal Usernames?

Any wallet or app that supports CCIP-Read, which the major Ethereum libraries do. A wallet without CCIP-Read support won't resolve the name.

What data becomes public?

Everything your endpoint returns. Anyone who looks up a username can read the addresses and text records you serve for it, so only return what you want public.

How is this different from offchain subnames?

Offchain subnames are created and stored in Namespace. Universal Usernames reads the usernames you already have from your own API, so there is nothing to create or import. A name uses one or the other: turning on Universal Usernames replaces any offchain or L2 subnames on that same name.

ENS partner avatar
ENS partner avatar
ENS partner avatar
ENS partner avatar
ENS partner avatar
Join 35+ Partners

Wall of Love

The Namespace team have been very proactive and supportive of our timelines to build an integrations with our offering. Definitely recommend working with them!
Joan testimonial photo

Joan

Founder of OpenFort

Namespace has been a core partner for PinMe. Their APIs are extremely easy to use, their subdomain infrastructure is stable and built for the long term.
Ted testimonial photo

Ted

Co-founder of PinMe

ENS is the future, and Namespace offers critical tools for making that happen
brantly.eth testimonial photo

brantly.eth

Founder of EFP

Namespace is providing a magical service. They made issuing thousands of subdomains for ETHDenver attendees simple and nearly effortless.
Griff.eth testimonial photo

Griff.eth

Founder of Unicorn & Giveth

When I was exploring ways to launch a local onchain music community, Namespace immediately came to mind. Their tooling made it effortless.
Marcus testimonial photo

Marcus

ENS DAO

Y'all are killing it and I think every product should have their own subname. And y'all are now my go-to rec. Love y'all 💛
Jesse Pollak testimonial photo

Jesse Pollak

Founder of Base

Our collaboration with Namespace and the Web3.js Plugin went really well. The plugin enabled developers to register and interact with ENS domains.
Santiago testimonial photo

Santiago

DevRel at Web3js

Namespace helped PizzaDAO's members mint subnames to show their affiliation all over the metaverse. The pizza flavored minting website is *chef's kiss*.
snax.eth testimonial photo

snax.eth

Head of Stuff at PizzaDAO

Our experience working with Namespace has been exceptional. Their team combines strong technical expertise with clear communication and a true spirit of partnership.
Kate testimonial photo

Kate

Head of Product & GTM @ CELO

From simple to complex Subname needs, Namespace has the tools and expertise to make it happen. Fully recommend.
Simon testimonial photo

Simon

Lead DevRel @ ENS Labs

You've developed an innovative and frictionless way for people to monetize their domains, empowering users to unlock new value with ENS.
Alex Netto testimonial photo

Alex Netto

Founder of Blockful

We have found in Namespace an efficient partner that quickly understood our needs and provided very solid solutions
Patricio testimonial photo

Patricio

Founder of POAP

Namespace has quickly become the go-to platform for managing ENS subnames. What was once confusing and error-prone is now a streamlined, intuitive experience.
Ben testimonial photo

Ben

Co-founder of ETH.LIMO

Namespace is the best tool for creating and issuing ENS subdomains, I think. The dashboard is very easy to use.
Sahil testimonial photo

Sahil

DevRel at QuickNode

The Namespace team is incredibly friendly and a pleasure to work with. Their passion and dedication to the ENS ecosystem are evident in everything they do.
Thomas Clowes testimonial photo

Thomas Clowes

Co-founder of Unruggable

One endpoint,every username live

Your users already have the names. Let them work everywhere.

Set it up in the app

Save your endpoint and switch the resolver from the Namespace App.

Set up Universal Usernames in the Namespace App

Build the endpoint

The response format, coin types and auth options, in the developer guide.

Universal Usernames developer guide

Bring a registry to ENS

Chains and name services with an existing registry. Let's scope it on a call.

Partner with Namespace to bring a name registry to ENS