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

The discussion revolves around the resource implications of full nodes processing at the tip, which involves validating 288 blocks. This process consumes CPU cycles primarily for validating the hash of each block entry. Despite this cost, the implementation of SegData is designed to be resource-efficient as it does not incur additional network or storage costs—data is moved rather than added.

For smaller nodes or those validating data beyond the typical retention window, there is an option to opt out, potentially saving on bandwidth, CPU, and storage resources. This feature highlights a strategic approach to resource management in network operations, where opting out of certain functionalities can lead to significant reductions in resource needs.

The core argument presented is that SegData, when opted out of by smaller nodes or nodes beyond the retention window, results in a net decrease in resource usage. This approach not only addresses concerns about resource consumption but also positions SegData as a solution that is overall beneficial in terms of network and storage requirements.