One Name, Every App: ENS as Portable Web3 Identity
Most of us have a dozen identities online and control none of them. Your handle on one platform, your profile picture on another, your follower list held hostage by whichever company owns the servers. The Ethereum Name Service proposes something quieter and stranger: your identity lives in a name you own, and apps read from it.
Text records: a profile you carry
Every ENS name can store key-value text records, and this is where a name stops being a redirect and starts being a person.
avatar— point it at an image or an NFT you hold, and apps that support ENS will show it as your profile picture automatically.urlanddescription— your site and your one-line bio, readable by anything.- Social handles — records for platforms like X and GitHub let apps display verified-looking links from one source.
contenthash— the record that points a name at a decentralised website.
Update the record once and every app that reads it updates too. There is no "change your photo in fourteen places" ritual. The full record list lives in the ENS documentation.
Subnames, and giving identity away
A name owner can issue subnames — team.yourname.eth, shop.yourname.eth, one per collaborator or department. That turns a single registration into a namespace you administer. Communities use it for member handles; studios use it to give every artist an address under the studio banner. It is the closest thing Web3 has to issuing company email, except the recipients actually own their piece of it.
Websites that nobody can unplug
Set a contenthash to a site stored on IPFS and your name serves a real website — reachable through gateways like eth.limo without a hosting bill or a takedown button. It is not a replacement for every site, but for a manifesto, a portfolio, or a project's canonical page, it is remarkably durable.
Signing in with a name
Plenty of apps now let you connect a wallet and greet you by your primary ENS name instead of a hex string. That is a small UX detail with a large consequence: the login is yours, the reputation attached to it is yours, and it travels between apps that never coordinated with each other. Announcements and ecosystem updates run through @ensdomains, and you can manage everything at app.ens.domains.
We covered the wider version of this idea in avatars as assets and identity, and the trust question in how to verify digital asset ownership.
How Nexaria uses your name
At Nexaria Digital an identity you own makes the marketplace better, not just prettier:
- Verified Creator badges anchored to a name people already recognise across Web3.
- Buyer-only unlockable content and Fan Passes, delivered to a name rather than to a platform account you could lose.
- Storefronts in the showcase that read your avatar and links straight from your records.
- Naming adapters documented at /developers, our path for supporting more identity protocols over time.
That is the direction we are building toward: one name, recognised everywhere, carrying your work with it. More on the reasoning in our resources.
The realistic version
Not every app reads ENS, and losing the wallet loses the identity. But a name you own is the sturdiest profile the open web has offered in years.
This post is educational, not financial advice — always do your own research. Protocol details come from the public pages linked above and may change; corrections are welcome at our contact page.
