From: Tom Harding <tomh@thinlink•com>
To: vjudeu@gazeta•pl
Cc: bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] tx max fee
Date: Thu, 11 May 2023 17:06:51 -0700 [thread overview]
Message-ID: <afed64d7-ae68-0332-f2ce-a499586af990@thinlink.com> (raw)
In-Reply-To: <171698970-6184d5f773dee0589bf3373c44b9f21f@pmq2v.m5r2.onet>
On 5/11/23 04:02, vjudeu via bitcoin-dev wrote:
> Every transaction paying "fee > sum" can be replaced by N transactions
> paying "fee <= sum", where the sum of all fees will be the same.
These N transactions will generally have a lower feerate than the
original, and the lowest feerate of the N could be drastically lower
than the original.
As a group, in the current environment (for example), they could take
days or weeks longer to be mined than the original.
next prev parent reply other threads:[~2023-05-12 0:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-10 16:19 vjudeu
2023-05-10 17:42 ` Erik Aronesty
2023-05-11 11:02 ` vjudeu
2023-05-11 12:32 ` Kalle Rosenbaum
2023-05-11 15:20 ` Andrew Baine
2023-05-12 0:06 ` Tom Harding [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-05-07 23:59 Erik Aronesty
2023-05-08 23:57 ` Peter Todd
2023-05-09 0:04 ` Erik Aronesty
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=afed64d7-ae68-0332-f2ce-a499586af990@thinlink.com \
--to=tomh@thinlink$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=vjudeu@gazeta$(echo .)pl \
/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