From: Gregory Maxwell <gmaxwell@gmail.com>
To: Justus Ranvier <justusranvier@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>,
"Goss, Brian C., M.D." <Goss.Brian@mayo.edu>
Subject: Re: [Bitcoin-development] Dust recycling
Date: Sat, 29 Mar 2014 13:33:13 -0700 [thread overview]
Message-ID: <CAAS2fgRAErVJJN8gAuNnBpgGjBx2U+0_sVwC351u7qvYvbpdfg@mail.gmail.com> (raw)
In-Reply-To: <53372B14.3050901@gmail.com>
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.
prev parent reply other threads:[~2014-03-29 20:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.85219.1396122262.2178.bitcoin-development@lists.sourceforge.net>
[not found] ` <3dfcdc$g3rb2n@ironport9.mayo.edu>
2014-03-29 19:59 ` [Bitcoin-development] Dust recycling Justus Ranvier
2014-03-29 20:05 ` Gregory Maxwell
2014-03-29 20:20 ` Justus Ranvier
2014-03-29 20:33 ` Gregory Maxwell [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAAS2fgRAErVJJN8gAuNnBpgGjBx2U+0_sVwC351u7qvYvbpdfg@mail.gmail.com \
--to=gmaxwell@gmail.com \
--cc=Goss.Brian@mayo.edu \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=justusranvier@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox