From: Sjors Provoost <sjors@sprovoost•nl>
To: Chris Stewart <stewart.chris1234@gmail•com>
Cc: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>,
jeremy <jeremy.l.rubin@gmail•com>
Subject: Re: [bitcoindev] Consensus Cleanup BIP draft
Date: Fri, 28 Mar 2025 15:07:17 +0100 [thread overview]
Message-ID: <8DCD4B60-F1BA-46C4-8594-5CAFB9540128@sprovoost.nl> (raw)
In-Reply-To: <CAGL6+mHuVgWc9ATjRnBz+b7SJyz84La8q9jeM=yiw-Anh=a3ag@mail.gmail.com>
Hi Chris,
Sorry for the confusion. I meant SegWit.
I believe that 64 byte pre-SegWit transactions are always malleable, because there's no space for a signature in the scriptSig. But with SegWit the scriptSig is empty, there could a SIGHASH_ALL signature in the witness.
- Sjors
> Op 28 mrt 2025, om 14:54 heeft Chris Stewart <stewart.chris1234@gmail•com> het volgende geschreven:
>
> Hi Sjors,
> Sorry to be a bit pedantic here, but I think this distinction is important. Are you referring to a pre-SegWit transaction or a SegWit transaction? It’s crucial to analyze these separately, as SegWit was designed to solve transaction malleability, which affects how we assess backward compatibility concerns when disallowing 64-byte transactions.
> In the future, it would be helpful to explicitly specify “pre-segwit” or “segwit” when discussing potential transactions. In my draft BIP, I differentiate between these two types when evaluating the backward compatibility risks of disallowing 64-byte transactions. Additionally, as I mentioned earlier (and as I believe Jeremy has also raised concerns about), there are potential future compatibility issues with segwit transactions.
> I'll take a closer look at the Stack Exchange examples and share my thoughts there when I have a bit of time.
>
--
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/8DCD4B60-F1BA-46C4-8594-5CAFB9540128%40sprovoost.nl.
next prev parent reply other threads:[~2025-03-28 14:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-26 17:14 'Antoine Poinsot' via Bitcoin Development Mailing List
2025-03-27 10:46 ` Chris Stewart
2025-03-27 17:54 ` /dev /fd0
2025-03-27 19:05 ` 'Antoine Poinsot' via Bitcoin Development Mailing List
2025-03-27 20:45 ` jeremy
2025-03-27 21:38 ` 'Antoine Poinsot' via Bitcoin Development Mailing List
2025-03-28 9:23 ` Sjors Provoost
2025-03-28 11:02 ` Chris Stewart
2025-03-28 12:48 ` Sjors Provoost
2025-03-28 13:54 ` Chris Stewart
2025-03-28 14:07 ` Sjors Provoost [this message]
2025-03-28 19:53 ` eric
2025-03-29 11:02 ` Sjors Provoost
2025-03-31 11:00 ` Anthony Towns
2025-03-31 15:29 ` 'Antoine Poinsot' via Bitcoin Development Mailing List
2025-03-31 20:09 ` eric
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=8DCD4B60-F1BA-46C4-8594-5CAFB9540128@sprovoost.nl \
--to=sjors@sprovoost$(echo .)nl \
--cc=bitcoindev@googlegroups.com \
--cc=jeremy.l.rubin@gmail$(echo .)com \
--cc=stewart.chris1234@gmail$(echo .)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