public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed

From: darosior <darosior@protonmail•com>
To: Gloria Zhao <gloriajzhao@gmail•com>,
	Bitcoin Protocol Discussion
	<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Proposal: Package Mempool Accept and Package RBF
Date: Thu, 14 Oct 2021 10:48:55 +0000	[thread overview]
Message-ID: <UuYb6dx_tR9juBtZyEGQC3uQLMkTC0pBAFDWN_kD65OBLUOdk-7C8kIRbQljb3TbuJvud2l084lr8GYtW23AzqYCyPVlHqt-fbI93XLo22A=@protonmail.com> (raw)
In-Reply-To: <CAFXO6=Lvcr7Pwn_ZD1CZohYUFKY-cC5sGRxdTOiP2MgnTvFnYA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1609 bytes --]

Hi Gloria,

> In summary, it seems that the decisions that might still need attention/input from devs on this mailing list are:
> 1. Whether we should start with multiple-parent-1-child or 1-parent-1-child.
> 2. Whether it's ok to require that the child not have conflicts with mempool transactions.

I would like to point out that package relay is not only useful in Lightning's adversarial scenarii but also for a better user experience of CPFP.
Take for instance a wallet managing coins it can only spend using pre-signed transactions. It may batch these coins into a single transaction, but only after broadcasting the pre-signed tx for each of these coins.
So for a 3 utxos it'd be:
coin1 -----> pres. tx1 ----- |
coin2 -----> pres. tx2 ----- | - - - spending transaction
coin3 -----> pres. tx3 ----- |

Now all these pre-signed transactions are pre-signed with a fixed feerate, which might be below the mempool minimum fee at the time of broadcast.
This is a usecase for multiple-parents-1-child packages. This is also something we do for Revault: you have pre-signed Unvault transactions, each have a CPFP output [0]. Since their confirmation is not security critical, you'd really want to batch the child-fee-paying tx.

Regarding 2. i did not come up with a reason for dropping this rule (yet?) since if you need to replace the child you can use individual submission, and if you need to replace the parent the child itself does not conflict anymore.

Thanks for the effort put into requesting feedback,
Antoine

[0] https://github.com/revault/practical-revault/blob/master/transactions.md#unvault_tx

[-- Attachment #2: Type: text/html, Size: 2155 bytes --]

next prev parent reply	other threads:[~2021-10-14 10:49 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-16  7:51 Gloria Zhao
2021-09-19 23:16 ` Antoine Riard
2021-09-20 15:10   ` Gloria Zhao
2021-09-23  4:29     ` Antoine Riard
2021-09-23 15:36       ` Gloria Zhao
2021-09-26 21:10         ` Antoine Riard
2021-09-27  7:15           ` Bastien TEINTURIER
2021-09-28 22:59             ` Antoine Riard
2021-09-29 11:56               ` Gloria Zhao
2021-10-14 10:48         ` darosior [this message]
2021-09-20  9:19 ` Bastien TEINTURIER
2021-09-21 11:18   ` Gloria Zhao
2021-09-21 15:18     ` Bastien TEINTURIER
2021-09-21 16:42       ` Gloria Zhao
2021-09-22  7:10         ` Bastien TEINTURIER
2021-09-22 13:26           ` Gloria Zhao

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='UuYb6dx_tR9juBtZyEGQC3uQLMkTC0pBAFDWN_kD65OBLUOdk-7C8kIRbQljb3TbuJvud2l084lr8GYtW23AzqYCyPVlHqt-fbI93XLo22A=@protonmail.com' \
    --to=darosior@protonmail$(echo .)com \
    --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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox