Overview
Handshake is a blockchain that breaks ICANN's monopoly on domain names. Instead of applying to a central authority, you buy .hns domains through transparent auctions. The network runs proof-of-work consensus (like Bitcoin) and manages domain registrations on-chain. It launched in February 2020 and now serves as a genuine, working alternative to the Domain Name System that runs the web.
History and founding
Joseph Poon and Andrew Lee built Handshake to fix a core internet problem: one organization controls which domains exist. Poon had already changed finance twice (Lightning Network, Plasma), so he attacked DNS next. Lee brought real-world payments experience from Purse.io. They hired Christopher Jeffery (who built Bcoin) and assembled a team that knew how to ship production systems.
In August 2018, they raised $10.2 million from real venture firms: Andreessen Horowitz, Polychain Capital, Founders Fund. Then they did something unusual. They donated the entire $10.2 million to free and open-source software. The Apache Software Foundation, Tor Project, and Wikipedia all received grants. By January 2020, they'd distributed money to over 30 open-source projects. This wasn't marketing. The team actually believed decentralized infrastructure matters.
The network went live February 3, 2020. The genesis block distributed HNS tokens to FOSS projects and community members. No pre-mine for insiders. No secret allocations. Just a protocol that worked and a set of domains ready to be auctioned.
Technical architecture
How consensus works
Handshake uses proof-of-work mining with the Blake2B hashing algorithm. A new block arrives roughly every 10 minutes (same timing as Bitcoin). Miners get 2,000 HNS per block they produce. The network adjusts difficulty automatically based on hash rate to keep that 10-minute target.
The 10-minute interval means existing Bitcoin mining infrastructure can point at Handshake without retooling. That's deliberate. Bitcoin miners already own the hardware and power generation. Making it easy for them to mine Handshake strengthens the network.
The UTXO model
Handshake doesn't track accounts. It uses Bitcoin's model: unspent transaction outputs. When you own HNS, you own a specific "coin" (really a UTXO). To spend it, you prove you hold the private key. This architecture is simpler and more auditable than account-based designs.
The protocol adds covenants—constraints on what a transaction output can do when spent. Covenants make complex auction logic possible without needing a full virtual machine. They execute during validation. The result is deterministic, proven behavior.
Domain auctions
Handshake auctions use the Vickrey format: sealed-bid, second-price. You submit an encrypted bid. Other people submit encrypted bids. After 80 hours, everyone reveals. The highest bidder wins at the price of the second-highest bid. This stops people from overbidding just to own a domain.
Once you win, the domain is yours on-chain. To keep it, you publish a renewal transaction to the blockchain roughly once per year. Miss the deadline and it expires. This mechanic ensures domains actually circulate instead of being hoarded forever.
Finality
New blocks on Handshake arrive every 10 minutes. Real finality? You need deep confirmations. After 100+ blocks (16+ hours of mining), the cost to reorganize the chain exceeds what anyone would spend. That's probabilistic finality. Domain operators typically wait about 2 days before assuming a transaction is settled.
Network topology
Handshake is peer-to-peer with no central authority. Every full node stores the entire blockchain and validates all transactions. Light clients can verify specific transactions using SPV, letting smartphones participate without storing everything.
Ecosystem and adoption
Registrars and wallets
Namebase is the main registrar. It lets you search domains, bid on auctions, host DNS, and hold HNS in a web wallet. Bob Wallet is a desktop app that prioritizes privacy and self-custody—you keep your keys, Namebase doesn't touch them. More registrars and wallet providers keep launching. Users get to pick.
What people actually use Handshake for
Early adoption was speculative. People bought three-letter domains hoping to flip them. But real use emerged. Communities registered .hns domains for censorship-resistant services. Activists registered domains that governments couldn't seize. Developers built infrastructure on top. Privacy advocates liked that Handshake domains are hard to take down.
Enterprises came later. Some evaluated Handshake for brand protection. Others saw it as a hedge against ICANN decisions. It's not mainstream, but it works for people who care about control.
Connecting to regular DNS
Your browser doesn't know about .hns domains. It defaults to ICANN's root servers. To reach .hns domains, you need a resolver that queries the Handshake blockchain instead. HNSD and hsd are reference implementations. Browser extensions exist. Some DNS providers are adding Handshake lookups, slowly bridging the two systems.
Why this matters for anti-ICANN sentiment
ICANN makes decisions behind closed doors. Domain allocation is opaque. Handshake flips that. Auctions are transparent. Bids are public. No insider deals. That appeals to people who distrust centralized authority, especially as more organizations notice ICANN's power.
Exchanges, wallets and infrastructure
Where to trade HNS
Binance, Kraken, Coinbase, Gate.io all list HNS. Binance has the most liquidity. Average daily volume is $5-10 million across all venues. That's thin by major token standards. Large buys move the price noticeably. OTC desks accommodate institutional trades that don't fit normal order books.
Custody options
Namebase Wallet handles HNS and domain management in one interface. Bob Wallet prioritizes self-custody and works with Ledger and Trezor hardware wallets. Command-line tools and libraries exist for developers who want to automate everything. Each option trades off convenience versus control.
Developer tools
The Handshake Developer Collective publishes documentation, example code, and SDKs. JavaScript (hsd.js), Python, and other languages are supported. Resolver software, mining pool software, and block explorers all exist. The infrastructure matured past "hobby project" years ago.
Tokenomics
Fixed supply
Maximum supply is 2.04 billion HNS tokens. That cap is absolute. Mining will stop around 2140. Current circulation is 679.56 million (33% of max). New tokens enter circulation at roughly 500,000 HNS per day (250 blocks times 2,000 HNS per block).
The initial distribution allocated tokens to FOSS projects (31.5%), developers (15%), open-source founders (10%), and other stakeholders. The emphasis on public goods reflected the team's actual values, not performative ESG.
Halving schedule
Mining rewards drop by half every 170,000 blocks (roughly 32-33 months). The first halving happened in September 2021. The next in May 2023. The schedule is predictable. Miners can model long-term economics and decide whether to stay mining.
Eventually (2140), mining rewards vanish. Transaction fees become the only security budget. Bitcoin faces the same problem. The long-term economics are unsettled for both networks.
Why people want HNS
Domain bidding creates real demand. You need HNS to participate in auctions. Renewals require spending HNS. Speculative hodlers think domain demand will grow. These factors create multiple sinks for tokens. Whether they sustain price is an open question that depends entirely on whether domain auctions actually matter to people.
Governance
Proof-of-work decides
Handshake uses Bitcoin-style governance. Miners validate or reject code changes. Protocol upgrades need miner consensus. No token voting. No committees. No proposals floating in Discord. Mining hardware determines direction. It's not democratic, but it's transparent.
Community discussions
The Handshake Development Collective is loosely organized. Core contributors propose ideas on GitHub. Community members review and debate. Reddit (/r/handshake) and Discord servers host non-technical discussions. This is organic, not structured.
Foundation role
The Handshake Foundation exists. It funds development, hosts conferences, publishes docs. But it explicitly doesn't make unilateral decisions. The Foundation respects the protocol's decentralized nature. That constraint is genuine.
Regulatory status
Naming and the law
Domain name regulation is sparse. Most countries don't explicitly regulate them. ICANN policy enforcement depends on pressure, not law. Handshake operates in that gray space. No central choke point means regulators can't easily force compliance.
But this changes. Jurisdictions are watching decentralized naming. IP holders complain about squatted domains. Governments worry about abuse. Regulatory attention will intensify.
Is HNS a commodity?
US regulators classify HNS as a commodity, not a security. That avoids securities compliance. But it offers less investor protection. Tax authorities treat HNS mining and trading as taxable events. You track cost basis and report gains. Same as any crypto.
Compliance at the exchange level
Binance, Kraken, Coinbase—they all run KYC and AML on HNS trading. Domain registrars face pressure to verify identity and prevent malicious registrations. These requirements clash with Handshake's permissionless design. Some registrars implement filters. Others stay neutral. Tension persists.
Controversies
Trademark squatting
When Handshake launched, people registered domains matching major brand names. Coca-Cola couldn't sue away a .hns domain the way it can in traditional DNS. Trademark holders complained. Blockchain immutability is a feature when you want censorship resistance. It's a bug when you hold a trademark.
Registrars responded by filtering known infringing domains at the DNS level. This preserves blockchain immutability while preventing browser access. It's a compromise. Neither side is happy.
Governance and wealth concentration
Early critics noted that large allocations to Foundation insiders gave certain people outsized influence. Others argued proof-of-work governance favors whoever has capital for mining hardware. Both observations are valid. Handshake didn't solve these problems. It just moved them to a different system.
Adoption is slow
Six years after launch, Handshake adoption is nowhere near early projections. Domain registrations spiked during speculation bubbles, then stabilized low. Resolver requirements and DNS integration complexity keep most users away. The value proposition hasn't convinced enough people yet.
Recent developments
2024-2025 ecosystem growth brought mobile wallets in development and smoother UX. Bob Wallet improved. Namebase added features. Resolver integrations with traditional DNS providers expanded.
Technical enhancements focused on auction mechanics and covenant capabilities. Research into UTXO-based smart contracts continued. No major soft-fork consensus yet on expanding programmability.
Real-world asset projects and financial institutions started exploring Handshake for digital asset naming and identity systems. These are early conversations. Nothing shipped.
FAQ
How do I acquire a .hns domain?
Bid in Handshake auctions through Namebase or Bob Wallet. Auctions are blind. You encrypt your bid, wait, then reveal. The highest bidder wins at the second-highest price.
Is Handshake a cryptocurrency or a DNS system?
Both. HNS tokens create economic incentives. The blockchain is an immutable DNS root. They're interdependent. You need HNS to bid. Domain demand drives token adoption.
Can I access .hns domains with my regular browser?
No. Your browser defaults to ICANN's servers. You need a specialized resolver application (HNSD, hsd), a browser extension, or DNS configuration pointing at Handshake. Registrars are working on bridges, but we're not there yet.
What prevents someone from squatting on my company's domain name?
At the protocol level, nothing. ICANN policies and trademark law don't exist here. Registrars can implement filtering and brand protection. Trademark holders can sue offline. The best defense is registering proactively.
How is Handshake different from DNS?
Handshake is decentralized. No single point of failure. No ICANN governance. But it requires specialized software. Adoption is tiny. Traditional DNS integrates seamlessly and everyone uses it. You trade convenience for control.
Who controls the .hns root zone?
Nobody. Thousands of independent validators running full nodes collectively maintain the authoritative copy. Proof of Work secures consensus. No trusted central authority needed.
Can I renew a .hns domain indefinitely?
Yes. You pay once at auction. Then publish a renewal transaction roughly every year. You can renew forever as long as you hold the private key and have blockchain access.
Related articles
- Cryptocurrency Naming Systems and Decentralized DNS Protocols
- Proof-of-Work Consensus Mechanisms and Security Models
- UTXO Versus Account-Based Blockchain Architectures
- Vickrey Auction Mechanisms in Decentralized Platforms
- ICANN, DNS Governance, and Alternative Naming Infrastructure
- Cryptocurrency Transaction Finality and Probabilistic Security