Handling “dead” (double-spent) transactions in my mempool

Question

Say I receive transaction A and it is in my node's mempool and unconfirmed.

Then a block gets mined directly, which spends one of transaction A's inputs, rendering transaction A invalid.

What can I expect my node to respond with, when I ask: getrawtransaction <transaction A's txid>?

Pieter Wuille · Accepted Answer · 2020-03-26 16:42:04Z

3

A will be kicked out of the mempool when that block is received, and getrawtransaction will subsequently fail for it.

answered Mar 26 '20 at 16:42

Pieter Wuille

67.3k8 gold badges145 silver badges220 bronze badges

Is there a good way to differentiate between getting kicked due to a double spend, vs getting kicked from the mempool due to a low fee for too long in a high volume environment? I know we could keep track of the transaction's inputs, and check if any of these inputs have been spent, but wondering if there's an easier way that doesn't require keeping track of inputs. – deezy Jul 30 '20 at 17:18

Add a comment |

1 Answer 1