📅 Original date posted:2015-07-11
📝 Original message: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 at 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 at 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 at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150711/3180630b/attachment.html>;
Jeff Garzik [ARCHIVE] /
npub1kf…f3f58
2023-06-07 15:41:54
in reply to nevent1q…j5r2
Author Public Key
npub1kf0ppcjaguxekg24yx6smgxlu73qn0k8lm0t2wrqc0scpl7u3sgsmf3f58Seen on
wss://relay.noswhere.comPublished at
2023-06-07 15:41:54Event JSON
{
"id": "0ec461e5b44452d553be73ff9409953c426305c6caf8412fe3d62ddec1352fcb",
"pubkey": "b25e10e25d470d9b215521b50da0dfe7a209bec7fedeb53860c3e180ffdc8c11",
"created_at": 1686152514,
"kind": 1,
"tags": [
[
"e",
"bfd4714bb94a189208ff2ce68134800f654e20d12d58c5096abb21e63eaebf75",
"",
"root"
],
[
"e",
"c72417b2e99c50d2a77b2eecaf8093f0d9d28a521a23530c39240fc71c598f08",
"",
"reply"
],
[
"p",
"bbe41ddf98a712e588455717ec8f3f0893c530699af0a98cbe86c0af0138b25d"
]
],
"content": "📅 Original date posted:2015-07-11\n📝 Original message:It sounds like you are seeking transaction expiration from the mempool, not\nCPFP.\n\n\n\nOn Sat, Jul 11, 2015 at 4:30 PM, Dan Bryant \u003cdkbryant at gmail.com\u003e wrote:\n\n\u003e I think a compromise will be somewhere in the middle. I think most people\n\u003e would be OK with TXs that don't have enough fees for P2P transfer to stay\n\u003e in deadmans land. Most people are stuck in a situation where they payed\n\u003e enough to get it into (and keep it in) the pool, but not enough to get it\n\u003e out.\n\u003e\n\u003e If we could get CPFP that only worked on TXs that met the minimum\n\u003e threshold for peer propagation, then I think we would be in much better\n\u003e position to battle this spam flood.\n\u003e\n\u003e On Sat, Jul 11, 2015 at 3:28 PM, Micha Bailey \u003cmichabailey at gmail.com\u003e\n\u003e wrote:\n\u003e\n\u003e\u003e Right. The issue (AIUI) is that, right now, even though transactions are\n\u003e\u003e evaluated for inclusion as a group with CPFP, they're not yet evaluated for\n\u003e\u003e relaying as a unit, nor can they be, because the current p2p protocol\n\u003e\u003e doesn't have a way to send multiple transactions in a single protocol\n\u003e\u003e message to signify that they should be evaluated together.\n\u003e\u003e\n\u003e\u003e\n\u003e\n\u003e\n\u003e _______________________________________________\n\u003e bitcoin-dev mailing list\n\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\u003e\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150711/3180630b/attachment.html\u003e",
"sig": "d74a5418aac1c08f5a364528dadd4531661cc4fbf3f51e7aa2b16ece5cffdc39a4dbb2c8c260c460ea3e546a88931583700d11c8abc83bbb2e2585557d23c3e1"
}