From: Jameson Lopp <jameson.lopp@gmail.com>
To: Antoine Poinsot <darosior@protonmail.com>
Cc: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] BIP 54 active on Bitcoin Inquisition
Date: Wed, 25 Feb 2026 11:49:39 -0500 [thread overview]
Message-ID: <CADL_X_ewFMqLuv7MVfWCZf3QhKezW9xiS19xWdROjtoT9dmU7w@mail.gmail.com> (raw)
In-Reply-To: <wJZkcSEOQD5Z8rsel8TJCSkUJiwn7YepjyOfSDHKt3P_4Fvh9MFu_oiva3G6C-Q_1CmRTCj6lqmVm6ZeZG8WbdVrCo4IZUFg3VazRdJ48AQ=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 1961 bytes --]
The main concern I'd have is whether or not doing so would leak more
information to the world about how to conduct such an attack on mainnet. It
may be prudent to perform such testing privately.
On Fri, Feb 13, 2026 at 5:28 PM 'Antoine Poinsot' via Bitcoin Development
Mailing List <bitcoindev@googlegroups.com> wrote:
> Hi everyone,
>
> Bitcoin Inquisition 29.2 was released last week with support for BIP 54
> (Consensus Cleanup) [0]. BIP
> 54 is now active on Inquisition since block 291168.
>
> By virtue of being a bugfix soft fork rather than introducing new
> features, there is fewer avenues
> for testing on the public Signet network. Perhaps we could create a Signet
> block that is slow but
> not quite as bad as the worst case, and share it here to demonstrate it is
> now invalid on
> Inquisition?
>
> At any rate, please let us know if you find anything in testing whether it
> is on the public Signet
> network, in private ones, or however else.
>
> Best,
> Antoine Poinsot
>
> [0] https://delvingbitcoin.org/t/bitcoin-inqusition-29-2/2236
>
> --
> 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/wJZkcSEOQD5Z8rsel8TJCSkUJiwn7YepjyOfSDHKt3P_4Fvh9MFu_oiva3G6C-Q_1CmRTCj6lqmVm6ZeZG8WbdVrCo4IZUFg3VazRdJ48AQ%3D%40protonmail.com
> .
>
--
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/CADL_X_ewFMqLuv7MVfWCZf3QhKezW9xiS19xWdROjtoT9dmU7w%40mail.gmail.com.
[-- Attachment #2: Type: text/html, Size: 2978 bytes --]
prev parent reply other threads:[~2026-02-25 17:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-13 22:27 'Antoine Poinsot' via Bitcoin Development Mailing List
2026-02-25 16:49 ` Jameson Lopp [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=CADL_X_ewFMqLuv7MVfWCZf3QhKezW9xiS19xWdROjtoT9dmU7w@mail.gmail.com \
--to=jameson.lopp@gmail.com \
--cc=bitcoindev@googlegroups.com \
--cc=darosior@protonmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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