Readable crypto handle – replaces 0x… with name.eth for sending ETH, ERC-20s or NFTs in any wallet or dApp
Multi-chain wallet hub – the same name can hold Bitcoin, Solana, Polygon, Base and dozens of other chain addresses through ENS multi-coin records
Reverse record (Primary name) – dApps show your ENS instead of the raw address when you connect your wallet
Portable profile layer – avatar (ENSIP-12), website, email, social links, PGP keys, custom text, etc., live on-chain in the name’s text records
Decentralized website pointer – the contenthash record routes name.eth to IPFS/Arweave/Swarm sites for fully censorship-resistant hosting
Single sign-on for Web3 – apps that implement Sign-In With Ethereum pull your ENS profile as your username/login state
Wallet-to-wallet messaging address – protocols like XMTP let anyone DM you.eth; the ENS name doubles as an inbox ID
Name Wrapper super-powers – wrap any name into an ERC-1155 NFT, burn “fuses” to lock transfers or perms (even make it soul-bound), and wrap sub-names so they’re tradable too
Unlimited sub-names – mint, delegate, airdrop, sell or rent sub-domains (member.yourdao.eth) via your own registrar contract for memberships or ticketing
Bridge Web2 → Web3 – import a DNS domain (.com, .org, etc.) into ENS or link it gas-free with off-chain DNSSEC integration
Off-chain / L2 resolution – CCIP-Read resolvers store records on Layer-2 or in databases while keeping trust anchored to mainnet
Tradable ERC-721 – like any NFT, a name can be transferred, listed, bundled, fractionalized or given as a gift on marketplaces and in wallets (inherent property of ENS ERC-721s)
DeFi collateral – valuable ENS NFTs can be staked on lending platforms (e.g., NFTfi, BendDAO) to borrow ETH or stablecoins
Token-gated access & DAO voting – Snapshot and countless tools read ENS ownership (or specific sub-names) to gate communities, events, airdrops or governance votes
Brand & social identity – appears in Twitter/X handles, Discord names, marketplace profiles, email-style services, AI agents, etc., as a verifiable brand asset
Readable smart-contract alias – map the ENS to a multisig or contract, so collaborators sign “pay.dao.eth” instead of an opaque address
ABI / interface host – store a contract’s ABI under the name so dApps can fetch it automatically (through the ABI() resolver call)
Custom verification records – add DNS-style TXT records (e.g., mp:xmtp, github:user) for service-specific proofs and future integrations
