Fight dust

[GoogleCodeExporter]

I'm searching for more workarounds to keep wallets clean.

What about this: If the user receives dust like this
https://blockchain.info/tx/31cc0f813ed0798bf47618243d4e5a37f877660c164e40616c4fe
c35a8a449b0
the transaction is immediately moved to the dead pool (or perhaps a new pool) 
with everything stripped except the input/output(s) that are relevant. And 
maybe not even those remaining, but somehow it would be nice to still be able 
to say how much it would have affected the wallet.

Goals:
- Those outputs are not picked for spending.
- The user gets an entry in his tx list that warns from getting more dust like 
this.

In the dead pool, it will at some time be garbage collected like other dead 
transactions will (in future) be.

If at some time we will be able to spend such an output economically (by 
changing priority rules, piggy-backing, etc.) the user will need to replay the 
blockchain once.

Original issue reported on code.google.com by andreas....@gmail.com on 12 Apr 2013 at 8:53

[GoogleCodeExporter]

I think the dust rules that come with the new fee rules work in this direction.

Original comment by andreas....@gmail.com on 17 Jun 2013 at 11:15

[GoogleCodeExporter]

Yes, though I'd also like to see the coin selector/fee rules try to pull in 
dust inputs until it causes fee to go up or causes size to go up significantly 
enough that the transaction wont be confirmed. That would require some thought, 
though (and probably some knowledge of what the minimum require fee per 
kb/priority per kb is to get into a block)

Original comment by coral...@google.com on 17 Jun 2013 at 12:10