Summary: Archivist is a durability-first storage network. The interesting part is repair, audits, and proof-backed loss management; it is not the branch anchor.
What it does:
Lets clients upload data, encrypt it locally, erasure-code it, and disperse it across independent storage providers
Uses zero-knowledge proofs to verify that providers still possess challenged data without requiring them to retransmit the full dataset
Posts storage requests on an Ethereum smart contract with duration, price, proof probability, and collateral parameters
Uses slashable collateral and validator monitoring to penalize providers who miss proofs or lose data
Repairs failed slots by reconstructing data from surviving erasure-coded fragments rather than assuming a human operator will re-seed content
Exposes a node binary, REST API, block-exchange layer, and testnet flow for providers and clients
Key claims:
The official site describes Archivist as durable decentralized storage with cryptographic durability guarantees, targeting nine to eleven nines of durability on commodity hardware
The What is Archivist? page frames it as BitTorrent with paid seeders and cryptographic durability guarantees, which is a strong classification clue because it distinguishes persistence/accountability from best-effort file sharing
The architecture docs formalize the system as a Decentralized Durability Engine with five required components: redundancy, auditing, repair, incentives, and dispersal
The whitepaper says modern decentralized storage networks often fail on durability, efficiency, or scalability of proofs, and proposes Archivist’s use of erasure coding, zero-knowledge proofs, and lazy repair as a different design center
The architecture docs show that storage contracts are parameterized by slots, proof frequency, duration, price, and collateral, which means the marketplace and audit cadence are part of the protocol’s real control surface
The system uses stochastic proof timing so providers cannot cheaply keep data only around expected audit windows
The verified durability-labs GitHub org, node repo, and docs repo support the view that Archivist is an actively built protocol surface rather than a manifesto-only project
Whitepaper: The main formal technical paper lives at the official whitepaper URL and has been saved locally as ../whitepapers/archivist-whitepaper.html. See also ../whitepapers/archivist-primary-sources-2026-05-09.md.