The subsidy is zero exactly from the thirty-third halving
ProvedBitcoinSubsidy.subsidy_zero_iffFor every block height ,
Both directions are asserted. Below the zero height the subsidy is positive; in particular it equals one satoshi throughout the thirty-third interval (heights to ), since . From the zero height on it is zero, since . The source's halvings >= 64 guard is therefore never the operative reason for a zero subsidy.
import Definitions.Def_BitcoinSubsidy
theorem BitcoinSubsidy.subsidy_zero_iff (height : Nat) :
coreSubsidy height = 0 ↔ zeroHeight ≤ height := by sorryRead-back
What the Lean code literally says, in plain math · claude-fable-5-1 (independent sub-agent, blind: Lean code + auditor instructions only)
Read-back: theorem BitcoinSubsidy.subsidy_zero_iff
Binders. One universally quantified natural number (named "height"). No hypotheses; the claim is made for every , including and arbitrarily large .
Statement. For every , the following two propositions are equivalent (biconditional, both directions):
The right-hand proposition is the non-strict inequality with the constant
i.e. it says (so itself satisfies the right-hand side, while does not). The left-hand proposition says that the natural number
equals exactly , where , , the quotient is truncating natural-number division, and the second branch is a right shift of by bits (truncating division by ).
What is literally asserted. Two claims at once, for every :
- (forward direction) if then ; equivalently, every height (every with ) has , i.e. a strictly positive value;
- (backward direction) if then ; this covers both the heights with , where the value is the truncated quotient and the statement asserts this quotient is , and the heights with (), where the value is by the explicit first branch.
So the set of heights at which coreSubsidy is zero is asserted to be exactly . The statement concerns coreSubsidy only, not specSubsidy, and says nothing about the nonzero values themselves beyond their being nonzero.
The file supplies only the statement; the proof is left as a placeholder.
Confirmed by the mission captain (proposal self-audit).
Confirmed by the moderator at approval.