ENS Names Explained: A Beginner's Guide to Human-Readable Crypto Addresses

There's an unspoken ritual in crypto: you hesitate before hitting "Send" because the recipient address looks like `0x71C7656EC7ab88b098defB751B7401B5f6d8976F`. One wrong character and the transaction is gone. ENS exists to fix that.

What Is an ENS Name?

ENS stands for Ethereum Name Service. It's a decentralized naming system on the Ethereum blockchain that converts human-readable names into blockchain addresses. Instead of copying and pasting a 42-character hex string, you can send crypto to `tangem.eth`.

That's the whole idea. A short, readable name that points to a wallet address, just like a domain name like `tangem.com` points to a server's IP address. Think of the name as the line you give another person, not the destination itself. Before a transaction goes out, the wallet still needs the underlying address. That distinction matters when you're starting: a readable name can reduce copying mistakes, but it doesn't replace the normal checks you make before sending crypto.

The `.eth` suffix is the most common form. You register a name, link it to your wallet address, and anyone who sends funds to that name reaches you automatically. It's worth being precise about one thing: the ENS name is not your wallet address. It's a pointer. The address itself still exists underneath; the name is just a human-readable label sitting on top of it.

How ENS Resolution Works

The core mechanism is called address mapping (or resolution). When you type `tangem.eth` into a wallet's Send field, the wallet queries the ENS system, retrieves the wallet address linked to that name, and uses that address for the transaction.

Say you're sending 500 USDT to `alice.eth`. The wallet reads the name first, finds the linked address, and then prepares the transfer to that address. You should still inspect the result before approval. ENS makes the name easier to enter. It does not change the address the blockchain receives. Here's what that looks like in practice. You open your wallet app, tap Send, and type `alice.eth` instead of a long address string. The app resolves the name in the background, confirms the address it found, and you approve the transaction. You never see the hex string at all.

ENS can store more than one address record per name. A single `.eth` name can hold an ETH address, a Bitcoin address, a Solana address, and records for other chains simultaneously. So `alice.eth` could point to different addresses on different networks, all managed from one name. Those records do not have to be limited to one asset. ENS can store an ETH address and additional address records, including Bitcoin and Solana addresses. A wallet still decides which records it can resolve. That's why support matters before you treat a name as a payment address.

There's also a concept called a primary name, which works in the opposite direction. A standard ENS lookup goes name → address. A primary name goes address → name, letting apps display `alice.eth` instead of `0x71C7...` when they look up who owns a given address. Setting a primary name is optional. Apps show your ENS name only when both the forward and reverse records are in place.

ENS resolution currently works across Ethereum and EVM-compatible networks. The primary Layer 2 networks supported include Arbitrum, Base, Linea, OP Mainnet, and Scroll.

ENS and Your Wallet

Not every wallet supports ENS out of the box. With that capability, the wallet's Send flow can accept a `.eth` name and resolve it automatically rather than requiring you to paste the raw address. The Tangem app added ENS support in version 5.28, released September 15, 2025. When you send cryptocurrency through the Tangem app, you can enter a recipient address manually, scan a QR code, or type a `.eth` name directly. The app resolves the name and fills in the address for you.

ENS support is part of the send flow, so the recipient field can start with a name rather than a pasted string. The app then shows the resolved address before you confirm. For a first payment to a new recipient, pause and compare it with an address or QR code the recipient has verified. That matters more than it sounds. When you're sending 500 USDT to a colleague and they give you `colleague.eth`, you type the name, the app shows you the resolved address, and you confirm. No copying, no triple-checking every character. The chance of a typo-induced loss drops significantly.

The Tangem app is free on iOS and Android. When paired with a Tangem hardware card, the transaction is signed offline on the card itself. The app handles the ENS resolution; the card handles the cryptographic signing. Neither step requires the private key to leave the secure element on the card. ENS resolution in the Tangem app works for sending.

What ENS Doesn't Do

• ENS is not a wallet. It doesn't hold funds, generate private keys, or protect anything on its own. It's a naming layer on top of existing addresses.

   

• It's also not universal. ENS is native to Ethereum and EVM-compatible chains. An ENS name can store a Bitcoin address as a record, but the Bitcoin network itself doesn't natively resolve `.eth` names.

   

• And it's optional. You can use crypto indefinitely without ever touching ENS. Long addresses work fine. ENS is a convenience layer for people who send and receive crypto often enough for readability to matter.

Use a name only after the sending wallet has resolved it and shown you the result. If it cannot do that, fall back to a raw address or QR code from the recipient. A name helps at the entry stage. The network still receives the underlying address.

The practical question is whether the wallet or app on the other end supports ENS resolution. If someone sends to `yourname.eth` from a wallet that doesn't resolve ENS, the transaction will fail or go nowhere. Before sharing your `.eth` name as a payment address, it's worth confirming the sender's wallet handles resolution.