Burn 250,000 THE•HOPPENING once, keep 250,000 HOP in your wallet, and unlock premium Rune intelligence for life.
Lifetime access requires a verified 250k burn and a live 250k hold in the same wallet.
Burn 250k HOP and hold 250k HOP to unlock lifetime Rabbit Hole access.
Waiting for wallet connection...
OP_RETURN Runestone (edict / pointer to OP_RETURN output, or a
cenotaph) burns the runes per the Ordinals specification.
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.
OP_RETURN output (e.g. ord wallet runes burn or another indexer-verified burn builder). The Hop cannot broadcast this for you today.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.verified unless the on-chain rule matches.rune id 950638:795
name THE•HOPPENING
amount 250000
output: OP_RETURN (Runestone)
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.
Five premium tools unlock once your 250k burn is verified and your wallet still holds 250k. Locked previews show shape only.
Percentage of HOP rune supply burned via OP_RETURN / cenotaph assignments. Headline metric stays public; premium burn intelligence is gated.
Per-wallet conviction scoring. Public preview shows the call shape; full archetype + flags require unlocked access.
Rune risk detector. Public preview returns a risk band; full label + flags require unlocked access.
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.
Premium subscribers see the full ranked Rune radar with 24h volume, holder velocity, new-wallet inflow, and whale share. Locked view shows shape only.
| Rune | 24h volume | Holders | New wallets | Whale share | Status |
|---|
All the technical details, kept out of the way until you want them.
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.
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.
/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).
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.
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.