Dealing with dummy stack element malleability

The five-minute read

One action, walked through

1. Open BIP 147 and read the status line before the examples.
2. Write down the rule in one sentence. A fair version of that sentence is: This document specifies proposed changes to the Bitcoin transaction validity rules to fix a malleability vector in the extra stack element consumed by OP_CHECKMULTISIG and OP_CHECKMULTISIGVERIFY .
3. Name the object that changes: OP_CHECKMULTISIG, OP_CHECKMULTISIGVERIFY, BIP141.
4. Ask what an old client, an old contract, or an offline counterparty does. If the document is silent, the silence is part of the design.

The argument, unpacked

What has to be true

• You are implementing BIP 147 at the status the text itself states: Deployed.
• The object that has to change is OP_CHECKMULTISIG, OP_CHECKMULTISIGVERIFY, BIP141. A neighbouring document with a similar name is not this one.
• Activation is a separate mechanism from the opcode or the sighash. This page does not pick a height.

What happened after the paper

The source marks this deployed. That is a statement about the text, not a promise that every wallet or node has shipped it. Later documents can narrow, replace, or ignore this one. Cite the number you mean.

What to check before you use the idea

• Which bytes become invalid under Dealing with dummy stack element malleability, and which old transactions stay valid?
• Is enforcement in consensus, or only in the mempool policy of one client?
• Which of these objects does the text actually define: OP_CHECKMULTISIG, OP_CHECKMULTISIGVERIFY, BIP141?

Terms

BIP 147

The public text titled Dealing with dummy stack element malleability.

Deployed

The document's own label for how finished the text is. It is not a market fact.

The problem the paper names

Bitcoin script and block validity only change when a soft fork says an old pattern is now invalid. Without that rule, every node is free to accept what this document wants to reject.

What the design proposes

• This document specifies proposed changes to the Bitcoin transaction validity rules to fix a malleability vector in the extra stack element consumed by OP_CHECKMULTISIG and OP_CHECKMULTISIGVERIFY .
• Signature malleability refers to the ability of any relay node on the network to transform the signature in transactions, with no access to the relevant private keys required.
• For non-segregated witness transactions, signature malleability will change the txid and invalidate any unconfirmed child transactions.

How the mechanism is specified

• Taken from the specification, the next constraint is: Signature malleability refers to the ability of any relay node on the network to transform the signature in transactions, with no access to the relevant private keys required.
• Locate OP_CHECKMULTISIG, OP_CHECKMULTISIGVERIFY, BIP141 in BIP 147 and apply it to one transaction or call.
• Then check the failure the class of rule always has: a node that did not upgrade, a reverted call, a replayed signature, or a peer that does not speak the message.

What this page does not treat as proven

• A soft fork does not bind a node that never upgrades. It binds the nodes that enforce the new rejection.
• Activation is a separate mechanism from the opcode or the sighash. This page does not pick a height.
• The source marks this deployed. That is a statement about the text, not a promise that every wallet or node has shipped it.

Why a venture studio still reads it

Use BIP 147 when a pitch says 'Dealing with dummy stack element malleability' without saying whether the rule is consensus, policy, or an interface. The number is the citation. The pitch is not.