What Is Transaction Malleability? Transaction malleability is the ability of a transaction to have multiple valid txids. Malleability occurs when a part of a transaction can change after the transaction has been signed without invalidating the signature.

Since a txid is a hash of the transaction, any change to the transaction will result in a change of the txid. However, changes that alter the txid and invalidate the signatures are not a concern; only changes which alter the txid and do not invalidate the signature raise malleability concerns.

Why Is Transaction Malleability a Problem? Transaction malleability is a problem for developers and users who want to reference a previous transaction in a new spending transaction before the previous transaction has been confirmed on the blockchain. This problem arises because, in order to spend bitcoin created by a previous transaction, the spending transaction must reference the txid of the previous transaction.

If this txid can change, the reference will fail, and the spending transaction will be rendered invalid. Before SegWit, transaction malleability was a problem preventing the adoption of the Lightning Network, which relies on the exchange of unconfirmed bitcoin transactions.

How Can Transaction Malleability Happen? A transaction can be malleated in two ways. First, after being signed, additional data can be added to a ScriptSig.

Secondly, the signature itself, which is contained within the ScriptSig, can be changed. These options are both possible because a signature cannot sign itself. Eliminating transaction malleability was achieved by the SegWit upgrade, enabling more innovation on top of Bitcoin, including the Lightning Network and Taproot.

SegWit eliminated transaction malleability by moving the ScriptSig—the transaction signature and the malleable part of the transaction—from the main body of the transaction into a separate Witness section.