The Domain Name System is centralized by design. ICANN governs the root zone. Verisign operates .com. Registrars sit between you and your domain name, and any of them — along with courts, governments, or ICANN itself — can seize or suspend a domain. For most of DNS’s history, this was an accepted tradeoff: centralization enabled coordination, stability, and dispute resolution.
Then came blockchain, and a simple question: what if nobody controlled the root zone?
Namecoin: The First Attempt
The idea of blockchain-based naming predates Ethereum by years. Namecoin, launched in April 2011 as the first fork of Bitcoin, introduced the .bit namespace. It was a proof-of-concept: names stored on a blockchain, registered through proof-of-work mining, and resolved via specialized software.
Namecoin implemented a key-value store on its blockchain. Registering a name like d/example mapped to a .bit domain, and the registrant stored DNS-like records (IP addresses, TLS fingerprints) as JSON values. No registrar. No ICANN. No one to call when something went wrong.
The technical model was sound but adoption was negligible. .bit domains required custom resolvers or browser extensions. No major browser ever supported them natively. The namespace became a haven for a small group of privacy enthusiasts and not much else. But Namecoin proved the concept was viable, and its ideas influenced everything that followed.
Ethereum Name Service (ENS)
ENS is the most successful blockchain naming system to date, and it works fundamentally differently from Namecoin. Launched in 2017 on Ethereum, ENS uses smart contracts to manage .eth domain registrations.
How ENS Works
ENS has three core components:
- The Registry — a smart contract that maps domain names to their owners and resolvers
- Registrars — smart contracts that handle the registration process (currently using a commit-reveal scheme to prevent front-running)
- Resolvers — smart contracts that translate names to addresses (Ethereum addresses, content hashes, or traditional DNS records)
When you register example.eth, you’re interacting with the ETH Registrar Controller contract. The process requires two transactions: a commit (hashing your desired name with a secret) followed by a reveal (claiming the name). This two-step process prevents miners and MEV bots from seeing your desired name and front-running your registration.
ENS names are ERC-721 NFTs — they’re tokens on Ethereum, transferable and tradeable like any other NFT. Annual renewal fees (denominated in USD, paid in ETH) prevent unlimited namespace squatting, though premium names still trade for significant sums.
Beyond .eth
ENS expanded beyond .eth in a critical way: it now supports DNS namespace integration. If you own example.com in traditional DNS, you can claim example.com in ENS by setting a specific TXT record in your DNS zone. This bridges the two systems rather than forcing users to choose.
ENS also introduced CCIP-Read (ERC-3668), which enables off-chain name resolution. Instead of storing every record on Ethereum (expensive), resolvers can point to off-chain data sources and provide cryptographic proofs of authenticity. This dramatically reduces gas costs while maintaining trustlessness.
Handshake (HNS): Decentralizing the Root Zone
While ENS creates a parallel namespace, Handshake takes a more ambitious approach: replacing the DNS root zone itself.
Handshake is a proof-of-work blockchain that allocates top-level domains through auctions. Instead of ICANN deciding who gets to operate .com, anyone can bid on TLDs using HNS tokens. The Handshake root zone is an alternative to ICANN’s root zone — same concept, decentralized governance.
The Technical Architecture
Handshake’s blockchain stores only TLD ownership and DNS records for those TLDs. It doesn’t replace the entire DNS hierarchy — just the root. Once you own a Handshake TLD, you operate it like any other TLD, pointing to authoritative nameservers that handle second-level domains using traditional DNS software.
Resolution works through Handshake-aware resolvers. Projects like Fingertip and HDNS provide recursive resolvers that check the Handshake blockchain for TLDs before falling back to the ICANN root. Some implementations use browser extensions; others configure system-level DNS resolution.
The cleverness of Handshake’s design is that it reserved all existing ICANN TLDs. You can’t register .com on Handshake — it’s blacklisted. This means Handshake names only resolve for new TLDs that don’t conflict with the existing namespace, reducing collision risks.
Adoption Reality
Handshake has carved out a niche but hasn’t achieved mainstream adoption. Key challenges include the chicken-and-egg problem (no users because no resolution support; no resolution support because no users), the difficulty of getting ISPs to add Handshake resolvers, and competition from ICANN’s own new gTLD program.
Unstoppable Domains
Unstoppable Domains takes a different commercial approach to blockchain naming. The company sells domains on multiple blockchain networks (primarily Ethereum and Polygon) under extensions like .crypto, .wallet, .x, .dao, and .blockchain.
The key differentiator: no renewal fees. You pay once and own the domain permanently (or as permanently as the underlying blockchain exists). Unstoppable Domains stores records on Polygon (an Ethereum Layer 2), keeping gas costs low.
Unstoppable Domains has achieved more mainstream integration than most competitors. Their domains resolve in Brave browser natively, and they’ve partnered with several crypto wallets for human-readable payment addresses. But “mainstream” is relative — these domains still don’t resolve in Chrome, Firefox, or Safari without extensions.
IPNS and the Content-Addressed Web
The InterPlanetary Name System (IPNS) approaches naming from a different angle entirely. In IPFS (InterPlanetary File System), content is addressed by its hash — QmT78zSuBmuS4z925WZfrqQ1qHaJ56DQaTfyMUF7F8ff5o. IPNS provides mutable names that point to changing content.
An IPNS name is derived from a cryptographic key pair. The owner of the private key can update what content the name points to, while anyone can verify the authenticity of that pointer. It’s not a domain name system in the traditional sense — it’s a naming layer for content-addressed storage.
ENS and IPNS work together: an ENS name can have a contenthash record pointing to IPFS/IPNS content, giving you a human-readable name (example.eth) that resolves to decentralized content without any traditional web server.
DID:web and Decentralized Identifiers
Decentralized Identifiers (DIDs) represent a W3C standard that takes yet another approach to naming. The did:web method bridges decentralized identity with traditional DNS:
did:web:example.com
This DID resolves by fetching https://example.com/.well-known/did.json, which contains a DID Document with public keys, service endpoints, and authentication methods. It’s decentralized in its identity model but centralized in its resolution — relying on DNS and HTTPS.
Other DID methods (did:ion, did:ethr, did:key) resolve against blockchains or are self-certifying. The DID ecosystem is broader than domain naming, encompassing verifiable credentials and self-sovereign identity, but it intersects with DNS in important ways — especially as AI agents need machine-verifiable identities.
SpaceID, Bonfida, and Multi-Chain Naming
The naming landscape extends beyond Ethereum. Bonfida operates the .sol namespace on Solana, offering low-cost name registration with fast finality. SpaceID provides a multi-chain naming service with a universal SDK, operating .bnb names on BNB Chain and expanding to other networks through its Space ID 3.0 protocol.
These projects highlight a fragmentation problem: if every blockchain has its own naming system, interoperability becomes a nightmare. A user might own alice.eth on Ethereum, alice.sol on Solana, and alice.bnb on BNB Chain — three separate registrations, three separate resolution paths, zero coordination.
Efforts to solve this include cross-chain resolution protocols and aggregator services, but none has achieved dominance. The multi-chain naming landscape today resembles the early internet before DNS won — multiple incompatible systems competing for adoption.
Will Blockchain Domains Replace DNS?
Probably not. Here’s why:
Performance. DNS resolution takes 10-50 milliseconds. On-chain resolution on Ethereum takes seconds, requires RPC calls, and depends on node infrastructure. CCIP-Read and Layer 2 solutions improve this, but they add complexity and trust assumptions that undercut the “fully decentralized” promise.
Governance isn’t optional. DNS has dispute resolution mechanisms (UDRP), abuse policies, and accountability structures. Blockchain naming systems have none. When someone registers a trademark as a blockchain domain and uses it for phishing, there’s no mechanism for recourse. This isn’t a hypothetical — it happens regularly.
The browser problem. Until Chrome, Safari, and Firefox resolve blockchain names natively — without extensions — adoption will remain niche. Browser vendors have shown little interest in adding this support, partly due to the governance concerns above.
DNS already works. For 99.9% of use cases, traditional DNS is fast, reliable, and well-understood. Blockchain naming solves a problem that most users don’t have.
That said, blockchain naming has found genuine utility in specific niches: human-readable cryptocurrency addresses, censorship-resistant publishing, and decentralized application naming. These use cases won’t disappear. But coexistence with DNS is far more likely than replacement.
The most probable future: ENS and similar systems become identity layers for the crypto ecosystem, while DNS continues to serve the broader internet. Bridges like ENS’s DNS integration will let the two worlds interoperate when needed. Neither wins. Both persist.