Author: Christian Decker 2014-08-06 15:17:02
Published on: 2014-08-06T15:17:02+00:00
In a discussion among Bitcoin developers, Jeff Garzik suggests that a new field for expiration time should be introduced instead of overloading existing fields with new meaning. Tom Harding agrees and suggests using nLockTime for expiration would not be appropriate since it begins as invalid and becomes valid after nLockTime passes. Mike Hearn proposes introducing a new field in a new tx version. However, Jeff Garzik argues that existing users and uses of nLockTime would become worthless if this were to happen suddenly, breaking payment channel refunds and other active uses of nLockTime. He suggests that a new, separate field containing expiration time would be more appropriate. The group also discusses the potential benefits of using nLockTime for expiration, such as preventing transaction creators from lying to help transactions live longer without pushing initial confirmation eligibility into the future.
Updated on: 2023-06-09T01:46:03.540548+00:00