The Hop Terminal · Rabbit Hole access

Burn HOP. Hold HOP. Enter the Rabbit Hole.

Burn 250,000 THE•HOPPENING once, keep 250,000 HOP in your wallet, and unlock premium Rune intelligence for life.

Self-custody only · Xverse & UniSat · No tracking
Unlock flow

Three steps to the Rabbit Hole

Connect wallet to begin
1
Get 500k HOP
Buy 500,000 HOP on Bound, then withdraw to a self-custody Xverse or UniSat wallet. Custodial balances don't count.
Trade $HOP on Bound ↗
Pending
2
Burn 250k HOP
Send a Runestone OP_RETURN burn of 250,000 HOP, then paste the txid to verify on-chain.
Pending
3
Hold 250k HOP
Keep the remaining 250,000 HOP in the connected wallet. Drop below and access pauses — no second burn needed.
Pending
Access status

Your Rabbit Hole gate

Wallet: —
0
HOP detected

Lifetime access requires a verified 250k burn and a live 250k hold in the same wallet.

Burn receipt (250,000 HOP)
No burn receipt verified yet
Current hold (≥ 250,000 HOP)

Burn 250k HOP and hold 250k HOP to unlock lifetime Rabbit Hole access.

No burn submitted
Wallet detection & debug log
Waiting for wallet connection...

Manual burn + verify receipt

⚠ Do NOT send HOP to a normal Bitcoin address. A normal rune transfer is not a burn — the recipient can still spend the runes. Only an OP_RETURN Runestone (edict / pointer to OP_RETURN output, or a cenotaph) burns the runes per the Ordinals specification.
Wallet-assisted burn (PSBT)

If the operator has configured a burn-PSBT builder (env vars BURN_PSBT_API_URL + BURN_PSBT_API_KEY / ORDINALSBOT_API_KEY), the terminal will request a Runestone OP_RETURN burn PSBT for you and pass it to UniSat signPsbt / pushPsbt. Nothing is signed or broadcast without your explicit wallet confirmation.

PSBT builder idle
  1. Build the burn transaction using ord-compatible tooling that emits a Runestone with an OP_RETURN output (e.g. ord wallet runes burn or another indexer-verified burn builder). The Hop cannot broadcast this for you today.
  2. Burn exactly 250,000 THE•HOPPENING — Rune ID 950638:795 · Name THE•HOPPENING. The Runestone edict must direct 25,000,000 base units (display 250,000 at divisibility 2) to an OP_RETURN output / cenotaph.
  3. Broadcast from the same self-custody wallet you connect here. Copy the resulting 64-hex txid.
  4. Keep 250,000 HOP in this same wallet. The hold check reads the connected wallet's live balance.
  5. Paste the burn txid below and click Verify burn receipt. We never claim verified unless the on-chain rule matches.
Quick copy: rune id 950638:795 name THE•HOPPENING amount 250000 output: OP_RETURN (Runestone)
Verify burn receipt

Paste the txid of your OP_RETURN burn transaction. The verifier checks the on-chain Runestone via UniSat /v1/indexer/runes/event — it does not accept ordinary rune transfers. The optional HOP_BURN_TX_API override is honored if an operator wants to route around UniSat. New burns may return pending_indexer for a few blocks.

Behind the Rabbit Hole

Premium Rune intelligence

Five premium tools unlock once your 250k burn is verified and your wallet still holds 250k. Locked previews show shape only.

Locked

Hopium Meter

Per-wallet conviction score, archetype, and behavioral flags (rotation-chasing, cooling signals ignored).
Score 73 · Unwell · High conviction · Rotation-chasing
Burn 250k + hold 250k to see live wallet scoring.
Locked

Rune Radar

Whale-share movement, fresh wallet velocity, and exit-liquidity warnings across active Runes.
4 Runes · 2 Crowded · 1 Dead · whale moves last 24h
Full ranked table unlocks with verified access.
Locked

Burn Intelligence

Live burn % is public. Premium adds per-block burn velocity, burner cohorts, supply-tightening alerts.
Burn velocity ↑ 1.2%/wk · top 3 burner cohorts
Unlocks once your burn receipt is verified on-chain.
Locked

Whale Watch

Detector deep-flags, holder concentration drift, and early-mover alerts when whales rotate.
3 new whale entries · 1 exit-liquidity warning
Detector full output gated until access unlocks.
Locked

Bubble Map

Top-holder distribution for THE•HOPPENING with cluster heuristics, ranked share, and live deltas.
Top 50 holders · cluster heuristic · share %
Proof-gated. Submit verified burn + 250k hold.
Public scoreboard

Burn Monitor

Percentage of HOP rune supply burned via OP_RETURN / cenotaph assignments. Headline metric stays public; premium burn intelligence is gated.

--
Burn percent
--
Burned
--
Supply / total issued
Hopium Meter Preview

Per-wallet conviction scoring. Public preview shows the call shape; full archetype + flags require unlocked access.

Rune Detector Preview

Rune risk detector. Public preview returns a risk band; full label + flags require unlocked access.

Rune Bubble Map Locked

Top-holder distribution

Unlocks for wallets that burned 250k and still hold 250k. Locked callers see a redacted preview — no addresses, no amounts. Access is proof-based via ?address= and ?txid= (Cloudflare Pages has no session auth).

# Address Amount Share Cluster (heuristic)

Cluster links are heuristic only — UniSat does not return a transfer/funding graph, so groupings are by address-script kind and prefix, not by real on-chain linkage.

Rune Radar Preview

Premium subscribers see the full ranked Rune radar with 24h volume, holder velocity, new-wallet inflow, and whale share. Locked view shows shape only.

Rune24h volumeHoldersNew walletsWhale shareStatus
Meter: -- Radar: -- Detector: --
Safety & details

How this works under the hood

All the technical details, kept out of the way until you want them.

What counts as a real burn?
Only a Runestone OP_RETURN output (or cenotaph) that assigns THE•HOPPENING units to an unspendable script counts as a burn per the Ordinals spec. A normal rune transfer to a regular Bitcoin address is not a burn — the recipient can still spend those runes.
Why can't I just send HOP to a burn address?
Bitcoin has no concept of a true "burn address" for Runes. Sending HOP to any standard bc1... looking address leaves the runes spendable by whoever controls (or claims) that key. The only honest burn is an OP_RETURN Runestone edict — that's what the verifier checks.
How does verification work?
You paste the burn txid; the server calls UniSat /v1/indexer/runes/event and only returns verified when the on-chain event is a real OP_RETURN burn of ≥250,000 THE•HOPPENING. New burns may show pending_indexer for a few blocks. The only env var required is UNISAT_API_KEY (or HOP_RUNE_API_KEY).
Which wallets are supported?
Xverse and UniSat — desktop browser extensions or the in-app browsers on mobile. Regular mobile Safari/Chrome cannot inject the provider, so use the wallet's built-in browser there. Demo mode kicks in when no provider is detected — and demo never grants premium access.
What happens if I sell below 250k?
Access pauses automatically. The burn receipt stays valid forever — top your wallet back to 250k HOP and the gate reopens on the next refresh. No second burn is ever required.
What does The Hop store about me?
Nothing persistent. No localStorage, no sessionStorage, no analytics, no tracking. State lives in memory for the page session only. On refresh you re-connect the wallet and re-submit the txid if needed. The server holds an API key for UniSat — nothing else.
Can The Hop burn HOP for me automatically?
Only if the operator has configured the pluggable PSBT builder (BURN_PSBT_API_URL + BURN_PSBT_API_KEY / ORDINALSBOT_API_KEY). When configured, the terminal requests a Runestone OP_RETURN PSBT and hands it to your wallet to sign + broadcast — nothing happens without your explicit confirmation. Otherwise the manual flow above is the path.
Copied