Author: Eric Lombrozo 2015-11-27 08:10:49
Published on: 2015-11-27T08:10:49+00:00
The discussion focuses on the relative locktime (or minimum age) and the nSequence field in transactions, which currently plays a combined role. The lack of a dedicated field for the purpose of relative locktime is considered unfortunate as it requires repurposing unused bits in the txin. However, there may be ways around this issue using segwit. One suggestion is to add an extra input vector to the prunable extra data that comprises the witness. Witness structures can provide additional data that is used in transaction validation but does not contribute to the tx hash. While signatures cannot contribute to the hash they are signing, segwit makes this separation explicit by moving the signatures to a structure external to the script. Adding extra prunable signed data fields to transactions may ultimately remove scarcity of tx data that can be repurposed via soft forks. The nSequence field could be turned into a dedicated min age/rlt field to simplify semantics and avoid ugliness in trying to reclaim unused bits.
Updated on: 2023-06-11T01:20:56.891309+00:00