Sequence locks are verified exactly from CSV activation
ProvedBitcoinActivation.lockTimeFlags_eqFor every height , lockTimeFlags is LOCKTIME_VERIFY_SEQUENCE when and otherwise: BIP68 relative locks are enforced from the CSV activation height on.
import Definitions.Def_BitcoinActivation
theorem BitcoinActivation.lockTimeFlags_eq (height : Nat) :
BitcoinActivation.lockTimeFlags height =
if 419328 ≤ height then BitcoinActivation.LOCKTIME_VERIFY_SEQUENCE else 0 := 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: BitcoinActivation.lockTimeFlags_eq
Binders. Universally quantified over one natural number ("height"), with no hypotheses: every , including , is covered.
Conclusion. An equality of natural numbers:
The right-hand side is a case split on the decidable proposition (non-strict, so falls in the first branch), written with the numeral directly rather than through any named height. The constant is, by its definition, the natural number ; so the right-hand side is when and otherwise.
Unfolding the left-hand side. By definition,
where is the Boolean truth value of , and . The left side's branch condition is thus a Boolean (the activation test for the label used as a condition), while the right side's branch condition is the proposition written out numerically.
What the statement asserts, concretely. For every natural , the number produced by (which is always or ) coincides with the number given by the explicit case split at the threshold . It is an equality of natural numbers, not a logical equivalence, and it mentions no other deployment label and no record of script flags.
Confirmed by the mission captain (proposal self-audit).
Confirmed by the moderator at approval.