From: Micha Bailey <michabailey@gmail•com>
To: Luke Dashjr <luke@dashjr•org>
Cc: "bitcoin-dev@lists•linuxfoundation.org"
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Why not Child-Pays-For-Parent?
Date: Sat, 11 Jul 2015 23:28:27 +0300 [thread overview]
Message-ID: <CAAmoQf1B1nFfS6ZXOkvoJGTaPpbN_NDwOcwCw30MSbRwooSh4Q@mail.gmail.com> (raw)
In-Reply-To: <201507102110.33706.luke@dashjr.org>
[-- Attachment #1: Type: text/plain, Size: 894 bytes --]
Right. The issue (AIUI) is that, right now, even though transactions are
evaluated for inclusion as a group with CPFP, they're not yet evaluated for
relaying as a unit, nor can they be, because the current p2p protocol
doesn't have a way to send multiple transactions in a single protocol
message to signify that they should be evaluated together.
On Saturday, July 11, 2015, Luke Dashjr <luke@dashjr•org> wrote:
> AFAIK the only thing holding it up is lack of unit tests. If anyone would
> like
> to implement those, I expect it'd be merged fairly soon. Then the problem
> is,
> as Jeff mentioned, getting the parent transactions relayed despite failing
> relay policy on their own.
>
> Luke
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org <javascript:;>
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
[-- Attachment #2: Type: text/html, Size: 1303 bytes --]
next prev parent reply other threads:[~2015-07-11 20:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-10 16:09 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
2015-07-10 21:10 ` Luke Dashjr
2015-07-11 20:28 ` Micha Bailey [this message]
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=CAAmoQf1B1nFfS6ZXOkvoJGTaPpbN_NDwOcwCw30MSbRwooSh4Q@mail.gmail.com \
--to=michabailey@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