Bitcoin’s coinbase maturity rule constrains newly created reward outputs. It is a block-height condition, not a fixed number of hours.

What the source establishes

The Bitcoin developer guide describes the coinbase transaction as the special transaction through which a miner claims the block reward and fees. Its outputs have a maturity restriction: they cannot be spent until the required 100-block maturity condition is satisfied. This use of coinbase is a protocol term, unrelated to the exchange’s brand. Bitcoin developer guide — block chain and coinbase transactions ↗

The condition is expressed in blocks. Converting it into an exact wall-clock release time would add a timing guarantee that block production does not provide. The rule also differs from a wallet’s chosen confirmation requirement for an ordinary incoming payment. Bitcoin developer guide — block chain and coinbase transactions ↗

What the distinction changes

A mining dashboard can report a reward that is present on the chain while a spending transaction remains ineligible. A single balance label hides that distinction. An operational ledger is clearer when it tracks immature, mature and actually spendable outputs separately.

This is also a reminder that confirmation counts must be interpreted with the transaction type. A rule applicable to a newly created reward is not a universal hold on every transfer. Treating the two as interchangeable can produce incorrect funding and treasury expectations.

Questions for the next review

Inspect the output’s originating transaction and the applicable chain-height condition using the node or wallet’s maturity status. Keep any estimated release time labelled as an estimate. Reorganizations and wallet-specific display conventions need their own handling rather than an assumed countdown.