How Mempool Congestion Creates Bonus Revenue for Miners

Why Mempool Congestion Matters to Miners

A Bitcoin block has a hard size ceiling — roughly 1 MB of base data plus witness data, which translates to between 3,000 and 7,000 transactions depending on what those transactions look like. Miners choose what to include, and they choose by fee rate, measured in satoshis per virtual byte (sat/vB). Whatever does not fit in this block waits in the mempool for the next one.

When inflow equals outflow, the mempool stays shallow and fee rates hover around 1-10 sat/vB. Block revenue in those stretches is almost entirely subsidy: fees are often just 1-5% of what a miner pulls in per block. That is the baseline. It is the world you are running hashrate in for most of a given year.

Congestion is when the inflow of new transactions outruns block space for hours, days, or weeks. Fee rates climb, sometimes to 100-400 sat/vB or higher, and the fee portion of block revenue balloons. In April 2024 — halving week plus the Runes launch — several blocks saw fees exceed the subsidy itself, the first time this happened persistently since the late-2017 bull run. For cloud mining users, this is where the math changes: the same rented TH/s that paid out a quiet amount in March was suddenly earning materially more per day in late April.

How the Mempool Works — One Paragraph

Users broadcast transactions with a fee-per-byte offer. Full nodes validate and hold those transactions in memory — the mempool, a sorted queue indexed by fee rate. Miners, including the pools that cloud platforms like NoxHash send hashrate to, pull transactions from the top of the queue and pack them into each ~1 MB block. When transaction submission rate outstrips the 1 MB every ~10 minutes throughput, users start outbidding each other for the limited block space. That bidding war is the congestion mechanism, and it is the single lever that converts network demand into fee revenue.

Historical Bonus Periods — What the Spikes Looked Like

Fees have never been a smooth line. They spike around specific events and then settle back toward baseline. The table below shows the major bonus periods since 2017, expressed as the fee share of miner revenue during the peak window of each event. These are public on-chain numbers — you can reproduce them from any block explorer or from the long-range fee history at Blockchain.com.

Two things stand out. First, the 2017 and 2024 peaks were both brief — a few days to a few weeks. Most of the calendar was baseline. Second, the 2023 Ordinals window was unusually long, because inscriptions produced a durable new source of block-space demand rather than a one-off event. When a bonus period lasts weeks instead of days, it shows up as a clearly elevated payout month on any FPPS cloud mining dashboard. You can always cross-check the current state of the queue visually at mempool.space before reading too much into any single daily payout.

Who Captures the Bonus — FPPS and Cloud Mining

Almost no cloud mining user mines solo. The hashrate you rent is pointed at a large mining pool, and the pool distributes earnings according to one of a few standard models. The one that matters here is FPPS (Full Pay Per Share), which is the model NoxHash uses.

The practical takeaway: on an FPPS pool, the fee bonus is not optional and not withheld. It is mechanically baked into every payout cycle. When you compare one month of rented hashrate against the next, a fat month usually maps back to something that happened in the mempool — a rally, a Runes drop, a market-wide unwind that pushed everyone to move BTC at once. Reading that relationship over a year or two is one of the most useful instincts a cloud mining user can build.

The Post-Halving Importance Shift

The subsidy halves roughly every four years. That schedule is hard-coded into Bitcoin and has played out four times so far.

The same fee environment — say, an average of 20 sat/vB — produces a steadily larger share of total revenue every time the subsidy halves. That is arithmetic, not speculation. You can see a clean long-run visualisation of the subsidy-versus-fees balance on Hashrate Index, which tracks the "fees as percent of miner revenue" series directly.

The strategic implication: as block rewards fall, the gap between a congested month and a quiet month widens in relative terms. Today, a 30% fee share feels like a meaningful bonus. In 2032, at the same absolute fee level, it would feel like a transformative payout. Cloud mining users who hold positions across multiple halvings will watch the fee component of their statements grow structurally over time — even without any single event behaving dramatically.

Can You Time Congestion? Honest Answer

In theory, renting hashrate right before a major fee event would be the move. In practice, you cannot time congestion with any reliability, and pretending otherwise is how cloud mining users end up overpaying for short contracts.

The rule of thumb most long-time miners live by: duration beats timing. A longer contract at a lower monthly rate is almost always a better bet than a shorter contract timed around a prediction. Congestion events happen on their own schedule; the only way to be guaranteed exposure to them is to already be running hashrate when they arrive. That is why the sibling piece on how to DCA into cloud mining contracts exists — dollar-cost averaging into duration is the closest thing to a free seat at the fee table.

Frequently Asked Questions