j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckMj<div class="post">As you figured out, the root problem is we shouldn't be counting or spending transactions until they have at least 1 confirmation. 0/unconfirmed transactions are very much second class citizens. At most, they are advice that something has been received, but counting them as balance or spending them is premature.<br/><br/>I made changes so they show up in lighter print, with the credit amount in square brackets like [+1.23], and the amount not counted towards your balance and not available for spending. This doesn't apply to transactions you sent, which you implicitly trust, since you wrote them.<br/><br/>I didn't make it (+1.23) because parenthesis in accounting means negative. I hope square brackets is different enough to be clear what is meant.<br/><br/>The JSON-RPC interface can still see 0/unconfirmed if it wants by specifying 0 confirmations.<br/><br/>I uploaded the changes to SVN rev 158. I will post a 0.3.13 RC shortly.<br/><br/>If you have any of these transactions in your wallet, do not send any payments until you've upgraded to 0.3.13, which will be coming soon.<br/><br/>If you've already sent any of these transactions, or you're the creator of them, then use theymos' patch or make the following change and use it to send your clean transactions to a new wallet to clean things up.<br/><br/>change:<br/> if (pcoin->GetDepthInMainChain() < 1 && pcoin->GetDebit() <= 0)<br/> continue;<br/>to:<br/> if (pcoin->GetDepthInMainChain() < 1)<br/> continue;<br/></div> text/html
https://whatsonchain.com/tx/ac14e7d1a3f8137bf1b7a785c333290e99bc9916275d6e8564deb32f02e1aae2