📅 Original date posted:2015-11-06
📝 Original message:Your suggested modification seems sound.
Though, a script author could do something similar right now by
prefacing his IF with this:
OP_DUP OP_DUP OP_0 OP_EQUAL OP_SWAP OP_1 OP_EQUAL OP_BOOLOR
OP_NOTIF OP_RETURN OP_ENDIF [actual OP_IF goes here]
That checks whether the input is 0 or 1, and runs OP_RETURN if not.
Your way is cleaner, though.
On Fri, Nov 6, 2015 at 1: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
Nick ODell [ARCHIVE] /
npub192…qwur0
2023-06-07 17:44:17
in reply to nevent1q…kmw0
Author Public Key
npub192dh6dprqsvsrdeche436s9xunwnlyzpu7jl5j3d83nz62tgznrsnqwur0Published at
2023-06-07 17:44:17Event JSON
{
"id": "a591f47dd4c24663480b535621ad3b01c0b7a77fc47fc1cf075ffafc4cfe96d6",
"pubkey": "2a9b7d3423041901b738be6b1d40a6e4dd3f9041e7a5fa4a2d3c662d296814c7",
"created_at": 1686159857,
"kind": 1,
"tags": [
[
"e",
"8bea40c9aca13fd590801b4ac87b57a3fa19ab1b40338c62d08701cf4269e071",
"",
"root"
],
[
"e",
"97b7cfe51e4262d399aeb1436862da1d7f51cd421e3c9b9df99837d6c756fbc9",
"",
"reply"
],
[
"p",
"b61e2e7ccbf4abd7f49715c62f4ac7a93cbdd5ead0316279c5f5fe9b18dd0aaa"
]
],
"content": "📅 Original date posted:2015-11-06\n📝 Original message:Your suggested modification seems sound.\n\nThough, a script author could do something similar right now by\nprefacing his IF with this:\n\n OP_DUP OP_DUP OP_0 OP_EQUAL OP_SWAP OP_1 OP_EQUAL OP_BOOLOR\nOP_NOTIF OP_RETURN OP_ENDIF [actual OP_IF goes here]\n\nThat checks whether the input is 0 or 1, and runs OP_RETURN if not.\nYour way is cleaner, though.\n\nOn Fri, Nov 6, 2015 at 1:13 AM, jl2012 via bitcoin-dev\n\u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\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. The\n\u003e 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 before\n\u003e the introduction of this BIP will still be accpeted by the network, the new\n\u003e 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",
"sig": "91b3dc35833fdd38b4791e46db0a5fd09a0022a051b834f223607b6a768ea381934d401b060480d74f60e03a3e7299a548d0c5f17cde85c6f37f6a63662422b4"
}