From: "'Antoine Poinsot' via Bitcoin Development Mailing List" <bitcoindev@googlegroups.com>
To: Jameson Lopp <jameson.lopp@gmail.com>
Cc: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] BIP 54 active on Bitcoin Inquisition
Date: Wed, 11 Mar 2026 15:02:21 +0000 [thread overview]
Message-ID: <273ith9pPyipCI5hjV6ETFBzFhM4xFN8ptEFK8zc5N-jxGwOBvEn5r9Bt2c9p0A-6-3Bs53gONglzo1QfI4LCIOwkJgR9PWT4iQT_Wbpllo=@protonmail.com> (raw)
In-Reply-To: <CADL_X_ewFMqLuv7MVfWCZf3QhKezW9xiS19xWdROjtoT9dmU7w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3837 bytes --]
I share this concern, which is why i only shared details about this in the (semi-)private Delving thread to this effect: https://delvingbitcoin.org/t/worst-block-validation-time-inquiry/711.
The testing for quality assurance has already been performed as part of the investigation into the various techniques and possible mitigations. Additional testing is always valuable, but the primary goal of a public demonstration for this would be to help build consensus.
It's a fine line to tread, because on the one hand you do not want to give away the details of how to optimise the attack (whether for maximum profit or for maximum impact), but on the other hand i do think it's necessary to provide some amount of publicly verifiable information to support a soft fork activation proposal.
My approach so far has been to share all details in the semi-private Delving thread that is accessible to a number of experts who would be able to figure it out on their own anyway, and to share a demonstration of an expensive-but-far-from-worst block publicly. This allows anyone to check for themselves that it is indeed possible to craft some slow blocks, and they can refer to an expert to confirm that it can be made much worse. Of course, i remain open to feedback.
On Wednesday, February 25th, 2026 at 12:03 PM, Jameson Lopp <jameson.lopp@gmail.com> wrote:
> 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](mailto:bitcoindev%2Bunsubscribe@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.
--
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/273ith9pPyipCI5hjV6ETFBzFhM4xFN8ptEFK8zc5N-jxGwOBvEn5r9Bt2c9p0A-6-3Bs53gONglzo1QfI4LCIOwkJgR9PWT4iQT_Wbpllo%3D%40protonmail.com.
[-- Attachment #2: Type: text/html, Size: 6038 bytes --]
next prev parent reply other threads:[~2026-03-11 15:27 UTC|newest]
Thread overview: 4+ 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
2026-03-11 15:02 ` 'Antoine Poinsot' via Bitcoin Development Mailing List [this message]
[not found] ` <Gehatc25PHdVzbYtnOGCDUsV7-ibRuP7gls32r4gekZGGjZI0o22lUvMhK27lv4B7_Cgb9MZA4-KmkI5wM_GL9GHWPaGA4sPNR5Mn7Kaz2c=@protonmail.com>
2026-03-31 3:09 ` Antoine Riard
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='273ith9pPyipCI5hjV6ETFBzFhM4xFN8ptEFK8zc5N-jxGwOBvEn5r9Bt2c9p0A-6-3Bs53gONglzo1QfI4LCIOwkJgR9PWT4iQT_Wbpllo=@protonmail.com' \
--to=bitcoindev@googlegroups.com \
--cc=darosior@protonmail.com \
--cc=jameson.lopp@gmail.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