<p>Regardless of what accounts they are in in your wallet, consolidating/spending your dust may require substantial transaction fees - maybe even exceeding the value of the dust. The major factor that comes into play is the size added to a transaction by each additional input. You can read a lot of info on the Bitcoin wiki about <a href="https://en.bitcoin.it/wiki/Transaction_fees" rel="nofollow">transaction fees</a>.</p>

<p>Here are some strategies for reducing/eliminating the fees:</p>

<ul>
<li><strong>Include some dust in a free transaction.</strong> How much you'll be able to include without lowering your priority below the minimum for a free transaction depends on the coin-age you're spending in the transaction (large, old balance = high priority).</li>
<li><strong>Include some dust in a paid transaction.</strong> The 0.0001 BTC per thousand bytes means that if you have a transaction that's only, say, 250 bytes you can add up to 750 bytes of extra data (in this case, dust inputs) for no additional cost.</li>
<li><strong>Transmit your transactions directly to a <a href="https://en.bitcoin.it/wiki/Free_transaction_relay_policy" rel="nofollow">free transaction relay/low-fee pool</a>.</strong> For example, Eligius <a href="http://eligius.st/~gateway/faq-page" rel="nofollow">only requires</a> 0.1 TBC (0.00004096 BTC) per 512 bytes.</li>
<li><strong>Wait it out.</strong> If the value of a bitcoin rises substantially, the transaction fee limits will likely be lowered to account for that, so your dust will not be so dusty-looking.</li>
</ul>

<p>If these all sound like a bit of a pain, that's because Bitcoin isn't really designed for micro-transactions, and much is in place to discourage spamming in the form of "dust".</p>

CC BY-SA 3.0
2014-06-05T15:55:17.240Z
This is because of too many inputs? If this is true then all leftover dust is un-usable (true or false)?
BENZ.404
CC BY-SA 3.0
2014-06-05T16:01:12.910Z
Inputs add size to a transaction. Size adds cost (to prevent spam from overwhelming the network). If you're looking for a true/false answer then, definitely *false*. It's not completely unusable. But practically, it might not be worth the trouble.
Tim S.
CC BY-SA 3.0
2014-06-05T18:21:14.810Z
So what if I do wait a while... please see edit-1 to my question
BENZ.404
CC BY-SA 3.0
2014-06-04T19:01:47.893Z
2014-06-05T16:01:48.220Z
2014-06-05T16:01:48.220Z
Tim S.
<p>Say I have two accounts in my wallet. Account <strong>A</strong> has one address, account <strong>B</strong> though has 5 address. Each address in account B has a dust amount of coin in it. If I were to use the rpc 'move' command, moving each piece of dust from the respective address in account B over to one lump in account A </p>

<blockquote>
  <p>Accounts, exist only within the Bitcoin Core client. They are just a bookkeeping device to group your funds. You can move coins between accounts with the move command in the Bitcoin Core console. This updates the client's internal records to adjust the balances of those accounts, but doesn't actually cause any coins to move between addresses, so it has no fee.</p>
</blockquote>

<p>How is that valid, as account A would have the one primary address? Does this mean that I am sending to another account owned by me so the coin dust is landing in the account ignoring the primary address?</p>

<p>And say for example I then used the lump in account A to buy some new boots. Wouldn't that make the next fee that account A would pay higher as it was made from a collection of dust(s)?</p>

<p>Would I have to wait a considerable amount of time to lower the fee? Is there another strategy I could use to bring the fee down? Like importing an external key from an compressed pubkey from another wallet (<strong>C</strong>), paying to to C from A. I don't yet fully understand public keys and compression but as I understand sending to them is considerably cheaper (something to do with inputs?.. not too sure what exactly those are)</p>

<p>I feel sort of like I am understanding more, can someone please clarify a little and/or correct me?</p>

<p><strong>Edit-1</strong></p>

<p>What if I wait a while then as <a href="https://bitcoin.stackexchange.com/users/12034/tim-s">Tim S</a> suggests... Account B has 5 addresses, lets look at one of them (an address with piece of dust in it). Lets say that some more dust payments were sent to that address making the 'dust pile' grow. </p>

<p>At what point is it not dusty?
Are there still too many inputs? </p>

<p>(Am I confused by the term 'inputs': <strong>"inputs from many addresses in your wallet"</strong> or <strong>"inputs from many payments to the one address"</strong>)</p>

<p>Say I waited 3 days after all the dust came in and settled until it gained priority, then sent the whole dust pile (from that account B address only) to another address. Would it be more worth sending / have I made the situation better?</p>

<json-rpc><movecmd>
Can I lower fees with stratagy
BENZ.404
# Can I lower fees with stratagy

(Asked by: username_0 on 2014-06-04)

Say I have two accounts in my wallet. Account **A** has one address, account **B** though has 5 address. Each address in account B has a dust amount of coin in it. If I were to use the rpc 'move' command, moving each piece of dust from the respective address in account B over to one lump in account A

> Accounts, exist only within the Bitcoin Core client. They are just a bookkeeping device to group your funds. You can move coins between accounts with the move command in the Bitcoin Core console. This updates the client's internal records to adjust the balances of those accounts, but doesn't actually cause any coins to move between addresses, so it has no fee.

How is that valid, as account A would have the one primary address? Does this mean that I am sending to another account owned by me so the coin dust is landing in the account ignoring the primary address?

And say for example I then used the lump in account A to buy some new boots. Wouldn't that make the next fee that account A would pay higher as it was made from a collection of dust(s)?

Would I have to wait a considerable amount of time to lower the fee? Is there another strategy I could use to bring the fee down? Like importing an external key from an compressed pubkey from another wallet (**C**), paying to to C from A. I don't yet fully understand public keys and compression but as I understand sending to them is considerably cheaper (something to do with inputs?.. not too sure what exactly those are)

I feel sort of like I am understanding more, can someone please clarify a little and/or correct me?

**Edit-1**

What if I wait a while then as [username_1](https://bitcoin.stackexchange.com/users/12034/tim-s) suggests... Account B has 5 addresses, lets look at one of them (an address with piece of dust in it). Lets say that some more dust payments were sent to that address making the 'dust pile' grow.

At what point is it not dusty?
Are there still too many inputs?

(Am I confused by the term 'inputs': **"inputs from many addresses in your wallet"** or **"inputs from many payments to the one address"**)

Say I waited 3 days after all the dust came in and settled until it gained priority, then sent the whole dust pile (from that account B address only) to another address. Would it be more worth sending / have I made the situation better?

**Tags:** json-rpc, movecmd


---

## 1 answers

### Answer by username_1 on 2014-06-04. Score: 4

Regardless of what accounts they are in in your wallet, consolidating/spending your dust may require substantial transaction fees - maybe even exceeding the value of the dust. The major factor that comes into play is the size added to a transaction by each additional input. You can read a lot of info on the Bitcoin wiki about [transaction fees](https://en.bitcoin.it/wiki/Transaction_fees).

Here are some strategies for reducing/eliminating the fees:

* **Include some dust in a free transaction.** How much you'll be able to include without lowering your priority below the minimum for a free transaction depends on the coin-age you're spending in the transaction (large, old balance = high priority).
* **Include some dust in a paid transaction.** The 0.0001 BTC per thousand bytes means that if you have a transaction that's only, say, 250 bytes you can add up to 750 bytes of extra data (in this case, dust inputs) for no additional cost.
* **Transmit your transactions directly to a [free transaction relay/low-fee pool](https://en.bitcoin.it/wiki/Free_transaction_relay_policy).** For example, Eligius [only requires](http://eligius.st/~gateway/faq-page) 0.1 TBC (0.00004096 BTC) per 512 bytes.
* **Wait it out.** If the value of a bitcoin rises substantially, the transaction fee limits will likely be lowered to account for that, so your dust will not be so dusty-looking.

If these all sound like a bit of a pain, that's because Bitcoin isn't really designed for micro-transactions, and much is in place to discourage spamming in the form of "dust".

> **Comments:**
> **username_0**: This is because of too many inputs? If this is true then all leftover dust is un-usable (true or false)?  
> **username_1**: Inputs add size to a transaction. Size adds cost (to prevent spam from overwhelming the network). If you're looking for a true/false answer then, definitely *false*. It's not completely unusable. But practically, it might not be worth the trouble.  
> **username_0**: So what if I do wait a while... please see edit-1 to my question  

---

