Bitcoin tokenomics

Promise and Scope

This editorial examines the documented issuance mechanisms of Bitcoin as defined in version-pinned code. The goal is to clarify the distinction between block subsidies, transaction fees, and theoretical supply limits without asserting future dates or current network states. We analyze the rules governing new unit creation and their mathematical constraints.

Established Facts: Subsidy versus Fees

Full nodes, software that checks blocks against consensus rules, validate those blocks independently. Proof of work links blocks through computational work. This description does not measure independence among node operators. A critical distinction exists between a block subsidy and transaction fees. The subsidy represents new units created by the protocol, while fees are existing units transferred from users to miners. This mechanism is described in developer guides but does not constitute a live measurement of mining concentration or usage patterns.

Units and MAX_MONEY Definition

Bitcoin Core v29.0 defines 1 BTC as 100,000,000 satoshis. A satoshi is the accounting unit used by the reviewed code, equal to 1/100,000,000 BTC. The code also sets a MAX_MONEY value of 21,000,000 BTC. MAX_MONEY serves as a consensus range check; it provides no measurement of actual total supply. No circulating or spendable supply has been measured in this review.

The Halving Mechanism and Integer Arithmetic

A halving reduces the allowed subsidy at an interval boundary; integer rounding applies to the amount. The GetBlockSubsidy function starts at 50 BTC and reduces the amount by right-shifting based on halving intervals. This rule uses integer satoshi arithmetic and is expressed in block heights rather than calendar dates.

At illustrative heights, the allowed subsidy decreases: 50 BTC at height 0, 25 BTC at 210,000, 3.125 BTC at 840,000, and 0.04882812 BTC at 2,100,000.

Each 210,000-block interval is called an epoch in this calculation. Epochs 0 through 32 allow positive subsidies, with epoch 32 permitting 1 satoshi per block. Epoch 33 begins at height 6,930,000 with zero subsidy. Due to integer rounding, the theoretical division of 50/1024 yields 0.048828125 BTC, but the code produces 0.04882812 BTC.

Interval Constraints and Theoretical Totals

Mainnet parameters set the subsidy halving interval to 210,000 blocks. Because this schedule is block-based, it does not establish an exact future calendar date for halvings. Native block subsidy issuance differs fundamentally from contractual releases of existing allocations; third-party wrapped assets or custodial arrangements are outside this scope.

Cryptosnif calculation bitcoin-subsidy-1 adds the allowed subsidy across 33 intervals, indexed k=0 through 32. The formula is the sum over those k values of 210,000 × floor(5,000,000,000 / 2^k) satoshis, where floor means rounding down to an integer. This results in a theoretical total allowance of 2,099,999,997,690,000 satoshis, or 20,999,999.97690000 BTC. This figure assumes every allowed subsidy is claimed, including the genesis subsidy, whose output is unspendable according to the reviewed mainnet source, and excludes transaction fees.

Unknowns and Operational Status

Current ownership concentration, privileged control powers, independently measured usage, incident remediation, and locally executable liquidity remain unverified. All operational criteria, including identity, supply, governance, and security, are marked as unknown pending independent scoped verification. The evidence coverage is insufficient to assign an overall score.

Consequences and Verdict

The theoretical allowance assumes the reviewed rules at every height and every allowed subsidy claimed, including the unspendable genesis output.

Current circulating supply requires separate observations, treatment of unclaimed rewards and a stated definition of circulation. Fees transfer existing units, so they do not add to subsidy issuance. A documented mechanism alone cannot establish current resilience or expected returns. The verdict remains unrated because the checks do not establish the project’s overall quality. Reproducible network observations, current control maps, and independent incident records would be required to evaluate the pending checks.