8
2
I have created, signed and sent a raw transaction via bitcoind RPC. Now I want to wait for it to have n confirmations.
Considering transaction malleability, I can't just check the "confirmations" field returned by gettransaction, because the transaction with that particular txid may never be accepted, in case an equivalent transaction with some other txid was accepted instead.
So, what is the canonical way, using bitcoind JSON-RPC, to check if an equivalent transaction was accepted in place of mine? What calls are better suited for the task?
So it is organized by output addresses, but what this fee means? If my transaction has 2 output addresses, the entries returned by
listtransactionsfor both will contain the same fee? – lvella – 2015-02-17T16:54:27.377The fee will be the same, yes. – Jimmy Song – 2015-02-17T21:42:54.067
1I am somewhat unsatisfied with this answer, because the answer for
listtransactionswill become increasingly large with my wallet usage. That won't be practical, if checking outgoing transactions is a routine operation. – lvella – 2015-03-28T06:10:33.177wouldn't an answer be that you get a negative confirmation amount if a malleability tx got confirmed instead? – tobi – 2017-04-03T09:35:27.400