Author: Jorge Timón 2015-05-06 07:37:37
Published on: 2015-05-06T07:37:37+00:00
A discussion among developers on the Bitcoin-development mailing list focused on the semantics of nSequence and a proposed change to its function in order to allow for relative locktime. The proposed change would make it so that transactions with an nSequence value less than or equal to their input's sequence number could be considered valid after a certain block height. Some developers expressed concerns about this change, arguing that it could reduce confidence in the currency if previously valid transactions became invalid. One suggested workaround was to have a way to enable relative locktime in the sigScript by extending Peter Todd's suggestion. Another proposed solution involved using a simple pattern match to determine whether the script should fail unless it was the first opcode in the script, although some felt that this option was less flexible and unnecessary.
Updated on: 2023-06-09T18:47:48.752753+00:00