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

The discussion centers on the technical implementation and potential improvements in handling data within blockchain transactions, specifically addressing the efficiency and relevance of data commitment to blockchain consensus. The primary concern raised pertains to whether data that is not critical for consensus should impact the block weight, particularly when it is optional for nodes to retain this data. There is skepticism regarding the effectiveness of relying on node operators to actively participate in the relay of non-consensus-critical data, suggesting that the current expectations might be overly optimistic.

An alternative approach proposed involves using an overlay network where specific data transaction announcements are managed independently of the main blockchain protocol. This would involve Bitcoin Core acting as a client that identifies and processes OP_RETURN outputs with a designated prefix, signifying their role in data transactions. These transactions could then be handled by overlay network nodes, which would be responsible for retrieving, storing, and sharing the data. Additionally, a costing mechanism is suggested where data transactions would incur a burn of sats proportional to the byte size, potentially aligned with the transaction's feerate. This method aims to mitigate the load on the main blockchain while still facilitating data transactions efficiently.

The query seeks clarification on how the proposed system improves upon such an overlay network model. The underlying implication is that there may be more efficient or effective methods to manage data transactions without burdening the main blockchain or relying extensively on consensus mechanisms that may not be universally supported by all nodes.