{"type":"rich","version":"1.0","title":"David A. Harding [ARCHIVE] wrote","author_name":"David A. Harding [ARCHIVE] (npub16d…x4wrd)","author_url":"https://yabu.me/npub16dt55fpq3a8r6zpphd9xngxr46zzqs75gna9cj5vf8pknyv2d7equx4wrd","provider_name":"njump","provider_url":"https://yabu.me","html":"📅 Original date posted:2021-09-05\n📝 Original message:On Fri, Sep 03, 2021 at 08:32:19PM -0700, Jeremy via bitcoin-dev wrote:\n\u003e Hi Bitcoin Devs,\n\u003e \n\u003e I recently noticed a flaw in the Sequence lock implementation with respect\n\u003e to upgradability. It might be the case that this is protected against by\n\u003e some transaction level policy (didn't see any in policy.cpp, but if not,\n\u003e I've put up a blogpost explaining the defect and patching it\n\u003e https://rubin.io/bitcoin/2021/09/03/upgradable-nops-flaw/\n\nIsn't this why BIP68 requires using tx.version=2?  Wouldn't we just\ndeploy any new nSequence rules with tx.version\u003e2?\n\n-Dave\n-------------- next part --------------\nA non-text attachment was scrubbed...\nName: signature.asc\nType: application/pgp-signature\nSize: 833 bytes\nDesc: not available\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20210905/2f55d419/attachment.sig\u003e"}