From: Aaron Voisine <voisine@gmail•com>
To: Luke Dashjr <luke@dashjr•org>
Cc: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] REQ BIP # / Discuss - Sweep incoming unconfirmed transactions with a bounty.
Date: Wed, 8 Jul 2015 23:17:03 -0700 [thread overview]
Message-ID: <CACq0ZD4PCSXMjZDXNS134ZWTSOaNGktKQd47q+6ncV-uRhS+YQ@mail.gmail.com> (raw)
In-Reply-To: <201507060424.57070.luke@dashjr.org>
[-- Attachment #1: Type: text/plain, Size: 866 bytes --]
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.
Aaron Voisine
co-founder and CEO
breadwallet.com
On Sun, Jul 5, 2015 at 9:24 PM, Luke Dashjr <luke@dashjr•org> wrote:
> On Monday, July 06, 2015 4:14:14 AM Dan Bryant wrote:
> > When I wrote the BIP proposal I was assuming (incorrectly) that CPFP TX
> > selection was already being done by miners,
>
> No, this is correct. It's just not included in the reference policy.
> Miners are not expected to use the reference policy as-is, and some of
> them do
> in fact use CPFP.
>
> Luke
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
[-- Attachment #2: Type: text/html, Size: 1698 bytes --]
next prev parent reply other threads:[~2015-07-09 6:17 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 [this message]
2015-07-09 6:22 ` Luke Dashjr
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=CACq0ZD4PCSXMjZDXNS134ZWTSOaNGktKQd47q+6ncV-uRhS+YQ@mail.gmail.com \
--to=voisine@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=luke@dashjr$(echo .)org \
/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