JSON-RPC to detect double-spent TXs

If your node received the original spend, the listunspent RPC will display the transaction with "-1" confirmations, as will any other RPCs that would normally list the transaction. The source code calls this conflicted: "not in the mempool and not in the block chain." This feature was first included in 0.9.0.

If your node never received the original spend (perhaps because it was offline at the time) or the now-stale block that contained it, it doesn't have any way to know about that original spend, so there's no information you can get from an RPC.

David A. Harding

Posted 2014-11-20T12:27:57.880

Reputation: 10 154

Thanks David! Now I'm really concerned about this: http://bitcoin.stackexchange.com/questions/730/what-does-the-bitcoin-client-do-when-it-receives-conflicting-transactions I wish I could find an update on that answer

– Doug Peters – 2014-11-20T18:47:32.973

AFAIR listunspent doesn't return txs that have < 0 confirmations. listsinceblock will not show them either but you can use listtransactions instead which does. – George Kimionis – 2015-01-03T18:32:59.800

JSON-RPC to detect double-spent TXs

Answers