From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WTzwO-0004HE-T6 for bitcoin-development@lists.sourceforge.net; Sat, 29 Mar 2014 20:33:20 +0000 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; Received: from mail-lb0-f179.google.com ([209.85.217.179]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WTzwO-0007BU-4s for bitcoin-development@lists.sourceforge.net; Sat, 29 Mar 2014 20:33:20 +0000 Received: by mail-lb0-f179.google.com with SMTP id p9so4769444lbv.10 for ; Sat, 29 Mar 2014 13:33:13 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.152.18.229 with SMTP id z5mr3142516lad.27.1396125193441; Sat, 29 Mar 2014 13:33:13 -0700 (PDT) Received: by 10.112.89.68 with HTTP; Sat, 29 Mar 2014 13:33:13 -0700 (PDT) In-Reply-To: <53372B14.3050901@gmail.com> References: <3dfcdc$g3rb2n@ironport9.mayo.edu> <53372605.7010405@gmail.com> <53372B14.3050901@gmail.com> Date: Sat, 29 Mar 2014 13:33:13 -0700 Message-ID: From: Gregory Maxwell To: Justus Ranvier Content-Type: text/plain; charset=UTF-8 X-Spam-Score: -1.6 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (gmaxwell[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1WTzwO-0007BU-4s Cc: Bitcoin Dev , "Goss, Brian C., M.D." Subject: Re: [Bitcoin-development] Dust recycling X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Mar 2014 20:33:21 -0000 On Sat, Mar 29, 2014 at 1:20 PM, Justus Ranvier 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.