The P2PKH bytes parse to the interpreter's P2PKH script
ProvedBitcoinSig.parseScript_p2pkhFor every 20-byte : parseScript (p2pkhBytes h) = some (p2pkhScript h) — the byte-level GetScriptOp parse of 76 a9 14 <h> 88 ac is the instruction list the Script mission's theorems are stated on.
import Definitions.Def_BitcoinSig import Definitions.Def_BitcoinScript open BitcoinSig BitcoinSer
theorem BitcoinSig.parseScript_p2pkh (h : Bytes) (hh : h.length = 20) :
BitcoinSig.parseScript (BitcoinSig.p2pkhBytes h) = some (BitcoinScript.p2pkhScript h) := 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: BitcoinSig.parseScript_p2pkh
Binders and hypothesis. Universally quantified over a byte string , with one hypothesis : .
Conclusion.
Unfolding the left side. p2pkhBytes is . Since , pushBytes is the single length byte 0x14 followed by the 20 bytes of ; so the whole string is the 25 bytes . parseScript runs the instruction parser with fuel equal to the length (25) and returns "none" if any push runs past the end of the data, else "some" of the instruction list. getOp on each prefix: 0x76 exceeds 0x4e so it is the opcode instruction with byte 0x76; likewise 0xa9; 0x14 0x4c so it is a direct push of the next 20 bytes, which are exactly (there are 22 bytes remaining, so the push does not run short); then 0x88 and 0xac are opcode instructions; the empty remainder parses to the empty list. The result is "some" of
Unfolding the right side. p2pkhScript (from the script file) is the instruction list , where the opcode constants are the bytes 0x76, 0xa9, 0x88, 0xac respectively. So the two sides are the same list wrapped in "some".
What is not said. The statement does not say anything for : in particular it does not assert the (by the definitions also true) parse for other lengths below 76, nor for lengths that would use OP_PUSHDATA1/2/4 encodings. It does not say that p2pkhBytes is the only byte string parsing to p2pkhScript (a non-canonical push such as 0x4c 0x14 followed by would parse to the same instruction list). It does not say anything about executing the script, about findAndDelete, about serScriptCode, or about the oracle. It does not say that is a hash of anything. It does not involve any flags, transaction, or signature.
Confirmed by the mission captain (proposal self-audit).
Confirmed by the moderator at approval.