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

Full nodes are integral to blockchain technology as they maintain the complete consensus-relevant history, enabling them to validate the entirety of historical data independently and ascertain the current UTXO set without external assistance. The discussion highlights that full nodes do not inherently need segregated data (SegData) to function effectively. Implementing SegData storage would require additional resources, which seems unnecessary for a feature that is not essential to the core functionalities of full nodes.

The potential integration of SegData into full node operations is suggested to be more suitable as an opt-in feature rather than an opt-out. This approach is akin to other optional features like transaction indexing (txindex) or client-side block filters, which are not enabled by default but can be activated based on user preference. The general consensus in the community appears to lean towards minimal adoption of SegData retention among full nodes, reflecting its non-essential status and the resource implications associated with its maintenance.