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

The analysis of the economic incentives associated with data payloads and their corresponding processing work units (WU) reveals significant insights into cost efficiencies. For various payload sizes, measured in bytes, reductions in work units and percentage savings were observed when comparing standard data handling versus optimized processes involving both witness commit and reveal stages.

For a small payload of 256 bytes, approximately 865 WU (216 virtual bytes or vB) are typically required. However, with the implementation of witness commit and reveal techniques, this requirement increases slightly to around 1,210 WU (303 vB). Despite the higher initial work units, the net saving stands at about 345 WU, translating to an efficiency gain of approximately 28%.

As the payload size increases to 1 KB, the required work units for standard processing are roughly 1,633 WU (408 vB), which then rise to 1,996 WU (499 vB) with the additional processes. Here, the savings are around 363 WU or 18%, showcasing a decreasing trend in percentage savings as the payload size increases.

When examining even larger payloads, such as 10 KB, the work required for standard procedures is about 10,849 WU (2,712 vB), which marginally grows to 11,266 WU (2,817 vB) with the advanced handling methods. The resulting savings from these optimizations are approximately 417 WU or a mere 4%, indicating that the relative economic benefit diminishes with larger payload sizes. This pattern underscores the trade-offs between implementing more complex data handling mechanisms and the proportional savings achieved, particularly as the volume of data increases.