From: Murch <murch@murch•one>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] One-Shot Replace-By-Fee-Rate
Date: Thu, 25 Jan 2024 16:25:28 -0500 [thread overview]
Message-ID: <3384566b-8c6d-4d8c-91b8-a45f17aaec68@murch.one> (raw)
In-Reply-To: <Za7xkUsoeACMv6Fw@petertodd.org>
Hi Peter,
On 1/22/24 17:52, Peter Todd wrote:
> An even simpler fix would be to just require that all unconfirmed inputs
> in a replacement come from the *same* replaced transaction. That would
> make certain rare, but economically viable, replacements infeasible. But
> it would definitely fix the issue.
The replacements spend at most a single unconfirmed input in my infinite
relay cycle example.
Murch
next prev parent reply other threads:[~2024-01-25 21:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-18 18:23 Peter Todd
2024-01-22 18:12 ` Murch
2024-01-22 22:52 ` Peter Todd
2024-01-24 4:44 ` Peter Todd
2024-01-25 21:25 ` Murch [this message]
2024-01-27 7:19 ` Peter Todd
2024-01-28 17:27 ` Murch
2024-01-31 8:40 ` Peter Todd
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=3384566b-8c6d-4d8c-91b8-a45f17aaec68@murch.one \
--to=murch@murch$(echo .)one \
--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