public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Tier Nolan <tier.nolan@gmail.com>
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Why not Child-Pays-For-Parent?
Date: Fri, 10 Jul 2015 20:39:14 +0100	[thread overview]
Message-ID: <CAE-z3OWMpCW51FjwT8409k_10Uj9Zq=H8AVUo5B6PfYBTQ_Axg@mail.gmail.com> (raw)
In-Reply-To: <CAPWm=eWH9rZpwJeK2tTdHH8+BWDU_Vam8oBtG0u49v2yZuYVfw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 418 bytes --]

It depends on what kind of inefficiency.  Inefficient could mean that it
uses a lot of CPU power.

If it gets a good solution rather than the best solution, it is still worth
having.

On Fri, Jul 10, 2015 at 6:51 PM, Alex Morcos <morcos@gmail.com> wrote:

> I think the biggest problem with merging CPFP right now is that at least
> in its current implementation it is not efficient enough in certain
> situations,.
>

[-- Attachment #2: Type: text/html, Size: 775 bytes --]

  reply	other threads:[~2015-07-10 19:39 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-10 16:09 [bitcoin-dev] Why not Child-Pays-For-Parent? Richard Moore
2015-07-10 16:13 ` Jeff Garzik
2015-07-10 16:25   ` Richard Moore
2015-07-10 16:26     ` Dan Bryant
2015-07-10 16:28 ` Tier Nolan
2015-07-10 16:31   ` Jeff Garzik
2015-07-10 17:02     ` Justus Ranvier
2015-07-10 17:16       ` Dan Bryant
2015-07-10 17:51       ` Alex Morcos
2015-07-10 19:39         ` Tier Nolan [this message]
2015-07-10 21:10           ` Luke Dashjr
2015-07-11 20:28             ` Micha Bailey
2015-07-11 21:30               ` Dan Bryant
2015-07-11 22:29                 ` Jeff Garzik
2015-07-12 10:18                   ` Matt Whitlock
2015-07-11 23:19                 ` Tier Nolan
2015-07-10 17:28     ` Tier Nolan

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='CAE-z3OWMpCW51FjwT8409k_10Uj9Zq=H8AVUo5B6PfYBTQ_Axg@mail.gmail.com' \
    --to=tier.nolan@gmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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