THE BATTLE FOR BLOCKSPACE

This is a parody dashboard. Every unit on the battlefield is a real Bitcoin transaction, streamed live and classified in your browser. Click any unit — or any kill-feed row — for its txid, matched rule text, and a link to mempool.space. Nothing here is fabricated; only the framing is a joke.

What BIP-110 actually is

BIP-110 — "Reduced Data Temporary Softfork" is a real proposal (author: pseudonymous Dathon Ohm; original draft & advice credited to Luke-Jr). It is a temporary, one-year consensus soft fork with seven rules that invalidate the main arbitrary-data embedding tricks — inscription envelopes, oversized pushes, bare-multisig data stuffing, big OP_RETURNs, and more. Deployment is a modified BIP9 on bit 4 with a 55% threshold, mandatory signaling at blocks 961,632–963,647 (~Aug 7 2026 — blocks not signaling are rejected), max activation height 965,664 (~Sep 1 2026), then auto-expiry after 52,416 blocks. As of mid-2026 miner signaling sits near ~0.31% of hashrate.

"Yes, this proposal intentionally breaks user space, specifically the data storage user space." — BIP-110 text

"The previous limit allows for 340,282,366,920,938,463,463,374,607,431,768,211,456 scripts, which is obviously way more than anyone could ever need." — BIP-110 Rationale

"If no further action is taken by you, it will expire in a year." — BIP-110 text

"And no, it's too late to cancel BIP110." — Luke Dashjr

"Fork around and find out." — Jameson Lopp (opposition)

Read it yourself: bip-0110.mediawiki  ·  bip110.com  ·  knotslies.com  ·  Lopp's layman's guide

How we classify

• Rules applied flat. The fork is not active. We check all seven rules against every transaction and label the verdict "would violate BIP-110 if active." We do not apply the grandfathering exemption (pre-activation UTXOs), because there is no activation height to grandfather against yet.
• Full-block scans for headline numbers. On each new block we fetch the raw block and classify 100% of its transactions — no first-100 sampling bias. The scoreboard's violator counts, weight, and blockspace share come from these full scans.
• "Observed" is sampled. The live mempool percentage is drawn from the streamed transactions we happen to see, and is labeled "observed" — not a headline figure.
• Faces are cosmetic. We can't cheaply resolve which collection a unit belongs to, so each protocol maps to a faction pool and a random face is drawn. The emoji is flavor; the protocol, rule text, and txid are real.
• Block scans lack prevouts. Raw block transactions have no spent-output data, so BIP-110 rule 3 and per-transaction fees can't be evaluated there (marked "n/a"). Fees in the kill feed come from the mempool stream; block fee totals from block extras.

The art on the units

Unit faces are sample pieces from iconic collections (cosmetic only, not the actual inscription in the transaction):

• NodeMonkes — on-chain inscriptions (ordinals.com), nodemonkes.com
• Bitcoin Puppets — on-chain inscriptions (ordinals.com)
• Quantum Cats — Taproot Wizards; recursive on-chain inscriptions, previews rendered by Magic Eden (renderer.magiceden.dev), quantumcats.xyz
• Taproot Wizards — on-chain inscriptions (ordinals.com), taprootwizards.com
• Wizards of Ord — on-chain inscriptions (ordinals.com); 3,333 pixel wizards on block-78 sats, gallery.wizards.art / @TheWizardsOfOrd
• Bitcoin Frogs — on-chain inscriptions (ordinals.com)
• Ordinal Maxi Biz — art by ZK Shark, on-chain inscriptions (ordinals.com)
• Runestone — Leonidas; 112,383-wallet airdrop, March 2024; glyph render courtesy Ordinals Wallet
• Bitcoin Stamps — Stamps #0, #4, #5 by Mike In Space & Arwyn (2023), decoded from on-chain data via stampchain.io
• Rare Pepe — Counterparty cards (2016): RAREPEPE ("Nakamoto card"), PEPECASH, FEELSGOODMAN (Matt Furie); images via tokenscan.io, rarepepes.com

Collection indexes courtesy Ordinals Wallet (turbo API). All art belongs to its creators/holders; used here as tiny sprites in a non-commercial parody visualization.

Trench Chat

Trench Chat runs on Nostr (NIP-28) over public relays — no server, no accounts, burner keys minted in your browser. BIP-110 literally advises storing data on Nostr instead. We complied.

Channel: e7896af04cf2fcdea9b209f801547f1ff529c73eb24c760855889bcdda481aa5

The score

Synthesized live in your browser with the Web Audio API — no samples, no files. It tracks the battle: drums build with the spam wave, stingers land on real block events. Toggle with the ♪ button or press M.

Honest caveats

• Knots node share is disputed. Bitcoin Knots is often cited at ~20–25% of reachable nodes; opponents argue that figure is Sybil-inflated. Treat it as "~20–25%, disputed."
• "Spam" ≠ "noncompliant." Some culturally-"spam" traffic (small Runes) is fully BIP-110 compliant — those are our "infiltrators," strolling through legally. That gap is the whole joke.
• Data courtesy of mempool.space (and its public mirrors). This site is not affiliated with mempool.space.

Satire of a public policy debate among public figures. Playful, not defamatory. No filters were harmed in the making of this dashboard.