Verified storage

Any hosting service can say "your files are safe". With Zaryn you can check it yourself. ## Check your last push From your project: ```bash zev verify-storage ``` zev checks, step by step, using math rather than trust: 1. Zaryn regularly re-reads every stored object and checks it against its hash, then signs a **receipt** listing what it holds. 2. zev confirms every object of your last push is in that receipt. 3. zev checks the receipt's signature, and that the receipt is recorded in Zaryn's public **transparency log**, an append-only record that can't be quietly edited later. If any step fails, zev says which one. You can name a remote and branch: `zev verify-storage origin main`. The same check can run in your browser: in the repository's settings on Zaryn, use **Verify, without trusting Zaryn**. It runs zev's own verification code in the page, so the check doesn't depend on Zaryn's server telling the truth. ## Read part of a big file, checked ```bash zev fetch-range <object-hash> <start> <length> -o part.bin ``` downloads just that part of a large object, with a proof that it belongs to the object. Even a few bytes from a multi-gigabyte file are checked against the file's hash. ## How Zaryn keeps your data - Every object is stored under the hash of its content, so damage is always detectable. - A second copy is kept, and a daily check repairs either copy from the other. - Where the server offers it, a "resilient" storage policy (repository settings) also splits large files across several servers with erasure coding, so they survive losing some of those servers.