deterministic transaction expiration



Summary:

The Bitcoin developers are discussing the implementation of a new script opcode that would allow users to prove their ability or inability to spend funds before or after a given date. This would require the client to revalidate all transactions in its mempool whenever the chain tip changes. While there are risks associated with this, it is not mandatory to use. Additionally, the developers discussed the issue of fee-sniping reorgs and proposed setting nLockTime at current-height + 1 to prevent them. They also suggested implementing #3753 (mempool janitor) in a way that allows transactions with nLockTime to live longer in the mempool than those without, and adding an IsStandard rule rejecting transactions with an nLockTime more than N blocks behind the current tip for some fixed value N. Finally, they proposed expiring things from the mempool in Bitcoin Core as a first step towards this change.


Updated on: 2023-06-09T01:47:54.963008+00:00