-
Notifications
You must be signed in to change notification settings - Fork 35.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sweep up dust inputs when there is room #1675
Comments
But fees might not be rounded to kilobyte (and aren't any more, with Gavin's changes, AFAIK) |
Er. I'd missed that. I think we should keep the rounding behavior, both for improved compatibility with current behavior, and also because it leaves some free room for housekeeping operations like this. |
I would say that it is more important to structure costs correctly. It is the creation of dust txouts that causes both the expense of storing them on the blockchain and the eventual expense of redeeming them. A better solution IMO would be to make txins free and calculate fees based on txouts, and then allow clients sweep all dust from their accounts at will. |
@Cryddit alas, for a miner, making them free would be economically irrational since the scarcity creating the market to begin with is the maximum size of the block. (Also, making txins free entirely has the risk of people stuffing kilobytes of data in them for parasitic storage) |
* move bitcoin release notes * 12.2 release notes draft * update * update * add latest commits, turn commits into links * typo + 1704 * +1707 * +1711 * clarify 8x tx
@MarcoFalke I suppose you can close this now that you're a member? |
The coin selection should automatically sweep up excessive small / dust inputs in order to get them out of the txout set when there is room and the txn already has change. (e.g. excess priority before the txn loses freeness, or room before the next kiliobyte fee increment)
This can be done as a post-processing step after the existing selection.
Care should be taken to avoid reducing privacy by linking otherwise independent accounts. This can sometimes increase privacy by further disguising the values exchange.
The text was updated successfully, but these errors were encountered: