📅 Original date posted:2015-11-06
📝 Original message:One and zero should be defined as arrays of length one. Otherwise, it is
still possible to mutate the transaction by changing the length of the
array.
They should also be minimally encoded but that is covered by previous rules.
On Fri, Nov 6, 2015 at 8:13 AM, jl2012 via bitcoin-dev <
bitcoin-dev at lists.linuxfoundation.org> wrote:
> I have a new BIP draft for fixing OP_IF and OP_NOTIF malleability. Please
> comment:
> https://github.com/jl2012/bips/blob/master/opifmalleability.mediawiki
>
> Copied below:
>
> BIP: x
> Title: Dealing with OP_IF and OP_NOTIF malleability
> Author: jl2012 <jl2012 at xbt.hk>
> Status: Draft
> Type: Standards Track
> Created: 2015-11-06
>
> Abstract
>
> As an supplement to BIP62, this document specifies proposed changes to the
> Bitcoin transaction validity rules in order to make malleability of
> transactions with OP_IF and OP_NOTIF impossible.
>
> Motivation
>
> OP_IF and OP_NOTIF are flow control codes in the Bitcoin script system.
> The programme flow is decided by whether the top stake value is 0 or not.
> However, this behavior opens a source of malleability as a third party may
> alter a non-zero flow control value to any other non-zero value without
> invalidating the transaction.
>
> As of November 2015, OP_IF and OP_NOTIF are not commonly used in the
> blockchain. However, as more sophisticated functions such as
> OP_CHECKLOCKTIMEVERITY are being introduced, OP_IF and OP_NOTIF will become
> more popular and the related malleability should be fixed. This proposal
> serves as a supplement to BIP62 and should be implemented with other
> malleability fixes together.
>
> Specification
>
> If the transaction version is 3 or above, the flow control value for OP_IF
> and OP_NOTIF must be either 0 or 1, or the transaction fails.
>
> This is to be implemented with BIP62.
>
> Compatibility
>
> This is a softfork. To ensure OP_IF and OP_NOTIF transactions created
> before the introduction of this BIP will still be accpeted by the network,
> the new rules only apply to transactions of version 3 or above.
>
> For people who want to preserve the original behaviour of OP_IF and
> OP_NOTIF, an OP_0NOTEQUAL could be used before the flow control code to
> transform any non-zero value to 1.
>
> Reference
>
> BIP62: https://github.com/bitcoin/bips/blob/master/bip-0062.mediawiki
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20151106/d815e1ae/attachment.html>;
Tier Nolan [ARCHIVE] /
npub1g6…sl5wd
2023-06-07 17:44:17
in reply to nevent1q…k0uk
Author Public Key
npub1g6vxlp4e0nyhs2dqxxcryztyf5f5hyuaq93nw4r87zcnv0sdsa0qqsl5wdPublished at
2023-06-07 17:44:17Event JSON
{
"id": "da1ac7112d24447e68eeedfd87ee252d2c2d7abfe1ea1b622dcb59637def5193",
"pubkey": "46986f86b97cc97829a031b03209644d134b939d0163375467f0b1363e0d875e",
"created_at": 1686159857,
"kind": 1,
"tags": [
[
"e",
"8bea40c9aca13fd590801b4ac87b57a3fa19ab1b40338c62d08701cf4269e071",
"",
"root"
],
[
"e",
"a591f47dd4c24663480b535621ad3b01c0b7a77fc47fc1cf075ffafc4cfe96d6",
"",
"reply"
],
[
"p",
"2a9b7d3423041901b738be6b1d40a6e4dd3f9041e7a5fa4a2d3c662d296814c7"
]
],
"content": "📅 Original date posted:2015-11-06\n📝 Original message:One and zero should be defined as arrays of length one. Otherwise, it is\nstill possible to mutate the transaction by changing the length of the\narray.\n\nThey should also be minimally encoded but that is covered by previous rules.\n\nOn Fri, Nov 6, 2015 at 8:13 AM, jl2012 via bitcoin-dev \u003c\nbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\n\u003e I have a new BIP draft for fixing OP_IF and OP_NOTIF malleability. Please\n\u003e comment:\n\u003e https://github.com/jl2012/bips/blob/master/opifmalleability.mediawiki\n\u003e\n\u003e Copied below:\n\u003e\n\u003e BIP: x\n\u003e Title: Dealing with OP_IF and OP_NOTIF malleability\n\u003e Author: jl2012 \u003cjl2012 at xbt.hk\u003e\n\u003e Status: Draft\n\u003e Type: Standards Track\n\u003e Created: 2015-11-06\n\u003e\n\u003e Abstract\n\u003e\n\u003e As an supplement to BIP62, this document specifies proposed changes to the\n\u003e Bitcoin transaction validity rules in order to make malleability of\n\u003e transactions with OP_IF and OP_NOTIF impossible.\n\u003e\n\u003e Motivation\n\u003e\n\u003e OP_IF and OP_NOTIF are flow control codes in the Bitcoin script system.\n\u003e The programme flow is decided by whether the top stake value is 0 or not.\n\u003e However, this behavior opens a source of malleability as a third party may\n\u003e alter a non-zero flow control value to any other non-zero value without\n\u003e invalidating the transaction.\n\u003e\n\u003e As of November 2015, OP_IF and OP_NOTIF are not commonly used in the\n\u003e blockchain. However, as more sophisticated functions such as\n\u003e OP_CHECKLOCKTIMEVERITY are being introduced, OP_IF and OP_NOTIF will become\n\u003e more popular and the related malleability should be fixed. This proposal\n\u003e serves as a supplement to BIP62 and should be implemented with other\n\u003e malleability fixes together.\n\u003e\n\u003e Specification\n\u003e\n\u003e If the transaction version is 3 or above, the flow control value for OP_IF\n\u003e and OP_NOTIF must be either 0 or 1, or the transaction fails.\n\u003e\n\u003e This is to be implemented with BIP62.\n\u003e\n\u003e Compatibility\n\u003e\n\u003e This is a softfork. To ensure OP_IF and OP_NOTIF transactions created\n\u003e before the introduction of this BIP will still be accpeted by the network,\n\u003e the new rules only apply to transactions of version 3 or above.\n\u003e\n\u003e For people who want to preserve the original behaviour of OP_IF and\n\u003e OP_NOTIF, an OP_0NOTEQUAL could be used before the flow control code to\n\u003e transform any non-zero value to 1.\n\u003e\n\u003e Reference\n\u003e\n\u003e BIP62: https://github.com/bitcoin/bips/blob/master/bip-0062.mediawiki\n\u003e\n\u003e _______________________________________________\n\u003e bitcoin-dev mailing list\n\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20151106/d815e1ae/attachment.html\u003e",
"sig": "a2a9c929a2916ac1eef53ecfb77a05043e8e5b53ebef8ced653e4cc12d9990474233f80a0e7fbe255b539dc3f74d2d0bfc8a6cbbc988e62c95cd023b41702f04"
}