Handshake
The Best and Pure Version of Handshake

Handshake.best

Preserving the pure, decentralized vision of Handshake V1. No central foundations. No forced reallocations. Just builders, holders, and miners aligning through skin in the game.

Join the Pure HNS Movement Signal Your Support On-Chain

Why Keep Handshake Pure?

Handshake was born to decentralize the root zone—no ICANN, no foundations, no gatekeepers. Every peer validates and owns the system.

The Risk: HIP-0019

Proposes reallocating ~874 million unclaimed HNS to a multisig-controlled "foundation."

  • ✕ Risks centralization
  • ✕ Contradicts permissionless ethos
  • ✕ Creates new power structures

The Solution: Pure HNS

Implement HIP-0018 (full on-chain DNS zone support) and rally grassroots efforts.

  • ✓ True decentralization: No trusted multisigs
  • ✓ Skin in the game: On-chain signals
  • ✓ Organic growth via community bounties

Pure HNS means: No inflation, no clawbacks, no new power structures. Just builders, holders, and miners aligning through skin in the game.

Join the Grassroots Rebuild

We're organizing as a real community effort. No leaders, just aligned builders.

On-Chain Signal Results

Community sentiment on HIP-0019 vs Pure HNS

Voting in Progress

Results TBD

Learn How to Signal On-Chain →
Join Discord View Proposals on GitHub

Support the Cause

Burn HNS to signal support – proceeds to community ideas:

hs1q...example...address

Frequently Asked Questions

Why oppose HIP-0019?
HIP-0019 proposes reallocating ~874 million unclaimed HNS to a multisig-controlled 'foundation.' We believe this risks centralization and contradicts the permissionless ethos of Handshake. We support organic growth, not forced reallocations.
What about the locked HNS?
The locked HNS consists of unclaimed airdrops. We believe it is safer to leave these coins locked or burn them rather than force a protocol change to seize them. Seizing user funds, even if inactive, sets a dangerous precedent.
How to get involved?
You can signal your support on-chain, join the community discussions on Discord/X, or contribute code to the ecosystem. We are building a grassroots movement of aligned builders.
Is this a fork?
No. We advocate for staying on the current Handshake consensus rules (V1) and improving the protocol through non-contentious updates like HIP-0018 (on-chain DNS zones). We oppose the contentious hard fork that HIP-0019 represents.