From: Peter Todd <pete@petertodd•org>
To: ArmchairCryptologist <ArmchairCryptologist@protonmail•com>
Cc: bitcoindev@googlegroups.com
Subject: Re: [bitcoindev] Transaction expiration should be based on the most recent transaction in a group, not the first
Date: Tue, 4 Feb 2025 21:39:34 +0000 [thread overview]
Message-ID: <Z6KJFvikr27e7Igk@petertodd.org> (raw)
In-Reply-To: <rqLkuDekAhYC8mO9BMrqXGQjv-Oq1a1jA2EDLdiohq9kHIQpE-MpzqFjqY15Cc5flU_GUrE7NoSxB_4wgkQg8Mv8IQdtzlXLtuxK76n7YRQ=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 2000 bytes --]
On Fri, Jan 31, 2025 at 12:02:56PM +0000, 'ArmchairCryptologist' via Bitcoin Development Mailing List wrote:
> Is expiration-based mempool eviction necessary or even desirable anymore? I'm consistently seeing unconfirmed transactions from months ago being rebroadcast and (now that the mempool is draining) eventually confirming, without anyone even trying to exploit anything. So from what I can tell, the only thing this really accomplishes is wasting CPU cycles and bandwidth evicting and later re-accepting the transactions in question.
All it would take is one person running a rebroadcasting service to make
mempool eviction useless except in the rare case that a soft-fork of
standard transactions has happened. Although even then, arguably you are
better off not wasting bandwidth re-accepting those transactions over
and over again.
> You were never able to rely on unconfirmed transactions ever going away without double-spending one of the inputs in the first place, and full-RBF is even a thing now, so this will always be possible.
Agreed.
> The mempool is capped by size anyway, so while I may be missing something, I cannot honestly see any good reasons to keep this mechanism at all, especially if it can be used as a vector for attacks.
>
> The only drawback I can think of is that abandontransaction currently does not work if a transaction is in the mempool, but it would probably be better to improve it so it actually evicts the transaction from the mempool of the local node if necessary.
Agreed. I've run into this problem before myself.
--
https://petertodd.org 'peter'[:-1]@petertodd.org
--
You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bitcoindev+unsubscribe@googlegroups•com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/Z6KJFvikr27e7Igk%40petertodd.org.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2025-02-04 21:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-28 22:25 Peter Todd
2025-01-31 12:02 ` 'ArmchairCryptologist' via Bitcoin Development Mailing List
2025-02-04 21:39 ` Peter Todd [this message]
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=Z6KJFvikr27e7Igk@petertodd.org \
--to=pete@petertodd$(echo .)org \
--cc=ArmchairCryptologist@protonmail$(echo .)com \
--cc=bitcoindev@googlegroups.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