Posted by Sjors Provoost
Jan 14, 2026/10:15 UTC
The discussion revolves around the serialization of transactions in Bitcoin, specifically under the guidelines of BIP 141. Antoine Poinsot points out a clarification regarding how transactions are serialized within a block, emphasizing that the process diverges from when witness data is included. This distinction is crucial because, in the context of BIP 141, the witness data is segregated, which means it's not included in the same way as traditional transaction data during serialization in a block.
Further elaboration on the topic by Sjors highlights the methodology for integrating SegWit transactions into the blockchain without disrupting the current system. This is achieved by incorporating the Merkle root into the coinbase transaction, a strategy designed to maintain compatibility with the existing blockchain infrastructure while introducing improvements. The approach ensures that as long as miners do not modify the SegWit OP_RETURN, which is a commitment to the coinbase witness, they can continue using the legacy transaction serialization method. This technique underscores the forward-thinking design of SegWit, allowing for future hard forks to place the witness tree in its own branch, thereby facilitating an evolution of the blockchain's structure without necessitating immediate, widespread changes to the network's operation.
Thread Summary (14 replies)
Dec 30 - Feb 12, 2026
15 messages • 14 replies
TLDR
We’ll email you summaries of the latest discussions from high signal bitcoin sources, like bitcoin-dev, lightning-dev, and Delving Bitcoin.
We'd love to hear your feedback on this project.
Give Feedback