From: Mark Friedenbach <mark@monetize•io>
To: Justus Ranvier <justusranvier@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Best practices for dust remining
Date: Sat, 29 Mar 2014 13:10:00 -0700 [thread overview]
Message-ID: <CACh7GpE8kEaT5UZtx4eACM1W0Y_x1=ozasaXktpxBtEWfBuy3A@mail.gmail.com> (raw)
In-Reply-To: <53372243.20106@silicon>
[-- Attachment #1: Type: text/plain, Size: 926 bytes --]
NONE|ANYONECANPAY. This is what dust-be-gone does.
On Mar 29, 2014 12:46 PM, "Justus Ranvier" <justusranvier@gmail•com> wrote:
> Suppose am m-of-n multisig wallet receives a bunch of dust deposits due
> to somebody advertising the Olympics, or any other reason, and the users
> of the wallet don't want the few satoshis involved.
>
> What is the best way to allow all these dust outputs to be re-mined in
> order to clean up the utxo set, keeping in mind the scripts may include
> large values of n?
>
> --
> Support online privacy by using email encryption whenever possible.
> Learn how here: http://www.youtube.com/watch?v=bakOKJFtB-k
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
[-- Attachment #2: Type: text/html, Size: 1463 bytes --]
prev parent reply other threads:[~2014-03-29 20:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-29 19:42 Justus Ranvier
2014-03-29 20:10 ` Mark Friedenbach [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='CACh7GpE8kEaT5UZtx4eACM1W0Y_x1=ozasaXktpxBtEWfBuy3A@mail.gmail.com' \
--to=mark@monetize$(echo .)io \
--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