{"id":2532,"date":"2026-07-16T09:51:59","date_gmt":"2026-07-16T09:51:59","guid":{"rendered":"https:\/\/nownodes.io\/blog\/?p=2532"},"modified":"2026-07-16T09:52:01","modified_gmt":"2026-07-16T09:52:01","slug":"what-is-ens-and-why-your-wallet-address-needs-a-name","status":"publish","type":"post","link":"https:\/\/nownodes.io\/blog\/what-is-ens-and-why-your-wallet-address-needs-a-name\/","title":{"rendered":"What Is ENS and Why Your Wallet Address Needs a Name"},"content":{"rendered":"\n

An Ethereum wallet address looks like 0x71C7656EC7ab88b098defB751B7401B5f6d8976F<\/code>. It works, but nobody can read it, remember it, or type it without triple-checking every character. ENS<\/strong> \u2014 the Ethereum Name Service<\/strong> \u2014 fixes that by mapping a human-readable name like alice.eth<\/code> to that string, the same way a phone contact hides the actual number behind a name. Cumulatively, more than 2.8 million .eth<\/code> names have been registered since launch, with millions of additional subnames issued by apps on top \u2014 and the service has quietly become the identity layer that wallets, exchanges, and apps build on.<\/p>\n\n\n\n

This guide explains ENS domains from the ground up \u2014 basics first, technical detail after. By the end you’ll know what ENS is, why a plain wallet address is a liability, how it works, what a name costs, who uses it, and how to resolve names in your own app.<\/p>\n\n\n\n

\n\n\n

What Is ENS (Ethereum Name Service)?<\/h2>\n\n\n

Let’s start with the simplest version. ENS is a naming system built on Ethereum that maps short, human-readable names to machine identifiers. Instead of sharing 0x71C7\u2026976F<\/code>, you share yourname.eth<\/code>, and wallets or apps that support it can resolve the right record before sending a supported asset.<\/p>\n\n\n\n

\n

ENS (Ethereum Name Service):<\/strong> an open, Ethereum-based protocol that maps human-readable names (like nick.eth<\/code>) to machine identifiers \u2014 wallet addresses for supported networks, content hashes, text records, avatars, and other metadata. It’s the Web3 counterpart to the Domain Name System that runs the web.<\/p>\n<\/blockquote>\n\n\n\n

The comparison people reach for is DNS, and it’s a good one. When you type a website into a browser, DNS translates that name into the numeric IP address a server actually uses. ENS performs a similar naming function for blockchain applications \u2014 except instead of pointing a name at an IP address, it points a name at a wallet address or another record.<\/p>\n\n\n\n

That single idea unlocks a lot. A .eth<\/code> name isn’t limited to one Ethereum address: through its resolver it can also store a Bitcoin address, a decentralized website, an avatar, and social handles \u2014 many record types under one label you control.<\/p>\n\n\n

ENS vs. DNS: The Key Difference<\/h3>\n\n\n
\"\"<\/figure>\n\n\n\n

Here’s the distinction that matters. DNS is managed through registrars and servers that a handful of organizations oversee. ENS records live on Ethereum as smart contracts, so control is defined by code rather than a registrar account \u2014 though that control isn’t unconditional, as expiry and subnames show below.<\/p>\n\n\n\n

You can also bring a domain you already own \u2014 a .com<\/code>, .org<\/code>, or .xyz<\/code> \u2014 into ENS after proving control through DNSSEC, so it isn’t limited to native .eth<\/code> names. That control stays tied to ownership of the underlying DNS name, so the protocol extends the web’s naming system rather than replacing it.<\/p>\n\n\n\n

\n\n\n

Why Your Wallet Address Needs a Name<\/h2>\n\n\n

Now the practical case: raw addresses are hostile to humans, and that hostility has a real cost.<\/p>\n\n\n\n

If you’ve ever pasted 0x382\u2026<\/code> into a wallet, you know the jolt of anxiety that follows. A random typo usually produces an invalid address that the wallet simply rejects \u2014 the real danger is copying or entering a different valid<\/em> address, in which case the funds go there and the transfer is irreversible. Sending to a readable yourname.eth<\/code> sidesteps the hardest part of that check.<\/p>\n\n\n\n

This is important:<\/strong> ENS reduces address-entry errors but does not eliminate them. You can still select the wrong name, land on a compromised interface, or resolve a maliciously configured record, so verifying the destination still matters.<\/p>\n\n\n\n

The upside compounds across the addresses a typical user juggles. You might keep one wallet for holdings, another for NFTs, and a hardware wallet for savings, then attach readable subnames \u2014 nfts.alice.eth<\/code>, savings.alice.eth<\/code> \u2014 to each. One name can serve as a portable identity across wallets and apps, as far as those wallets, networks, and record types support it.<\/p>\n\n\n\n

\n\n\n

How ENS Actually Works Under the Hood<\/h2>\n\n\n

Time to open the box. The service isn’t a single database; it’s a set of smart contracts that hand work off to each other. Three pieces do the heavy lifting, and the official ENS docs<\/a> break them down like this.<\/p>\n\n\n\n

Component<\/th>What It Does<\/th><\/tr><\/thead>
Registry<\/strong><\/td>A single core contract that records, for each name, its owner, its resolver, and a time-to-live value (TTL). It’s the master index.<\/td><\/tr>
Resolver<\/strong><\/td>The contract that stores and returns the actual data \u2014 the wallet address, content hash, or text records a name points to.<\/td><\/tr>
Registrars<\/strong><\/td>Contracts that issue names: the .eth<\/code> Registrar hands out native names, and the DNS Registrar handles imported domains. The Reverse Registrar is different \u2014 it manages reverse records and primary-name configuration rather than issuing names.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

The resolution flow is simpler than the component list suggests. To resolve a name, an app first asks the Registry which resolver is responsible for alice.eth<\/code>, then asks that resolver for the record it wants \u2014 say, the Ethereum address. Two lookups, and the name becomes an address.<\/p>\n\n\n

Forward vs. Reverse Resolution<\/h3>\n\n\n
\"\"<\/figure>\n\n\n\n

There are two directions to this, and both matter. Forward resolution<\/strong> is the common one: name in, address out (alice.eth<\/code> \u2192 0x71C7\u2026<\/code>). Reverse resolution<\/strong> goes the other way, turning an address back into a name so a wallet can display alice.eth<\/code> instead of a hex string.<\/p>\n\n\n\n

\n

Primary Name (reverse record):<\/strong> the name an address chooses to be known by. Setting it lets apps show your name next to your address, and per the docs, reverse records now work on Ethereum mainnet and major Layer 2 networks including Base, OP Mainnet, Arbitrum, Scroll, and Linea.<\/p>\n<\/blockquote>\n\n\n

Names Are Tokens You Register<\/h3>\n\n\n

One detail trips up newcomers: a .eth<\/code> name is a token. Second-level .eth<\/code> registrations are ERC-721<\/strong> NFTs, while names in the Name Wrapper use the ERC-1155<\/strong> standard \u2014 so not every name is represented the same way (how ENS names evolved<\/a>). Either way, you can hold, transfer, or sell it.<\/p>\n\n\n\n

Be precise about what ownership means, though. A .eth<\/code> name is a time-limited registration<\/strong>: you control a transferable token for as long as the name stays registered, but it expires if you don’t renew. No traditional registrar account controls it, yet the registration stays subject to expiration and the rules enforced by the registrar contracts.<\/p>\n\n\n\n

That token model is also what makes subnames<\/strong> powerful. If you own company.eth<\/code>, you can issue alice.company.eth<\/code> and thousands more \u2014 but by default the parent owner can still replace, revoke, or modify a subname unless those permissions are restricted through the Name Wrapper. That trade-off is exactly what makes subnames useful for businesses.<\/p>\n\n\n\n

\n\n\n

How Much Does an ENS Name Cost?<\/h2>\n\n\n

Prices are refreshingly simple, and shorter names cost more because there are fewer of them. According to the ETH Registrar docs<\/a>, the annual fees are USD-denominated:<\/p>\n\n\n\n

Name length<\/th>Annual fee (USD, paid in ETH)<\/th><\/tr><\/thead>
5+ characters<\/td>$5 \/ year<\/td><\/tr>
4 characters<\/td>$160 \/ year<\/td><\/tr>
3 characters<\/td>$640 \/ year<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

A few things to know. The minimum length is three characters. Fees are denominated in USD but paid in ETH<\/strong>, converted at registration time, plus a variable gas fee<\/strong>. Because ETH’s price moves, wallets add a small buffer (~3\u201310%) and refund any excess in the same transaction.<\/p>\n\n\n\n

There’s also a premium on recently expired names, and the timing matters. A .eth<\/code> name first enters a 90-day grace period<\/strong> in which only the previous owner can renew it. Only after that does it go into a 21-day temporary premium<\/strong> \u2014 a Dutch-auction mechanism that starts near $100 million and decays toward $0 \u2014 which exists to stop snipers from instantly grabbing valuable expired names.<\/p>\n\n\n\n

Registering is permissionless: anyone can visit the ENS Manager App<\/a>, type a name, choose a duration, and confirm. There’s no account, no approval, and no gatekeeper \u2014 much like buying a domain, minus the company in the middle.<\/p>\n\n\n\n

\n\n\n

ENS for Business: Who Actually Uses It<\/h2>\n\n\n

This is where ENS stops being a novelty and becomes infrastructure. For a business, a name does three jobs at once: it simplifies payments, signals that you’re crypto-native, and \u2014 through subnames \u2014 gives customers or staff an identity under your brand.<\/p>\n\n\n\n

Payments are the obvious win. A customer resolving store.eth<\/code> in a supporting wallet is less likely to fumble the transfer than one hand-copying a 42-character address \u2014 fewer failed transactions and support tickets. The same pattern scales to teams: a company can issue alice.company.eth<\/code> and bob.company.eth<\/code> under one name.<\/p>\n\n\n\n

The adoption numbers show this isn’t theoretical. A few of the largest deployments:<\/p>\n\n\n\n