Btc Drak 於 2015-09-17 15:12 寫到:

Forgive me if I have missed the exact use-case, but this seems overly
complex. Surely fill-or-kill refers to getting a transaction confirmed
within a few confirms or to drop the tx from the mempool so it wont be
considered for inclusion anymore. As such, you could just repurpose a
small range of nLocktime such that a TX will be accepted into mempool
for a specific period before expiring.

What I'm describing is to implement fill-or-kill as consensus rule. Certainly, we could implement it at the P2P network level: everything is the same as I described, but the nLockTime2 and nKillTime are for reference only and tx validity depends only on the nLockTime. Benevolent miners should drop the tx after the suggested kill time but there is no guarantee