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

Posted by MrHash

Jun 26, 2026/18:29 UTC

The discussion surrounding the proposal highlights several critical aspects of data management within blockchain networks, specifically concerning full nodes and their data retention policies. Full nodes are required to retain data within a specified retention window, identified here as 288 blocks. This requirement is crucial as the absence of this data cannot be tolerated by the network. The enforcement of data existence is comparable to the treatment of witness data, which is also strictly enforced at the point of inclusion in the network.

The proposal introduces an interesting concept where, unlike the current model that necessitates perpetual data retention, it allows for optional re-validation after the data has been initially confirmed and buried. This model aligns with the 'assumevalid' trust approach but with an additional flexibility for SegData nodes. These nodes have the option to discard certain entries post-validation, which are not required for future transaction validations or spending purposes.

Moreover, the proposed system emphasizes the non-requirement of consensus mechanisms needing the retained data post-download phase, enhancing efficiency particularly for nodes operating under bandwidth constraints. This is crucial because it addresses the issue of unnecessary data download and storage burdens on smaller nodes, especially those on metered connections or with limited disk space. The proposal suggests a method whereby nodes can skip historical data during initial block download (IBD) and only retain data pertinent to the defined window while still maintaining full validation capabilities and upholding the network’s monetary history.

Importantly, the proposal argues against the necessity of forcing every node to indefinitely retain arbitrary data, suggesting instead that allowing nodes to drop historical data could be a more pragmatic approach. This flexibility could potentially lead to better resource management across the network without compromising the integrity and functionality of the blockchain.

Link to Raw Post
Bitcoin Logo

TLDR

Join Our Newsletter

We’ll email you summaries of the latest discussions from high signal bitcoin sources, like bitcoin-dev, lightning-dev, and Delving Bitcoin.

Explore all Products

ChatBTC imageBitcoin searchBitcoin TranscriptsSaving SatoshiDecoding BitcoinWarnet
Built with 🧡 by the Bitcoin Dev Project
View our public visitor count

We'd love to hear your feedback on this project.

Give Feedback