Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fixed IX confirmation bug for gettransaction
IX confirmations now show up correctly via the RPC interface immediately after IX confirms they are double-spend proof: gettransaction 64c04e06ac058e572cefb5d98728dba21401cb8826f9688cbaf4270adfc6afb2  { "amount" : 0.00000000, "fee" : -0.01000000, "confirmations" : 5, "bcconfirmations" : 0, "txid" : "64c04e06ac058e572cefb5d98728dba21401cb8826f9688cbaf4270adfc6afb2", "walletconflicts" : [ } ... a moment later ...  gettransaction 64c04e06ac058e572cefb5d98728dba21401cb8826f9688cbaf4270adfc6afb2  { "amount" : 0.00000000, "fee" : -0.01000000, "confirmations" : 6, "bcconfirmations" : 1, "blockhash" : "00000000000f850e60431a5a88fba1cd8d3868477056f65493664e2d39c1837c", "blockindex" : 2, "blocktime" : 1443290068, "txid" : "64c04e06ac058e572cefb5d98728dba21401cb8826f9688cbaf4270adfc6afb2", "walletconflicts" : [ ], }
- Loading branch information
71272d4
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can't find the issue with previous implementation... what was it?
71272d4
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Try sending yourself an IX with the old implementation, then run gettransaction on that hash. I was getting a segfault, I looked at it for a couple hours and couldn't find the cause, although it's reproducible.