How Many Bitcoins Are Mined a Day? Translate Blocks Into a Supply Budget
At Bitcoin’s usual ten-minute target pace, about 450 new BTC are mined in a 24-hour period during the current 3.125-BTC subsidy era. That is 144 expected blocks multiplied by 3.125 BTC each. It is a planning rate, not a promise that exactly 450 BTC appear on every calendar date. The more useful way to apply it is to distinguish a daily shorthand, a month-length estimate and the fixed block budget that governs an entire halving era.
One subsidy rule, several reporting units
Bitcoin issues the subsidy with accepted blocks, not with daily accounting runs. Bit.Fan’s explanation of the per-block daily-mining rule ties the daily estimate to block timing and the current block reward. The Bitcoin.org halving schedule lists 3.125 BTC per block after the April 2024 halving at height 840,000 and an average target of roughly ten minutes per block. Divide 24 hours by ten minutes and you get 144 target-paced blocks, hence 450 BTC.
Writing “450 BTC/day” is a unit conversion from a protocol rule and a target interval. The actual rule is 3.125 BTC of permitted new subsidy per block in this height range. A date with faster or slower block discoveries will contain a different number of blocks. No miner receives a special midnight payment to correct a day that happens to finish above or below the planning rate.
A month estimate must state its month length
A report that says “13,500 BTC per month” silently assumes a 30-day month at 450 BTC per day. For a 28-day February, the same rate gives 12,600 BTC; for 31 days, it gives 13,950 BTC. Those three values are hypothetical target-paced baselines, not observed chain totals. A reader comparing monthly figures should check whether the author used 28, 30 or 31 days before attributing the difference to miners or an issuance change.
The same care applies to annualization. At 450 BTC a day for 365 days, the arithmetic result is 164,250 BTC. A leap year would produce a different calendar multiplier, and a year that crosses the next subsidy halving cannot use 3.125 BTC for every block. The annualized figure is helpful for a rough scale comparison only when its assumptions are printed beside it.
Imagine a planning spreadsheet with “BTC created” as one row. Its formula can use expected blocks per day times the active subsidy times the number of days. Label the cell “target-paced estimate” and include the relevant block-height range. A separate row can later hold observed subsidy from the chain. Combining estimate and observation under one unlabeled number makes revisions look like contradictions when they are simply different methods.
The halving era has a block budget, not a calendar budget
The subsidy remains 3.125 BTC for 210,000 block heights from 840,000 through 1,049,999. If every block claims the full permitted subsidy, that range allows 210,000 multiplied by 3.125, or 656,250 BTC of new issuance. This is a block-count budget for the era. How many calendar days the era lasts depends on actual block timing, so multiplying a four-year guess by 450 BTC/day will not necessarily produce the same exact number.
At height 1,050,000, Bitcoin.org lists the next subsidy as 1.5625 BTC, with the calendar date estimated around 2028. The height is the rule boundary; the date is a projection. A month containing that boundary should divide its accepted blocks into the two subsidy ranges. Multiplying every block in such a month by the old 3.125 rate would overstate the scheduled issuance after the halving.
Reconcile an estimate with chain data
For an observed month, count accepted blocks in the reporting window and apply each block’s subsidy. The Bitcoin developer getblockstats reference describes a per-block subsidy field and a separate totalfee field, both measured in satoshis. Transaction fees are existing BTC paid by users, not extra newly minted supply. A combined block reward display is therefore the wrong column for a new-issuance sum.
A reporting window also needs a declared time zone and date boundary. An explorer’s block timestamps and chain selection may change an early, unsettled count; wait for an accepted history before calling a short window final. If a miner claims less than the full permitted subsidy, a simple block-count times rule calculation is an upper schedule estimate rather than the exact amount claimed. State which measurement you use.
Suppose a hypothetical 30-day period contains 4,280 accepted blocks, all within the current height era and claiming full subsidy. The chain-based schedule result is 4,280 times 3.125, or 13,375 BTC. That is 125 BTC below the 13,500-BTC target-paced month because there were 40 fewer blocks than the 4,320 target count. Nothing about the halving rule changed. This invented block count illustrates reconciliation, not a report on an actual month.
Use the daily figure for the right purpose
About 450 BTC per day is a convenient statement of present target-paced network creation. For calendar planning, multiply it by the correct number of days and warn when a halving may intervene. For a halving-era budget, use 210,000 block heights and the subsidy assigned to those heights. For history, inspect accepted blocks and fees separately. These are three ways to answer how many bitcoins are mined a day at different levels of precision, without pretending a daily estimate is a fixed protocol payout.

Comments
Post a Comment