Author: Luke Dashjr 2016-09-17 21:10:26
Published on: 2016-09-17T21:10:26+00:00
A proposed solution to transaction ID malleability in Bitcoin was suggested by Rune K. Svendsen via bitcoin-dev mailing list. The solution involves introducing a new opcode called OP_TXHASHVERIFY, which would only work if added to a scriptSig as the very first operation and would abort if the hash of the transaction with all OP_TXHASHVERIFY operations removed does not match what has been pushed on the stack. This would add 34 bytes per input but is considered a simple solution until something better like SegWit becomes available. However, a reply from Luke suggested that it may be more trouble than SegWit to deploy and would not completely fix the problem as anyone malleating the transaction could simply update the hash before this opcode.
Updated on: 2023-06-11T19:59:42.997850+00:00