From: Anthony Towns <aj@erisian•com.au>
To: Gloria Zhao <gloriajzhao@gmail•com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Package Relay Proposal
Date: Tue, 24 May 2022 15:48:02 -0400 [thread overview]
Message-ID: <2B3D1901-901C-4000-A2B9-F6857FCE2847@erisian.com.au> (raw)
In-Reply-To: <CAFXO6=KXToP2MFWQ1JVKX6jV++utw8E4Z13T4cH+mfgtyeUx_A@mail.gmail.com>
On 23 May 2022 9:13:43 pm GMT-04:00, Gloria Zhao <gloriajzhao@gmail•com> wrote:
>> If you're asking for the package for "D", would a response telling you:
>> txid_D (500 sat, 100vB)
>> txid_A (0 sat, 100vB)
>> txid_B (2000 sat, 100 vB)
>> be better, in that case? Then the receiver can maybe do the logic
>> themselves to figure out that they already have A in their mempool
>> so it's fine, or not?
>Right, I also considered giving the fees and sizes of each transaction in
>the package in “pckginfo1”. But I don’t think that information provides
>additional meaning unless you know the exact topology, i.e. also know if
>the parents have dependency relationships between them. For instance, in
>the {A, B, D} package there, even if you have the information listed, your
>decision should be different depending on whether B spends from A.
I don't think that's true? We already know D is above our fee floor so if B with A is also above the floor, we want them all, but also if B isn't above the floor, but all of them combined are, then we also do?
If you've got (A,B,C,X) where B spends A and X spends A,B,C where X+C is below fee floor while A+B and A+B+C+X are above fee floor you have the problem though.
Is it plausible to add the graph in?
Cheers,
aj
--
Sent from my phone.
next prev parent reply other threads:[~2022-05-24 19:48 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-17 16:01 Gloria Zhao
2022-05-17 17:56 ` Greg Sanders
2022-05-17 20:45 ` Gloria Zhao
2022-05-18 0:35 ` Anthony Towns
2022-05-18 18:40 ` Gloria Zhao
2022-05-23 21:34 ` Anthony Towns
2022-05-24 1:13 ` Gloria Zhao
2022-05-24 19:48 ` Anthony Towns [this message]
2022-05-24 21:05 ` Gloria Zhao
2022-05-24 23:43 ` Eric Voskuil
2022-05-25 18:55 ` Anthony Towns
2022-05-25 20:52 ` eric
2022-05-26 2:59 ` eric
2022-06-07 17:44 ` Gloria Zhao
2022-06-08 15:59 ` Suhas Daftuar
2022-06-14 9:59 ` Gloria Zhao
2022-05-28 1:54 ` Gloria Zhao
2022-06-17 20:08 ` Antoine Riard
2022-11-01 18:03 ` Gloria Zhao
2023-05-10 15:12 Tom Trevethan
2023-05-10 15:42 ` Greg Sanders
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=2B3D1901-901C-4000-A2B9-F6857FCE2847@erisian.com.au \
--to=aj@erisian$(echo .)com.au \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=gloriajzhao@gmail$(echo .)com \
/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