From: Justus Ranvier <justusranvier@gmail•com>
To: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Cc: "Goss, Brian C., M.D." <Goss.Brian@mayo•edu>
Subject: Re: [Bitcoin-development] Dust recycling
Date: Sat, 29 Mar 2014 19:59:01 +0000 [thread overview]
Message-ID: <53372605.7010405@gmail.com> (raw)
In-Reply-To: <3dfcdc$g3rb2n@ironport9.mayo.edu>
[-- Attachment #1.1: Type: text/plain, Size: 715 bytes --]
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.
--
Support online privacy by using email encryption whenever possible.
Learn how here: http://www.youtube.com/watch?v=bakOKJFtB-k
[-- Attachment #1.2: 0x1B438BF4.asc --]
[-- Type: application/pgp-keys, Size: 21521 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 555 bytes --]
next parent reply other threads:[~2014-03-29 20:00 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 [this message]
2014-03-29 20:05 ` Gregory Maxwell
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=53372605.7010405@gmail.com \
--to=justusranvier@gmail$(echo .)com \
--cc=Goss.Brian@mayo$(echo .)edu \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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