{"type":"rich","version":"1.0","title":"Jeremy [ARCHIVE] wrote","author_name":"Jeremy [ARCHIVE] (npub1q8…8qwta)","author_url":"https://yabu.me/npub1q86n5vtxkwerzwfqza3hwls8pl8764244464talfqy2vpj0qaz6q38qwta","provider_name":"njump","provider_url":"https://yabu.me","html":"📅 Original date posted:2021-09-05\n📝 Original message:In working on resolving this issue, one issue that has come up is what\nsequence values get used by wallet implementations?\n\nE.g., in Bitcoin Core a script test says\n\nBIP125_SEQUENCE_NUMBER = 0xfffffffd  # Sequence number that is rbf-opt-in\n(BIP 125) and csv-opt-out (BIP 68)\n\nAre any other numbers currently expected by any wallet software to be\nbroadcastable with the DISABLE flag set? Does anyone use *this* number? Is\nthere any advantage of this number v.s. just 0? Do people commonly use\n0xfffffffd? 0xfffffffe is special, but it seems the former has the\nalternative of either 0 valued sequence lock (1\u003c\u003c22 or 0).\n\nAre there any other sequence numbers that are not defined in a BIP that\nmight be used somewhere?\n\nCheers,\n\nJeremy\n--\n@JeremyRubin \u003chttps://twitter.com/JeremyRubin\u003e\n\u003chttps://twitter.com/JeremyRubin\u003e\n\n\nOn Fri, Sep 3, 2021 at 8:32 PM Jeremy \u003cjlrubin at mit.edu\u003e wrote:\n\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\u003e\n\u003e I've proposed patching it here\n\u003e https://github.com/bitcoin/bitcoin/pull/22871, it is proper to widely\n\u003e survey the community before patching to ensure no one is depending on the\n\u003e current semantics in any live application lest this tightening of\n\u003e standardness rules engender a confiscatory effect.\n\u003e\n\u003e Best,\n\u003e\n\u003e Jeremy\n\u003e\n\u003e --\n\u003e @JeremyRubin \u003chttps://twitter.com/JeremyRubin\u003e\n\u003e \u003chttps://twitter.com/JeremyRubin\u003e\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20210904/036089ac/attachment.html\u003e"}