Author: Tom Harding 2014-08-06 14:44:25
Published on: 2014-08-06T14:44:25+00:00
In a discussion about introducing a new field in a new transaction version, Jeff Garzik raised concerns that existing users and uses of nLockTime would become worthless, breaking payment channel refunds and other active uses of nLockTime. He argued that it cannot be assumed that the user is around to rewrite their nLockTime if it fails to be confirmed before some arbitrary deadline being set. Tom Harding responded by pointing out that if nLockTime is used for expiration, the transaction creator can't lie to help the transaction live longer without pushing initial confirmation eligibility into the future. This would allow for "fill or kill" transactions with a backdated nLockTime, which must be confirmed in a few blocks or start vanishing from mempools.
Updated on: 2023-06-09T01:45:05.740482+00:00