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
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.
@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.
Wallets don't read your database.They read ENS.
- MetaMask → ENSresolve
- ENS → MetaMaskOffchainLookup
- MetaMask → GatewayCCIP-Read
- Gateway → Your APIGET /alice
- Your API → Gateway200 OK
- Gateway → MetaMasksigned answer
- MetaMask → ENSverify
- ENS → MetaMask0x4A7D…31da
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.
How to turn your usernames into ENS names
One endpoint and one transaction. Nothing to deploy.
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.
Save it in the Namespace App
Add your endpoint in the Namespace App. Namespace hosts the gateway, so there is nothing to deploy.
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
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.
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.
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.
Questions teams ask us





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!
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.
ENS is the future, and Namespace offers critical tools for making that happen
Namespace is providing a magical service. They made issuing thousands of subdomains for ETHDenver attendees simple and nearly effortless.
When I was exploring ways to launch a local onchain music community, Namespace immediately came to mind. Their tooling made it effortless.
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 💛
Our collaboration with Namespace and the Web3.js Plugin went really well. The plugin enabled developers to register and interact with ENS domains.
Namespace helped PizzaDAO's members mint subnames to show their affiliation all over the metaverse. The pizza flavored minting website is *chef's kiss*.
Our experience working with Namespace has been exceptional. Their team combines strong technical expertise with clear communication and a true spirit of partnership.
From simple to complex Subname needs, Namespace has the tools and expertise to make it happen. Fully recommend.
You've developed an innovative and frictionless way for people to monetize their domains, empowering users to unlock new value with ENS.
We have found in Namespace an efficient partner that quickly understood our needs and provided very solid solutions
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.
Namespace is the best tool for creating and issuing ENS subdomains, I think. The dashboard is very easy to use.
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.
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.
Build the endpoint
The response format, coin types and auth options, in the developer guide.
Bring a registry to ENS
Chains and name services with an existing registry. Let's scope it on a call.













