From: Jeff Garzik <jgarzik@gmail•com>
To: DKBryant@gmail•com
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 17:29:07 -0500 [thread overview]
Message-ID: <CADm_Wcaed61oWMGu_FVCeRUWOS6jfFvGwNGEwh9GymfrqgtQKQ@mail.gmail.com> (raw)
In-Reply-To: <CAAUFj12JC1e7wY1M-_U_Kh5wQv8V4X0SeGGtONn7m8PcOEhp_Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1295 bytes --]
It sounds like you are seeking transaction expiration from the mempool, not
CPFP.
On Sat, Jul 11, 2015 at 4:30 PM, Dan Bryant <dkbryant@gmail•com> wrote:
> I think a compromise will be somewhere in the middle. I think most people
> would be OK with TXs that don't have enough fees for P2P transfer to stay
> in deadmans land. Most people are stuck in a situation where they payed
> enough to get it into (and keep it in) the pool, but not enough to get it
> out.
>
> If we could get CPFP that only worked on TXs that met the minimum
> threshold for peer propagation, then I think we would be in much better
> position to battle this spam flood.
>
> On Sat, Jul 11, 2015 at 3:28 PM, Micha Bailey <michabailey@gmail•com>
> wrote:
>
>> 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.
>>
>>
>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
>
[-- Attachment #2: Type: text/html, Size: 2221 bytes --]
next prev parent reply other threads:[~2015-07-11 22:29 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
2015-07-11 21:30 ` Dan Bryant
2015-07-11 22:29 ` Jeff Garzik [this message]
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=CADm_Wcaed61oWMGu_FVCeRUWOS6jfFvGwNGEwh9GymfrqgtQKQ@mail.gmail.com \
--to=jgarzik@gmail$(echo .)com \
--cc=DKBryant@gmail$(echo .)com \
--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