Non-binding coordination
Public Signals For The Open Root Measure support without pretending to control consensus.
Handshake needs a better way to see who is building, who is ready, who objects, and which proposals have real momentum. Signals can help, as long as they stay honest about their limits.
What Signals Can Show
Holder Conviction
HNS holders can publish signed support, objections, or delegated trust to community groups. Show both unique participants and HNS-weighted views.
Builder Position
Wallet maintainers, node developers, market operators, DNS services, and educators can explain what they support and what they can actually ship.
Operator Readiness
Node operators, resolvers, wallets, marketplaces, browsers, and hosting providers can publish whether they are testing, ready, opposed, or waiting.
Miner Intent
Miners and pools can signal which software they intend to run, but that signal should be displayed as readiness, not treated as final governance.
What Signals Cannot Do
- They cannot force a hard fork. Hard forks require users, nodes, miners, wallets, exchanges, services, and economic value to converge.
- They cannot prove one miner, one vote. Hashrate can move, split, lease, or hide behind pools.
- They cannot replace implementation review. A popular proposal can still be unsafe, underspecified, or too expensive to maintain.
- They cannot erase disagreement. A useful dashboard should show objections and uncertainty clearly.
A Better First Relaunch Event
Believer Badges
Let people opt into a portable, signed proof that they are still here and want Handshake to succeed.
HNS Rings
Organize around wallets, miners, resolvers, hosting, regions, education, domain ownership, and builders.
Readiness Dashboard
Show who is active, what is shipping, what is blocked, and which proposals need more work.
The Rule
Use signals to make coordination visible. Do not use them to claim authority that only the broader Handshake network can grant.