Author: Stephen Morse 2015-05-19 12:48:20
Published on: 2015-05-19T12:48:20+00:00
The discussion is about including the height in transactions without adding an extra field. It is suggested that for non-coinbase transactions, the height used is zero, and for coinbase transactions, the height specified in the scriptSig is copied into the locktime of the transaction before computing the normalized transaction ID. However, it is argued that there's no need to replace lock times or any other part of the transaction at all. Instead, the height can be serialized right before serializing the transaction and 0 can be pre-serialized for non-coinbase transactions. The normalization process for non-coinbase transactions involves replacing prevout hash with normalized hash and clearing the scriptSig. Finally, the transaction is serialized using CHashWriter.
Updated on: 2023-06-09T20:56:28.350311+00:00