A 2024 halving and a token launch shared one block

Inherited archive entry · retained from the earlier edition. Its factual, legal and policy claims have not all been reverified for 19 September 2026. Research scope.

One scheduled event, one coincidental launch

Block 840,000, mined 20 April 2024 according to the block record, carried Bitcoin's fourth scheduled subsidy halving, cutting the coinbase reward from 6.25 to 3.125 bitcoin under the same every-210,000-block rule described in the developer reference. The block record also shows total fees of roughly 37.6 bitcoin paid across the block's 3,050 transactions, with a fee range running into several million satoshis per virtual byte, a level of contention distinct from the subsidy schedule itself. The Runes specification states plainly that 'the Runes protocol activates on block 840,000,' meaning a token protocol's own activation height was deliberately set to coincide with the halving rather than occurring because of it.

Two mechanisms, one block height

These are separate systems that happen to share a trigger height. The halving is a consensus rule embedded in every node's validation of the coinbase transaction; it required no software beyond what already shipped. Runes, by contrast, is a convention for encoding fungible-token data in an OP_RETURN output, described in the specification as beginning with OP_RETURN followed by a data-carrying opcode, whose contents are decoded into instructions for etching a new token or transferring existing balances. Choosing the halving height as the activation point was a coordination choice by the protocol's designers, not a technical requirement flowing from the subsidy schedule.

The boundary: elevated fees are a fee-market event, not a monetary one

The high transaction fees visible in the block record reflect competition for limited block space in a specific, closely watched block, under Bitcoin's existing fee-market rules; they are not a consequence of the subsidy falling, and the block record does not attribute the fee spike to any single cause. Conflating 'the halving' with 'a surge in transaction fees around the halving' treats a scheduled monetary event and a temporary congestion event as one fact when the record supports two separate ones, connected only by the coordinated timing the Runes documentation states directly.

Questions to carry forward

• Does a given account of block 840,000 distinguish the scheduled subsidy change from the coincidental fee spike, or present them as one event?
• What ongoing effect, if any, does Runes activity have on typical transaction fees outside coordinated launch events like this one?
• Who verifies that an indexer's reported rune balances match what the specification defines, given that Bitcoin's consensus layer does not interpret OP_RETURN contents itself?

Block 840,000 supports two distinct, well-documented facts, a scheduled halving and a coordinated protocol launch, and keeping them separate is more useful than treating the block as a single undifferentiated headline event.