Thinking of this for file storage, for a decentralised and trust-minimised approach, with redundancy and privacy: - Merkle trees (or something similar) to represent the stored files, so that large files and directory structures can be stored, and Merkle proofs so that service providers can easily prove that they have every (part of) your file. If a provider loses your data, you can prove it publicly. With the right design of this, we can support making lots of small changes very efficiently and updating the root quickly - encrypt the data - Redundancy. Store your data with multiple providers, with a watchtower to test providers regularly (using the Merkle proofs) to identify gaps - as well as encrypting the data, also encrypt the data a second time with a different key for each provider. This forces providers to really store your data, instead of just 'proxying' another provider's copy of your data - Your watchtower(s) doesn't need to know the main encryption key. They just need to know your secondary - per-provider - keys. This gives your watchtower enough information to quickly copy your data to other service providers, always ensuring that you have at least N copies of each fragment of data - the providers sign the Merkle root, giving you a promise to store that data. Making a small change to a huge file system is an efficient process. When you change some data, you sign an event which releases the old root - paid with bitcoin of course. If making many small changes, a system that allows high-frequency micropayments (e.g. Cashu Spilman channels) would help to pay on demand Let's make a simple web-based client for this, perhaps a PWA that uses Nostr to store state