[BIP draft] CHECKLOCKTIMEVERIFY - Prevent a txout from being spent until an expiration time

Author: Sergio Lerner 2014-10-01 15:29:48
Published on: 2014-10-01T15:29:48+00:00

• Combined Summary of all posts in thread
• Click here to read original discussion on the bitcoin-dev mailing list

Summary:

The proposal of broadcasting transactions having OP_CHECKLOCKTIMEVERIFY a few blocks after the timeout value is favored. However, if a node broadcasts a transaction with OP_CHECKLOCKTIMEVERIFY and nLockTime equal to the current height and timeout value but is one block behind in the blockchain, the transaction will be rejected and the source will be banned. One alternative suggested was not to ban peers who send transactions that fail to verify OP_CHECKLOCKTIMEVERIFY, but it was not well-liked. Another option would be for the sender to periodically check the height of their peers using the version command to ensure that the transaction with OP_CHECKLOCKTIMEVERIFY is only sent to peers up-to-date with the blockchain. These options were provided by Sergio.

Updated on: 2023-06-09T02:52:11.280022+00:00