Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.217.179 as permitted sender)
	client-ip=209.85.217.179; envelope-from=gmaxwell@gmail.com;
	helo=mail-lb0-f179.google.com; 
MIME-Version: 1.0
In-Reply-To: <53372B14.3050901@gmail.com>
References: <mailman.85219.1396122262.2178.bitcoin-development@lists.sourceforge.net>
	<3dfcdc$g3rb2n@ironport9.mayo.edu> <53372605.7010405@gmail.com>
	<CAAS2fgTi8CetE44tBetbwrPNy=NWH79imSiivYKshxxb_J6h=Q@mail.gmail.com>
	<53372B14.3050901@gmail.com>
Date: Sat, 29 Mar 2014 13:33:13 -0700
Message-ID: <CAAS2fgRAErVJJN8gAuNnBpgGjBx2U+0_sVwC351u7qvYvbpdfg@mail.gmail.com>
From: Gregory Maxwell <gmaxwell@gmail.com>
To: Justus Ranvier <justusranvier@gmail.com>
Content-Type: text/plain; charset=UTF-8
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>, "Goss, Brian C.,
	M.D." <Goss.Brian@mayo.edu>
Subject: Re: [Bitcoin-development] Dust recycling
Precedence: list

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.