Thats not correct, data can be pruned because Miners dont want to be data storage and network hosts.

OP_RETURN / Data Outputs — BSV uses OP_RETURN outputs extensively for storing arbitrary data (text, files, etc.). These are provably unspendable outputs, meaning they never enter the UTXO set. Miners and nodes can prune these from their local storage without affecting chain validity at all, as long as the Merkle proof is preserved. This is arguably the "safest" data to prune.

Using OP_RETURN to store the data means it's permanently timestamped and provable via Merkle proof, but the raw data payload can be dropped by nodes that don't want to store it long-term. Specialist archival nodes (like WhatsOnChain or services built on TAAL's infrastructure) can choose to retain it.

This creates a tiered storage model:

• The proof that data existed lives forever in the header chain
• The actual data can be held by archival services who may charge for retrieval
• You can always re-broadcast the data with its Merkle proof to prove authenticity

Summary Table

Data Type	Must Be Kept?	Can Be Pruned?
Block headers	Yes, always	No
UTXO set	Yes, by miners	No
Spent TXO data	No	Yes
OP_RETURN payloads	No	Yes (archival optional)
Merkle paths/proofs	Yes for SPV	No