I used to be studying this gist and am unsure I’m understanding/studying the hex of the multisig’s redeem script accurately (line 14). It’s:
52410491bba2510912a5bd37da1fb5b1673010e43d2c6d812c514e91bfa9f2eb129e1c183329db55bd868e209aac2fbc02cb33d98fe74bf23f0c235d6126b1d8334f864104865c40293a680cb9c020e7b1e106d8c1916d3cef99aa431a56d253e69256dac09ef122b1a986818a7cb624532f062c1d1f8722084861c5c3291ccffef4ec687441048d2455d2403e08708fc1f556002f1b6cd83f992d085097f9974ab08a28838f07896fbab08f39495e15fa6fad6edbfb1e754e35fa1c7844c41f322a1863d4621353ae
So I see the three public key pairs, starting in daring textual content. I perceive that the final byte (0xae) is OP_CHECKMULTISIG. However I’m confused concerning the bytes (0x53, earlier than 0xae) and the 5241 firstly. I’m below the impression that earlier than the general public keys there must be two variables pushed onto the stack; one due to the checkmultisig bug and one other to establish the m of n required signatures to unlock the bitcoin. After which n ought to come proper earlier than the final opcode (3 on this case).
What am I not understanding accurately? What’s up with these fives and the 41 firstly? Thanks for the assistance!
Hyperlink to gist if damaged: https://gist.github.com/gavinandresen/3966071
