The Week in Bitcoin: Launching Our Recurring Report Format
The first edition of a recurring, dated report: price and volatility context, the network's on-chain state, and one story from the news cycle read…
Every halving pushes the same open question further into view: can transaction fees alone eventually fund the security that keeps Bitcoin's chain honest? The claim is asked constantly. It is rarely examined this carefully.
Not provably yet, on current evidence. Fee revenue has been structurally too small and too volatile to replace the block subsidy today, and whether it grows enough over the coming decades depends on assumptions about future transaction demand and block-space value that cannot be verified in advance — which is exactly why this should be treated as an open question rather than a settled one in either direction.
Every halving cycle, the same question resurfaces, usually stated as a settled fact in one direction or the other: will Bitcoin’s transaction fees eventually replace the block subsidy as miner revenue, funding the security budget once issuance approaches zero? We think this deserves a properly first-principles look, because both the confident “yes, obviously” and the confident “no, this is a fatal flaw” camps are making claims the current evidence does not fully support.
Miners are paid two ways: the block subsidy (newly issued bitcoin, currently a fraction of what it was at launch and halving again roughly every four years) and transaction fees (paid by users for inclusion in a block). The subsidy is on a fixed, publicly known schedule converging toward zero over the coming century, with the overwhelming majority of it already issued well before then. As the subsidy shrinks, fees necessarily become a larger share of whatever miner revenue remains — the open question is whether that share becomes large enough, in absolute terms, to fund a security budget adequate to protect a network of Bitcoin’s value.
Looking at the actual history of miner revenue composition, transaction fees have typically made up a small share of total revenue — often in the low single digits as a percentage — with the block subsidy doing the overwhelming majority of the work. This share is not static, however: several episodes have seen it spike sharply. The 2017 congestion period, various 2021 demand surges, and the 2023–24 inscription-driven fee spikes all pushed the fee share into double digits, occasionally briefly exceeding the subsidy itself during the most acute moments.
The pattern across every one of these episodes is the same: a sharp rise, followed by reversion toward the prior low baseline once the specific driving demand (congestion, a particular on-chain activity fad) subsided. No episode observed so far has established a new, durable, higher floor for sustained fee revenue.
There are two structural forces at work, and they point different ways. On one side, layer-2 scaling — principally the Lightning Network — is explicitly designed to move routine, small-value payments off the base chain, settling many payments through occasional on-chain channel transactions instead. If Lightning succeeds at its stated purpose, it should reduce the number of routine payment transactions competing for base-layer block space, which works against fee growth even as the broader system succeeds on its own terms.
On the other side, base-layer demand is not limited to payments. Data-carrying transactions (inscriptions and similar use cases), large batched settlements from exchanges and layer-2 systems, and use cases that do not yet exist could all drive demand for scarce block space upward independent of anything resembling “more people making payments.” The 2023–24 fee spikes were driven substantially by exactly this kind of non-payment demand, which nobody had specifically forecast in advance.
This is not resolvable by argument alone — it requires data that does not yet exist, because the subsidy has never fallen anywhere near the level where this dynamic would be tested for real. The honest position is to track fee-share-of-total-miner-revenue at every halving as a genuine, ongoing data point, without treating any single reading — high or low — as proof of where the multi-decade trend ends up.
It is also worth separating two questions that often get merged: whether fee revenue rises enough in absolute dollar terms, and whether that’s enough security relative to what is actually needed to protect the network’s value at that future point. A smaller absolute security budget could be entirely adequate if the cost of attacking the network scales sensibly with what is being protected. We cannot resolve that jointly with the fee question, because both depend on the same unknowable future price and demand path.
Unproven, in either direction, on the evidence available today. This is one of the genuinely open long-run questions in Bitcoin’s design, and treating it as settled — in the “obviously fine” direction or the “fatal flaw” direction — is asserting more confidence than four halvings of historical data can support. We will keep tracking the fee-share figure at every future halving, and we will keep saying so if the picture stays unresolved.
For fees to replace the subsidy, either the fee rate per transaction must rise substantially, the volume of fee-paying transactions must rise substantially, or some combination of both — because total fee revenue is simply rate multiplied by demand for the fixed supply of block space available.
Historical data shows fee revenue is capable of large spikes under acute demand, but has not sustained a high baseline over any multi-year period observed so far — every spike has reverted once its specific driver passed, rather than establishing a new durable floor.
Higher-layer scaling, particularly the Lightning Network, is explicitly designed to move routine small payments off the base chain entirely, which — if it succeeds at its stated purpose — reduces rather than increases the base-layer transaction volume competing for block space, working against the fee-growth side of this equation even as it succeeds on its own terms.
Simultaneously, base-layer demand could rise for reasons unrelated to payments volume — inscriptions, layer-2 settlement batches, or future use cases not yet invented — any of which could push fee revenue up independent of "adoption" in the conventional sense.
This does not prove that the fee market will fail to fund security — it has not been tested under the conditions that will actually apply, since the subsidy has never yet fallen anywhere near zero, and forecasting three, four, or ten halvings ahead from a handful of historical data points carries very wide uncertainty either way.
It also does not prove that current security levels would necessarily be needed at that future point — if the value being secured (bitcoin's market capitalization, and the cost of an attack relative to it) also grows over the same period, a smaller required security budget in absolute terms could still be adequate. This analysis cannot resolve that jointly with the fee-revenue question, since both depend on the same unknowable future price and demand path.
What this analysis can responsibly conclude is only that the claim is unproven in either direction on current evidence, that it deserves being tracked as fee-share-of-revenue continues to be published every halving cycle, and that anyone stating with confidence that it definitely will or definitely will not work out is asserting more certainty than the data supports.
Historically low, typically low-single-digits on average, with sharp temporary spikes during periods of high demand for block space that have not persisted once the specific demand driver subsided.
Potentially, for base-layer fee revenue specifically — Lightning is designed to move routine payments off-chain, which could reduce competition for base-layer block space even as it succeeds at its own goal of cheaper, faster payments.
This analysis does not support that conclusion any more than it supports confident optimism. It is a genuinely open question that will not be resolved by argument, only by data that does not yet exist. Not financial advice either way.
The first edition of a recurring, dated report: price and volatility context, the network's on-chain state, and one story from the news cycle read…
This section carries analysis from outside the desk — always labelled clearly, always disclosed, always held to the same First-Principles Take…
Round numbers generate coverage in proportion to their digits rather than their significance. A threshold is a base-ten artefact, not a property of…
The week’s Bitcoin news, one reasoned take, and the on-chain number that mattered. Free, weekly.
Signal, not noise. Unsubscribe any time.