You're talking about Bitcoin soft forks wrong! ...at least, that’s what Bitcoin developer @reardencode says. “We need to be thinking about what *capabilities* different opcodes create” also: OP_CAT, MEV, and Bitcoin decentralization Notes: - Bitcoin is the first digitally scarce asset - OP_CAT enables five different capabilities - SegWit enabled non-third party malleable txs - Taproot enabled hidden script paths - CTV+CSS combo enables rebindable signatures - MEV concerns can probably be scoped and managed Timestamps: 00:00 Start 01:28 What is Bitcoin? 02:36 What's an OP code? 05:41 How to think about OP codes 07:39 Capabilities examples 10:17 Explaining OP codes 12:03 What do we want? 13:24 Why did SegWit NOT do more? 15:22 Taproot 18:50 Arch 19:25 Hidden script paths 22:13 CTV 31:55 OP_CAT 35:11 Check Contract Verify 36:33 Introduction of "state" & MEV 37:07 MEV 40:29 Limiting MEV 43:36 The problems of OP_CAT 48:26 The current consensus 52:22 Wrap up