Definition
Block Reward is the total bitcoin a miner collects for producing a valid block. It is the sum of two parts: the block subsidy (newly issued bitcoin created by the protocol) plus all transaction fees paid by the transactions packed into that block.
Also known as: mining reward, block payout.
The block reward is the entire economic reason mining exists. It is what turns electricity and silicon into a financial incentive to keep the network honest, and it is the only mechanism by which new bitcoin enters circulation. Every other concept in mining — hashrate, difficulty, firmware tuning, power cost — ultimately resolves to one question: how much of the block reward does a given machine earn over time?
How the block reward is actually claimed
A miner does not simply “receive” the reward; it writes the reward to itself inside the block it builds. The first transaction in every block is a special coinbase transaction that has no normal inputs and pays out the subsidy plus the collected fees to an address the miner (or pool) controls. That coinbase transaction is the first leaf in the block’s merkle tree, so its contents are baked into the merkle root committed in the block header. When firmware reconstructs and hashes a candidate header — version + previous block hash + merkle root + ntime + nbits + nonce — it is, in effect, hashing a header that already promises the reward to a specific recipient. Find a hash at or below the network difficulty target and the block is valid; the embedded coinbase payout becomes spendable (after a 100-block maturity period). This is why proof-of-work and the reward are inseparable: the work is what authorizes the new issuance.
The subsidy, halvings, and the shift toward fees
The subsidy half of the reward follows a fixed, protocol-enforced schedule. It started at 50 BTC when Bitcoin launched in 2009 and is cut in half every 210,000 blocks — roughly every four years — in an event called the halving. After the April 2024 halving the subsidy stands at 3.125 BTC. This geometric decay is what caps total supply near 21 million coins and is why miner economics are not static: the newly issued portion of every payout shrinks on a schedule no operator can change.
As the subsidy falls, the fee portion of the block reward grows in relative importance. Fees are not fixed by the protocol; they emerge from a market where users bid for limited block space. In high-demand periods that competition can make fees a meaningful share of a block’s value, and over a long enough horizon fees are designed to become the dominant — eventually the sole — component of the reward once the subsidy approaches zero. For an operator, this means revenue modeling cannot assume the subsidy alone; the fee environment is a real variable.
Why the block reward shapes hardware decisions
For anyone running real machines, the block reward is the top line of the entire profitability equation. An S19, S21, or a desk-side Bitaxe earns a probabilistic slice of each block reward proportional to its share of total hashrate. Because the subsidy is fixed per block and difficulty rises as more hashrate competes, the bitcoin earned per terahash trends downward over time even when a machine’s output never changes. The reward sets what is on the table; difficulty determines how thinly it gets divided.
That dynamic is the structural pressure behind every efficiency decision in mining. Operators cannot raise the block reward, and they cannot lower difficulty — the only lever they fully control is joules per terahash. That is why lower-power chips, careful difficulty-aware profitability math, undervolting, and per-domain frequency tuning matter: each one stretches more of the shrinking per-terahash reward into actual margin. If you are weighing how different firmware stacks approach tuning and efficiency, our firmware comparison lays out the trade-offs.
Who decides where the reward goes
It is worth being precise about who controls the coinbase payout. When you mine through a traditional pool, the pool builds the block template and writes its own address into the coinbase transaction, then distributes earnings to participants under its payout scheme. When you mine solo — or through a template-sovereign arrangement where the miner constructs the block from its own node’s getblocktemplate — the miner dictates the coinbase and pays the full reward directly to itself, with the pool supplying only difficulty. That distinction sits at the heart of decentralization: the closer the operator is to building its own templates, the closer the block reward flows to the person doing the work rather than through an intermediary.
If you are sizing a build around current block-reward economics and a realistic difficulty outlook, our team plans deployments around real network conditions rather than optimistic assumptions — browse current-generation hardware in the D-Central shop to match the right machine to your power cost and reward expectations.
Related terms: Block Subsidy, Halving, Coinbase Transaction, Transaction Fees, Proof-of-Work.
In Simple Terms
The Bitcoin earned by mining a block. Currently 3.125 BTC, it halves roughly every four years.
Block Reward is the total bitcoin a miner collects for producing a valid block. It is the sum of two parts: the block subsidy (newly issued bitcoin created by the protocol) plus all transaction fees paid by the transactions packed into that block.
Also known as: mining reward, block payout.
The block reward is the entire economic reason mining exists. It is what turns electricity and silicon into a financial incentive to keep the network honest, and it is the only mechanism by which new bitcoin enters circulation. Every other concept in mining — hashrate, difficulty, firmware tuning, power cost — ultimately resolves to one question: how much of the block reward does a given machine earn over time?
How the block reward is actually claimed
A miner does not simply "receive" the reward; it writes the reward to itself inside the block it builds. The first transaction in every block is a special coinbase transaction that has no normal inputs and pays out the subsidy plus the collected fees to an address the miner (or pool) controls. That coinbase transaction is the first leaf in the block's merkle tree, so its contents are baked into the merkle root committed in the block header. When firmware reconstructs and hashes a candidate header — version + previous block hash + merkle root + ntime + nbits + nonce — it is, in effect, hashing a header that already promises the reward to a specific recipient. Find a hash at or below the network difficulty target and the block is valid; the embedded coinbase payout becomes spendable (after a 100-block maturity period). This is why proof-of-work and the reward are inseparable: the work is what authorizes the new issuance.
The subsidy, halvings, and the shift toward fees
The subsidy half of the reward follows a fixed, protocol-enforced schedule. It started at 50 BTC when Bitcoin launched in 2009 and is cut in half every 210,000 blocks — roughly every four years — in an event called the halving. After the April 2024 halving the subsidy stands at 3.125 BTC. This geometric decay is what caps total supply near 21 million coins and is why miner economics are not static: the newly issued portion of every payout shrinks on a schedule no operator can change.
As the subsidy falls, the fee portion of the block reward grows in relative importance. Fees are not fixed by the protocol; they emerge from a market where users bid for limited block space. In high-demand periods that competition can make fees a meaningful share of a block's value, and over a long enough horizon fees are designed to become the dominant — eventually the sole — component of the reward once the subsidy approaches zero. For an operator, this means revenue modeling cannot assume the subsidy alone; the fee environment is a real variable.
Why the block reward shapes hardware decisions
For anyone running real machines, the block reward is the top line of the entire profitability equation. An S19, S21, or a desk-side Bitaxe earns a probabilistic slice of each block reward proportional to its share of total hashrate. Because the subsidy is fixed per block and difficulty rises as more hashrate competes, the bitcoin earned per terahash trends downward over time even when a machine's output never changes. The reward sets what is on the table; difficulty determines how thinly it gets divided.
That dynamic is the structural pressure behind every efficiency decision in mining. Operators cannot raise the block reward, and they cannot lower difficulty — the only lever they fully control is joules per terahash. That is why lower-power chips, careful difficulty-aware profitability math, undervolting, and per-domain frequency tuning matter: each one stretches more of the shrinking per-terahash reward into actual margin. If you are weighing how different firmware stacks approach tuning and efficiency, our firmware comparison lays out the trade-offs.
Who decides where the reward goes
It is worth being precise about who controls the coinbase payout. When you mine through a traditional pool, the pool builds the block template and writes its own address into the coinbase transaction, then distributes earnings to participants under its payout scheme. When you mine solo — or through a template-sovereign arrangement where the miner constructs the block from its own node's getblocktemplate — the miner dictates the coinbase and pays the full reward directly to itself, with the pool supplying only difficulty. That distinction sits at the heart of decentralization: the closer the operator is to building its own templates, the closer the block reward flows to the person doing the work rather than through an intermediary.
If you are sizing a build around current block-reward economics and a realistic difficulty outlook, our team plans deployments around real network conditions rather than optimistic assumptions — browse current-generation hardware in the D-Central shop to match the right machine to your power cost and reward expectations.
Related terms: Block Subsidy, Halving, Coinbase Transaction, Transaction Fees, Proof-of-Work.