[BIP Draft] Segregated Data: a prunable, script-isolated block region for data carriage

The discussion centers on the inefficacies of a proposed mining strategy where miners include transactions but withhold certain data, specifically SegData. This approach allows miners to collect transaction fees and ensures the block propagates smoothly among nodes that have not been upgraded, all while using less bandwidth. However, this method presents significant drawbacks in terms of data visibility and availability. Since the complete SegData is not propagated with the block, only other nodes might transmit the data for their specific transactions. This results in reduced visibility and availability of SegData across the network.

Moreover, due to these limitations, there is an incentive for data embedders to opt for witness data over SegData. Witness data, unlike SegData, guarantees data availability at the same cost, making it a more attractive option for ensuring information integrity and accessibility within the blockchain. The critique highlights that the current proposal does not effectively address or resolve core issues for any stakeholders involved, questioning the overall utility and problem-solving capability of the suggested strategy. This raises concerns about the viability of implementing such a method without substantial modifications to address these critical flaws.