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:05:05 -0700 [thread overview]
Message-ID: <CAAS2fgTi8CetE44tBetbwrPNy=NWH79imSiivYKshxxb_J6h=Q@mail.gmail.com> (raw)
In-Reply-To: <53372605.7010405@gmail.com>
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. :)
next prev parent reply other threads:[~2014-03-29 20:05 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 ` Justus Ranvier
2014-03-29 20:05 ` Gregory Maxwell [this message]
2014-03-29 20:20 ` Justus Ranvier
2014-03-29 20:33 ` Gregory Maxwell
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='CAAS2fgTi8CetE44tBetbwrPNy=NWH79imSiivYKshxxb_J6h=Q@mail.gmail.com' \
--to=gmaxwell@gmail$(echo .)com \
--cc=Goss.Brian@mayo$(echo .)edu \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=justusranvier@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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