From: Luke Dashjr <luke@dashjr•org>
To: Aaron Voisine <voisine@gmail•com>
Cc: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] REQ BIP # / Discuss - Sweep incoming unconfirmed transactions with a bounty.
Date: Thu, 9 Jul 2015 06:22:42 +0000 [thread overview]
Message-ID: <201507090622.43214.luke@dashjr.org> (raw)
In-Reply-To: <CACq0ZD4PCSXMjZDXNS134ZWTSOaNGktKQd47q+6ncV-uRhS+YQ@mail.gmail.com>
On Thursday, July 09, 2015 6:17:03 AM Aaron Voisine wrote:
> Do you have any idea how much hashing power is using CPFP? It's a useful
> metric for wallet developers to know what sort of confirmation times they
> might be able to get when attempting to use it.
Not sure. At least 4% (Eligius)?
next prev parent reply other threads:[~2015-07-09 6:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-02 4:44 Dan Bryant
2015-07-02 4:52 ` Mark Friedenbach
2015-07-02 4:57 ` Matt Whitlock
2015-07-02 13:13 ` Tier Nolan
2015-07-03 21:56 ` Peter Todd
2015-07-06 4:14 ` Dan Bryant
2015-07-06 4:20 ` Micha Bailey
2015-07-06 4:24 ` Luke Dashjr
2015-07-09 6:17 ` Aaron Voisine
2015-07-09 6:22 ` Luke Dashjr [this message]
2015-07-09 7:19 ` Dan Bryant
2015-07-15 8:26 ` Dan Bryant
2015-08-26 15:28 ` Aaron Voisine
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=201507090622.43214.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=voisine@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