From: Tier Nolan <tier.nolan@gmail•com>
Cc: "bitcoin-dev@lists•linuxfoundation.org"
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Why not Child-Pays-For-Parent?
Date: Sun, 12 Jul 2015 00:19:14 +0100 [thread overview]
Message-ID: <CAE-z3OVLF5whUL_HoP3i5B5mxB_KztBLJSB1dJ=dQ9+UDg55hg@mail.gmail.com> (raw)
In-Reply-To: <CAAUFj12JC1e7wY1M-_U_Kh5wQv8V4X0SeGGtONn7m8PcOEhp_Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1189 bytes --]
On Sat, Jul 11, 2015 at 10: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.
>
Agreed. A lot of the functionality could be achieved by a system that
works in most cases. Even if 100 transaction chains aren't supported, 3-5
transaction chains would give a significant fraction of the desired
functionality.
At the moment, a transaction is only added into the memory pool if it meets
the relay threshold and spends transactions that are either in the memory
pool or in a block.
There is an orphan pool that can store up to 100 orphans.
The same could be done for child pays for parent. A node could remember
the last 100 transactions (up to 5000 bytes) that were rejected from the
memory pool due to insufficient relay fees.
This allows nodes to send a chain of transactions in a row. If the child
is sent last, then the parent(s) will be in the unrelayed transaction pool.
[-- Attachment #2: Type: text/html, Size: 1639 bytes --]
next prev parent reply other threads:[~2015-07-11 23:19 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
2015-07-12 10:18 ` Matt Whitlock
2015-07-11 23:19 ` Tier Nolan [this message]
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-z3OVLF5whUL_HoP3i5B5mxB_KztBLJSB1dJ=dQ9+UDg55hg@mail.gmail.com' \
--to=tier.nolan@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