Bitcoin Block Wars beta boss footage — Bitcoin activity turned into arcade encountersI’ve started publishing beta footage for the minibosses and in-field bosses currently being tested in
Bitcoin Block Wars.
Play here:
https://bitcoinblockwars.comBitcoin Block Wars is a browser arcade shooter built around a simple idea: Bitcoin activity should not just sit in a block explorer — it should become playable.
Blocks, fees, transactions, OP_RETURN-style data, dust-like fanout, UTXO consolidation, distribution patterns, and large value movement can all influence what the player sees inside the arena. The goal is not to simulate Bitcoin perfectly. The goal is to turn recognisable Bitcoin and mempool behaviour into readable arcade pressure.
How the Bitcoin triggers work, at a public levelThe game watches for recognisable Bitcoin/network patterns: new blocks, fast or slow block cadence, fee pressure, message-style transactions, dust-like fanout, mass distribution, UTXO consolidation, and large-value movement.
Those patterns do not directly spawn bosses the instant they appear.
They create encounter possibilities. The game still decides whether the current run can introduce that encounter fairly. That separation matters. Bitcoin provides the live texture, surprise, and theme. The arcade rules still protect readability, pacing, and player agency.
In other words: Bitcoin brings the chaos. The game decides when that chaos is allowed onto the screen.
I’m keeping the exact thresholds, scoring, and activation logic private. The notes below describe the Bitcoin pattern each boss listens for at a public level, not the full detection recipe.
Current beta boss footageBelow are the current beta videos for nine Bitcoin-linked minibosses and in-field bosses.
1. Dust Swarm — Bitcoin Dust Burst EncounterDust Swarm is based on dust-like transaction behaviour: tiny-value fanout, repeated small outputs, and transaction shapes that feel more like network grit than ordinary payment flow.
In-game, that becomes a contamination boss. The arena fills with drifting dust clouds, motes, brown-orange storm fronts, and dirty field-control pressure. The threat is not just one big enemy firing at you. It is the field itself becoming polluted.
Public trigger noteDust Swarm comes from the messy end of Bitcoin transaction activity: tiny-value fanout, repeated small outputs, and patterns that feel more like network grit than normal payment flow.
The arcade translation is contamination. What looks like dust on-chain becomes clouds, motes, dirty pressure zones, and a battlefield that slowly feels polluted.
Video link:
https://www.youtube.com/watch?v=WTFpeUuilZY2. Faucet Hydra — Mass Distribution EncounterFaucet Hydra is based on distribution-style transaction behaviour: value spraying outward to many recipients, like faucet payouts, batch sends, or exchange-style distribution.
In-game, that becomes a multi-headed distribution gunship. Split heads, branch lanes, manifold bursts, and cascade drops push pressure across several angles at once.
The boss is not meant to feel like generic bullet spam. The idea is distribution as attack grammar: one source, many outlets, many branches, many decisions.
Public trigger noteFaucet Hydra is tied to transactions that spread value outward across many recipients: faucet-like payouts, batch distribution, exchange-style sends, or similar many-output structures.
That becomes the boss’s whole personality. One source splits into many heads, many lanes, and many simultaneous decisions.
Video link:
https://www.youtube.com/watch?v=e2rRxRaPG1Y3. Fee Inferno — High-Fee Bitcoin EncounterFee Inferno is the fee market turned into a boss.
When fee pressure gets hot, the arena gets hot. The boss becomes a furnace-style threat: flame rails, ember fans, smoke, hot zones, meteor marks, and burning lane denial.
The design goal is to make fee pressure feel like expensive blockspace. You still have room to survive, but the safe routes become narrower, more contested, and more costly to misread.
Public trigger noteFee Inferno is driven by the feeling of hot blockspace: transactions paying up, fee pressure rising, and the mempool turning expensive.
In-game, that pressure becomes heat. Safe space gets narrower. Lanes burn. Smoke and flame turn the fee market into something you can physically dodge.
Video link:
https://www.youtube.com/watch?v=2YYogCrCwg04. Message Boss — OP_RETURN Signal EncounterMessage Boss is based on message-bearing Bitcoin transactions, especially OP_RETURN-style embedded data.
The encounter turns chain data into a signal fight. Instead of simply firing bullets, the boss feels like it is writing danger into the field: relay beams, glyph cages, broadcast pulses, line scars, and encoded pressure.
It should feel less like a generic beam turret and more like a hostile inscription engine broadcasting patterns into the arena.
Public trigger noteMessage Boss listens for Bitcoin activity with a data or message flavour, especially OP_RETURN-style signalling.
Instead of treating that as just metadata, the game turns it into hostile communication: relay beams, glyphs, broadcast pulses, and an arena that feels like it is being written over by the chain.
Video link:
https://www.youtube.com/watch?v=7gDW0DQ-ZEc5. New Block Miniboss — Bitcoin Block Mined EncounterNew Block Miniboss is a lightweight punctuation event for newly mined Bitcoin blocks.
A new block is a major rhythm point in Bitcoin, so the game can mark it with a compact miniboss encounter. It is not supposed to derail the whole run. It is more like a chain event marker: the network moved forward, the arena noticed, and the player gets a short readable fight.
Mine blocks. Fight blocks.
Public trigger noteNew Block Miniboss is the cleanest chain rhythm encounter: the Bitcoin chain advances, and the arena may answer.
It is not meant to hijack the run. It is a punctuation mark — a compact block-themed fight that says, “a new block landed; the game noticed.”
Video link:
https://www.youtube.com/watch?v=Q8934XVDcv06. Quick Succession Miniboss — Fast Block EncounterQuick Succession is based on unusually fast block cadence.
If Bitcoin blocks arrive faster than expected, the game can express that as a tempo spike: paired pressure, double targets, relay movement, and faster decision-making.
This is not a long mythic boss. It is a cadence punctuation mark. Fast blocks become fast trouble.
Public trigger noteQuick Succession is about tempo. When blocks arrive unusually quickly, the game can turn that faster chain rhythm into a short burst of arcade pressure.
The result is a twin miniboss encounter: fast, sharp, and built to feel like the chain suddenly picked up speed.
Video link:
https://www.youtube.com/watch?v=Fdwp0S5wZc87. Stuck Block Boss — Long Block Interval EncounterStuck Block is the opposite side of cadence: what happens when blocks take too long.
A long interval can feel like the chain is jammed, so the boss becomes a blockade. Corridor clamps, heavy sweeps, pressure fields, and structural denial make the screen feel stalled and compressed.
Every Bitcoin user understands the feeling: waiting for confirmation, watching the clock, and wondering when the next block will finally land. In-game, that tension becomes a boss that tries to lock down movement.
Public trigger noteStuck Block comes from the opposite feeling: waiting too long for the next block.
The boss turns that stalled-chain tension into arena pressure. Movement gets clamped, space feels blocked, and the fight carries the same mood as watching confirmations refuse to arrive.
Video link:
https://www.youtube.com/watch?v=BiA4_UTkfj48. UTXO Swarm Boss — Consolidation Transaction EncounterUTXO Swarm is based on consolidation-style transaction structure: many inputs being gathered and collapsed into fewer outputs.
That is a great arcade verb. Consolidation becomes gathering, dragging, compressing, reeling in, and throwing mass back at the player.
The boss uses tractor-like pressure, captured enemies, swarm packets, and thrown bodies to make consolidation feel physical.
Many inputs. Few outputs. One nasty boss.
Public trigger noteUTXO Swarm is built around consolidation: many inputs being gathered, compressed, and collapsed into fewer outputs.
That maps naturally into gameplay. The boss pulls things together, captures mass, compresses the field, and throws that pressure back at the player.
Video link:
https://www.youtube.com/watch?v=ae36LfTGwAc9. Whale Move Boss — Large Bitcoin Transfer EncounterWhale Move is based on large-value Bitcoin movement patterns.
A huge transfer should feel like something heavy crossed the chain, so this boss is built around capital-ship energy: broad passes, wake turbulence, lane pressure, large-body movement, and the sense that the player is dealing with something too big to ignore.
This is not a subtle encounter. It is the arena equivalent of seeing a giant transaction move across the network and thinking: someone just shifted serious weight.
Big coins. Bigger problems.
Public trigger noteWhale Move is tied to the feeling of serious value moving across Bitcoin.
The game treats that as weight. A large transfer becomes a capital-ship encounter: heavy passes, wake turbulence, broad pressure, and the sense that something massive just crossed the arena.
Video link:
https://www.youtube.com/watch?v=yQptiGYMd1IWhy build bosses this way?Most crypto games use crypto mainly as decoration: coins, wallets, NFTs, rewards, or leaderboards layered on top of a mostly unrelated game.
Bitcoin Block Wars is trying something different. The structure of Bitcoin activity becomes the structure of the fight.
Dust-like fanout becomes contamination and toxic field pressure.
Mass distribution becomes Faucet Hydra and many-headed output pressure.
High fee pressure becomes Fee Inferno and blockspace heat.
Message data becomes Message Boss and hostile signal patterns.
New blocks become compact block-themed miniboss punctuation.
Fast block cadence becomes Quick Succession and tempo pressure.
Long block cadence becomes Stuck Block and blockade pressure.
UTXO consolidation becomes UTXO Swarm and compression/tractor pressure.
Large value movement becomes Whale Move and capital-ship pressure.
The important design problem is readability.
Bitcoin data can be chaotic, but an arcade game still has to be fair. A player must be able to understand what is happening, dodge it, learn it, and improve.
That is why the chain data creates encounter possibilities rather than direct forced spawns. The blockchain influences the run, but it does not get to break the run.
Current beta goalsThis footage is still beta material, so I am especially interested in feedback on:
- whether the bosses read clearly at game speed
- whether the Bitcoin trigger idea makes sense from the footage
- whether each boss feels mechanically distinct
- whether the arena gets too visually dense
- how the fights feel on mobile
- whether the crypto/on-chain theme feels integrated rather than pasted on
- whether the public trigger explanations are understandable without exposing the exact tuning
Play / test the betaBitcoin Block Wars runs directly in the browser:
https://bitcoinblockwars.comNo install required.
Feedback is welcome, especially from people who understand Bitcoin transaction structure, mempool behaviour, arcade shooters, or all three.
