One more nice call today! We discussed our favorite tools from
@whitenoisechat @bitaxe_stx @FutureBit to
@Boltzhq
We also answered the following questions:
1. How is Script executed? Explain in terms of data elements, opcodes and the stack. What conditions cause immediate failure?
2. Why is Bitcoin Script intentionally not Turing-complete? What attacks does this prevent?
3. What role does scriptSig play vs scriptPubKey? How exactly are scriptSig and scriptPubKey combined and executed? (for legacy transactions)
4. Why are there limits on Script size, opcode count, and stack elements? What kinds of denial-of-service attacks do these limits prevent?
5. How could a ‘hash collision’ puzzle be created with script (unlocked by providing a hash collision)? What real hash collision bounty was claimed on the blockchain in 2017?
6. Walk through a standard P2PKH script step-by-step - what is happening at each opcode?
7. What is P2SH? What problems with ‘bare multisig’ was it supposed to solve when it was introduced?
8. Compare P2PKH vs P2WPKH vs P2TR from a Script perspective - what actually changes? How does signature verification differ (ECDSA vs Schnorr)?
9. What is the difference between legacy Script evaluation and SegWit evaluation? How is witness data treated differently during validation?
10. How does Taproot change the way scripts are revealed and executed? What is the difference between key-path and script-path spending?
See you next week, bitcoiners! Love to see this community so strong.