ENS: Turning Wallet Addresses Into Names

Ethereum Name Service (ENS) launched in 2017 as a decentralized naming system for Ethereum. Instead of sending ETH to 0x7a3b…4f2c, you could send it to vitalik.eth. The concept was borrowed from DNS (the system that turns domain names into IP addresses) but built on Ethereum smart contracts. ENS names were NFTs — owned by the registrant, tradeable on secondary markets, and resolvable by any compatible wallet or application.

ENS grew slowly for its first four years, then exploded in 2021-2022 as crypto culture embraced .eth names as identity. Setting your Twitter name to your ENS domain became a social signal. Three-digit ENS names (000.eth through 999.eth) traded for thousands of dollars. Four-digit names became collectible. “ENS domains” became a speculative asset class of their own, with traders flipping names the way domain squatters flipped .com names in the 1990s.

The ENS token airdropped in November 2021, distributed to anyone who had registered an ENS name. Early registrants who had been using ENS since 2017 received substantial allocations — some worth over $100,000. The airdrop created the ENS DAO, which governed the protocol and managed a treasury worth hundreds of millions. Nick Johnson, ENS’s lead developer, became one of the most respected figures in Ethereum infrastructure.

ENS’s broader significance is that it proved onchain identity could be simple, useful, and valuable. A human-readable name attached to a wallet address seems trivial, but it transformed how people interact with Ethereum. ENS names appear in wallet UIs, block explorers, social platforms, and governance interfaces. They became the closest thing crypto has to a universal username. Whether ENS faces competition from alternative naming systems (Unstoppable Domains, .sol names on Solana) or becomes the permanent standard depends on network effects — and ENS has a substantial head start.


Trade memecoins safely on Memeshot — iOS / Android

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *