one minor correction: the video says you can't tell what opcodes are used in unspent scripts.

this is true. you *can* however tell what version of scripts bitcoin is locked up to.

so theoretically you could remove support for a version of script once all bitcoin locked up to that script version had been spent.

there are currently 3 versions of scripts in bitcoin; none of them have ever been deprecated and all of them currently have funds locked up to them. 

 Don't core devs test out new versions for a few months before releasing it to the public? 

 New versions are tested on Testnet, signets, or locally with regtest Bitcoin. But until it's live on mainnet it's effectively just like testing it on a completely separate fork 

 Well, the rule could take into account the block number the transaction was confirmed in. However, it still has many problems:

- the handling code cannot be removed
- if someone doesn't get their tx into the chain fast enough, they lose
- incentivizes miners to reorg

It could have some more, that's just what I came up with now. 

  https://i.nostr.build/QQRa.gif  

 Would you mind giving us an example of some things that this would work for? 

 You spark another thing than my LN wallet ! Lisa you are a bitcoin rockstar , take care of you. One day I'll take base58 courses.  

 Thanks for the detail! 

 https://video.nostr.build/62ff77e7778154b429f4192448198eb1e617c49d4b399adf79f8e4672ad26230.mp4#m=video%2Fmp4&dim=1280x720&blurhash=iBDls85F00%7DmD%25KHQ%3F%2529ZGZm-%23mELkV.8H%40S1%25f9v%250%251ELs%3AxHIUfks%3Bx%40kDMyV%40R%25bq%25fs%3BRQ%24*SfS1xtRjRQtRRRni&x=4dff01beaa34ebdee375e882174d264574b2fa3a99d13c96e548cb0d2341e75e