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

The email raises concerns about the impracticality of expecting Bitcoin node operators to store non-monetary data that is unrelated to Bitcoin transactions without any incentives. The sender argues that there is no logical reason for node runners to store such data for free and that this expectation is unrealistic. Furthermore, they mention that if the goal is merely to have nodes commit to some data, this functionality already exists and can be easily achieved by embedding a hash into a tweaked taproot key or using an opreturn, which suggests that no new changes are necessary to accommodate this need. This stance underscores the sender's skepticism towards the proposal of storing non-essential data on the Bitcoin blockchain, emphasizing the existing capabilities that already support data commitments without requiring any modifications to the current system.