From: Luke Dashjr <luke@dashjr•org>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] Why not Child-Pays-For-Parent?
Date: Fri, 10 Jul 2015 21:10:32 +0000 [thread overview]
Message-ID: <201507102110.33706.luke@dashjr.org> (raw)
In-Reply-To: <CAE-z3OWMpCW51FjwT8409k_10Uj9Zq=H8AVUo5B6PfYBTQ_Axg@mail.gmail.com>
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
next prev parent reply other threads:[~2015-07-10 21:11 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 [this message]
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=201507102110.33706.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.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