Consensus Cleanup BIP draft

Posted by Sjors Provoost

Mar 28, 2025/14:07 UTC

Segregated Witness (SegWit) significantly alters the structure and malleability of Bitcoin transactions compared to pre-SegWit transactions. The traditional 64-byte transactions, which were prevalent before the adoption of SegWit, inherently possess a malleability issue due to the lack of space for a signature within the scriptSig field. This limitation opens up these transactions to potential manipulation, as their identifiers can be altered without affecting the essence of the transaction itself.

SegWit addresses this critical vulnerability by changing how transaction data is stored and transmitted. Specifically, it introduces a separation where the witness data (including signatures) is detached from the main transaction block. This structural modification means that in SegWit transactions, the scriptSig field is left empty, and instead, the signature information is included in a new component called the witness. A common type of signature used in this context is the SIGHASH_ALL, which is stored within the witness area. This design not only solves the malleability issue but also paves the way for further advancements in the Bitcoin protocol by enabling more complex scripting capabilities and improving scalability.

Link to Raw Post
Bitcoin Logo

TLDR

Join Our Newsletter

We’ll email you summaries of the latest discussions from authoritative bitcoin sources, like bitcoin-dev, lightning-dev, and Delving Bitcoin.

Explore all Products

ChatBTC imageBitcoin searchBitcoin TranscriptsSaving SatoshiBitcoin Transcripts Review
Built with 🧡 by the Bitcoin Dev Project
View our public visitor count

We'd love to hear your feedback on this project?

Give Feedback