Dust recycling

On 03/29/2014 07:55 PM, Goss, Brian C., M.D. wrote:

> Could you collect the dust into a transaction with no outputs (thus making it all tx fees) or putting in to an anyone can spend tx?
>
> The large number of signatures (for large n) would make the tx size large...but, if enough dust were out there, it might be worth propagating to a pools hash power.

What would make it easier is if there was a standard output type for sending the entire transaction to miner fees, that would make even large transactions propagate that would normally be dropped by fee/kB rules.

On Sat, Mar 29, 2014 at 12:59 PM, Justus Ranvier <justusranvier@gmail•com> wrote:

> What would make it easier is if there was a standard output type for
> sending the entire transaction to miner fees,

Hm. maybe it could be called a "return operator" or something like that? :)

> that would make even large
> transactions propagate that would normally be dropped by fee/kB rules.

Use dust-b-gone and make it someone elses problem to get it relayed. :)

On 03/29/2014 08:05 PM, Gregory Maxwell wrote:

> Use dust-b-gone and make it someone elses problem to get it relayed. :)
>

That's a sub-optimal solution, as it introduces a third party. What if his server goes down?

An universal solution is preferable.

On Sat, Mar 29, 2014 at 1:20 PM, Justus Ranvier <justusranvier@gmail•com> wrote:

> On 03/29/2014 08:05 PM, Gregory Maxwell wrote:
>> Use dust-b-gone and make it someone elses problem to get it relayed. :)
> That's a sub-optimal solution, as it introduces a third party. What if
> his server goes down?
> An universal solution is preferable.

Then start the server yourself. There is no replacement for aggregating multiple bits of dust in single transactions. Other ways are less efficient.

You can already OP_RETURN to include your dust, but miners aren't going to automatically take that over transactions paying more in terms of fee/byte.