Feature request: warn if a transaction will consolidate balances

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Send an amount to another address
2. Observe a local balance of X BTC
3. 0 BTC is available for spending

What is the expected output? What do you see instead?

I expected to be able to spend the remainder of my balance immediately.

What version of Bitcoin Wallet are you using? On what Android version and
what phone? Don't just state 'most recent', this is not enough info.

2.20

Today, I had a few transactions to make using Multibit, but was halted by the 
sudden unavailability of my balance because the balance of two addresses had to 
be combined in order to submit a payment, with change being returned to a 
single one of my addresses in the same transaction. I observed this behavior on 
Bitcoin Wallet for Android a few days ago, but thought it was just how BWfA 
works.

I wrote up [a quick explanation of balance 
consolidation](http://bitcoin.stackexchange.com/questions/4560/after-sending-som
e-bitcoins-why-do-i-have-zero-available-to-spend-when-i-clearl/) at the Bitcoin 
StackExchange.

It'd be nice if clients warned me that the transaction I was about to create 
would necessitate combining the balance of two addresses, leaving me with 0 BTC 
available until the transaction was fully confirmed. Had I known that would be 
the case, I may have sent coins from another wallet/client in order to avoid 
having 0 BTC available.

Original issue reported on code.google.com by colind...@gmail.com on 27 Aug 2012 at 1:18

[GoogleCodeExporter]

Most probably, this issue will be solved by letting the user immediately spend 
change.

The only reason for the current behaviour is that in earlier versions, the 
client had no indication if its transaction has actually been accepted by the 
network. With the confidence enhancements in bitcoinj 0.6 / Bitcoin Wallet 2.23 
we can now change the current behaviour.

Also see http://code.google.com/p/bitcoinj/issues/detail?id=40

Original comment by andreas....@gmail.com on 6 Oct 2012 at 3:17

• Changed state: Accepted
• Added labels: Priority-Low, Type-Enhancement
• Removed labels: Priority-Medium, Type-Defect

[GoogleCodeExporter]

You are now able to spend your change immediately. So I assume the issue is 
fixed.

Original comment by andreas....@gmail.com on 13 Apr 2013 at 4:16

• Changed state: Fixed

[GoogleCodeExporter]

Yeah, that'll do it. Thanks!

Original comment by colind...@gmail.com on 13 Apr 2013 at 5:49