how to disable segwit in my build?



Summary:

The conversation on the bitcoin-dev mailing list is about the implications of not upgrading to a SegWit compliant node. Hampus Sjöberg argues that not upgrading could save users bandwidth, but if the majority of the network adopts SegWit, a non-SegWit node would be downgraded to near-SPV node validation and may not be able to fully verify the ownership of bitcoins. Dan Libby notes that even if one does not upgrade to SegWit, there is no avoiding receiving UTXOs that were previously encumbered by a SegWit output. In response to a question from Dan, Hampus explains that all non-SegWit nodes will accept incoming transaction inputs, but will not perform any SegWit related validation, thus those inputs are not fully validated. However, old nodes make the transaction appear to always spendable for them, regardless of whether it really was spendable or not, in order to maintain backward compatibility. Old nodes do not understand the witness program encoded in a new format, so a number greater than zero will be put on the stack, which will be evaluated to true (because of >0) and counted as a valid spend. The links provided give more detailed explanations of this process.


Updated on: 2023-06-12T03:37:37.987229+00:00