📅 Original date posted:2015-11-06
📝 Original message: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
jl2012 at xbt.hk [ARCHIVE] /
npub1kc…wjfw4
2023-06-07 17:44:16
in reply to nevent1q…0klz
Author Public Key
npub1kc0zulxt7j4a0ayhzhrz7jk84y7tm4026qcky7w97hlfkxxap24qnwjfw4Published at
2023-06-07 17:44:16Event JSON
{
"id": "97b7cfe51e4262d399aeb1436862da1d7f51cd421e3c9b9df99837d6c756fbc9",
"pubkey": "b61e2e7ccbf4abd7f49715c62f4ac7a93cbdd5ead0316279c5f5fe9b18dd0aaa",
"created_at": 1686159856,
"kind": 1,
"tags": [
[
"e",
"8bea40c9aca13fd590801b4ac87b57a3fa19ab1b40338c62d08701cf4269e071",
"",
"reply"
],
[
"p",
"a23dbf6c6cc83e14cc3df4e56cc71845f611908084cfe620e83e40c06ccdd3d0"
]
],
"content": "📅 Original date posted:2015-11-06\n📝 Original message:I have a new BIP draft for fixing OP_IF and OP_NOTIF malleability. \nPlease comment: \nhttps://github.com/jl2012/bips/blob/master/opifmalleability.mediawiki\n\nCopied below:\n\nBIP: x\n Title: Dealing with OP_IF and OP_NOTIF malleability\n Author: jl2012 \u003cjl2012 at xbt.hk\u003e\n Status: Draft\n Type: Standards Track\n Created: 2015-11-06\n\nAbstract\n\nAs an supplement to BIP62, this document specifies proposed changes to \nthe Bitcoin transaction validity rules in order to make malleability of \ntransactions with OP_IF and OP_NOTIF impossible.\n\nMotivation\n\nOP_IF and OP_NOTIF are flow control codes in the Bitcoin script system. \nThe programme flow is decided by whether the top stake value is 0 or \nnot. However, this behavior opens a source of malleability as a third \nparty may alter a non-zero flow control value to any other non-zero \nvalue without invalidating the transaction.\n\nAs of November 2015, OP_IF and OP_NOTIF are not commonly used in the \nblockchain. However, as more sophisticated functions such as \nOP_CHECKLOCKTIMEVERITY are being introduced, OP_IF and OP_NOTIF will \nbecome more popular and the related malleability should be fixed. This \nproposal serves as a supplement to BIP62 and should be implemented with \nother malleability fixes together.\n\nSpecification\n\nIf the transaction version is 3 or above, the flow control value for \nOP_IF and OP_NOTIF must be either 0 or 1, or the transaction fails.\n\nThis is to be implemented with BIP62.\n\nCompatibility\n\nThis is a softfork. To ensure OP_IF and OP_NOTIF transactions created \nbefore the introduction of this BIP will still be accpeted by the \nnetwork, the new rules only apply to transactions of version 3 or above.\n\nFor people who want to preserve the original behaviour of OP_IF and \nOP_NOTIF, an OP_0NOTEQUAL could be used before the flow control code to \ntransform any non-zero value to 1.\n\nReference\n\nBIP62: https://github.com/bitcoin/bips/blob/master/bip-0062.mediawiki",
"sig": "30c2fce8a187f7a042084381ad1f1858e07b5585e70606e06cab16caa4d11f9e4916ce095ec023fbce2464ba9736b4a38d07cbaed5f70602acf2a029689c55fe"
}