Handshake

How the On-Chain Vote Works Signal with Skin in the Game for Pure Handshake

No centralized polls, no loud voices without stake. Use the Handshake blockchain itself to show real holder commitment. Your HNS amount burned or sent demonstrates conviction—higher commitment = stronger signal.

Wallet
Send TX
Burn + OP_RETURN
Explorer Verify
Tally
Send Your Signal Now

Why On-Chain Signaling?

Traditional polls favor noise from zero-stake accounts. On-chain signals filter for real alignment:

  • Economic cost: Transaction fees + burn amount weeds out spam.
  • Weighted by Stake: HNS committed shows true skin in the game.
  • Immutable & Public: Anyone can verify on explorers like shakeshift.com.

Current Status

The community is currently signaling. Results are being tallied live on-chain.

Voting Window: March 7 – March 21, 2026

Step-by-Step: How to Signal

1 Prepare Your Vote

Vote Options

  • Support Pure HNS (Oppose HIP-0019) NO
  • Support HIP-0019 Reallocation YES
  • Abstain ABSTAIN

Data String Format: HIP0019:[VOTE] (e.g., HIP0019:NO)

Choose Your Commitment

Amount: 0.1 – 1000+ HNS. This is your "skin in the game". Higher amount = more weight in the tally.

Burn Address (Provably Unspendable)

hs1qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq

2 Choose Your Method

Method A: Bob Wallet

  1. Open Bob Wallet (ensure synced).
  2. Go to Send.
  3. Paste the Burn Address.
  4. Enter your HNS Amount.
  5. Crucial: Add the data string (e.g., HIP0019:NO) in the Memo/Data field if available, or use the CLI console.

Note: Standard UI might not support raw OP_RETURN strings easily. Use the Script method for precision.

Recommended

Method B: Simple JS Script

Connects to Bob's local node. No seed exposure.

const { WalletClient } = require('hs-client');

const walletClient = new WalletClient({ 
  network: 'main', 
  port: 12037 // Bob default 
});

async function sendSignal(vote, amountHNS) {
  const id = 'default'; // Your wallet ID
  const dataHex = Buffer.from(
    `HIP0019:${vote.toUpperCase()}`, 
    'utf8'
  ).toString('hex');
  
  const amountSat = Math.floor(amountHNS * 1e6);

  const outputs = [
    { 
      address: 'hs1qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq', 
      value: amountSat 
    },
    { 
      script: `OP_RETURN ${dataHex}`, 
      value: 0 
    }
  ];

  const tx = await walletClient.send(id, { outputs });
  console.log('TXID:', tx.hash);
  console.log('View: https://shakeshift.com/tx/' + tx.hash);
}

// Edit & run:
sendSignal('NO', 5.0); // Example: NO vote with 5 HNS

1. Install Node.js
2. Save as signal.js
3. Run node signal.js

Verify Your Vote

Once sent, copy your TXID.

  1. Go to shakeshift.com
  2. Search for your TXID.
  3. Look for the OP_RETURN output (hex decodes to your string) and the burn amount.

Rules & Transparency

  • Window: March 7 – March 21, 2026.
  • Weight: Total HNS sent to burn address with matching OP_RETURN.
  • No Spam: Tally unique addresses or cap per addr if community agrees.
  • Results: Public script will be released for anyone to audit the tally.

FAQ

Is this binding?

No—it's sentiment signaling to guide consensus and show where the real economic weight stands.

Is it secure?

Yes. The script runs locally via your own Bob wallet node. It never asks for your seed phrase.

What if I mess up the string?

If the string is not exactly `HIP0019:YES` or `HIP0019:NO` (case sensitive), it may not be counted by the automated tally script.