Archivist primary sources — 2026-05-09

Classification takeaway

Archivist is best cataloged as durability-focused decentralized storage infrastructure. The key reusable mechanism is the Decentralized Durability Engine (DDE): a storage-system model built from redundancy, auditing, repair, incentives, and dispersal, with Archivist implementing that model through erasure coding, ZK proofs of retrievability, slashable collateral, and lazy repair. The main analytical value is that it turns durability from a vague aspiration into an explicit design object and market/control surface.

Primary sources reviewed

1. Main site — https://archivist.storage/

   • Concisely states the protocol thesis: encrypted, erasure-coded, dispersed storage verified by ZK proofs.
   • Good first-pass signal that Archivist is positioning around durable sovereign storage rather than generic file sharing.

2. Docs overview — https://docs.archivist.storage/

   • Establishes the main documentation set and points directly to architecture, whitepaper, testnet, and API references.
   • Useful for confirming this is a live protocol / node surface rather than a paper-only idea.

3. What is Archivist? — https://docs.archivist.storage/learn/what-is-archivist

   • The clearest classification page.
   • Explicitly contrasts Archivist with BitTorrent and IPFS, emphasizing paid seeders, durability budgets, automatic repair, slashable collateral, and cryptographic audits.
   • Introduces the R.A.P.I.D. framing: redundancy, auditing, repair, incentives, dispersal.

4. Architecture docs — https://docs.archivist.storage/learn/architecture

   • The most important practical mechanism source.
   • Formalizes the DDE model, defines node roles, explains upload / storage / retrieval / repair flows, describes the proof system, and details the Ethereum marketplace parameters.
   • Particularly useful for identifying the real control surfaces: proof probability, collateral levels, slot counts, repair policy, and validator behavior.

5. Whitepaper — https://docs.archivist.storage/learn/whitepaper

   • The formal technical source.
   • Says Archivist uses erasure coding as part of both redundancy and storage proofs, coupled with zero-knowledge proofs and lazy repair, and includes a CTMC-based durability analysis.
   • Important because it elevates durability claims above homepage copy.

6. GitHub org and repos — https://github.com/durability-labs ; https://github.com/durability-labs/archivist-node ; https://github.com/durability-labs/archivist-docs

   • The GitHub org is verified for the archivist.storage domain.
   • Public node and docs repos make the system inspectable and operationally legible.

Whitepaper / technical-doc status

• The official whitepaper page has been saved locally as archivist-whitepaper.html.
• The docs stack is unusually good for current operational detail; the whitepaper is best for the formal design lens.

Why it stays in the active corpus

• Provides a clean mechanism lens for decentralized storage: not just who stores bytes, but how redundancy, auditing, repair, incentives, and dispersal interact.
• Useful comparison class for IPFS-like distribution, Filecoin-like storage markets, and other sovereignty / censorship-resistance storage claims.
• Helps reason about where trust really sits when durability guarantees depend on proof cadence, repair thresholds, collateral policy, and dispersal assumptions.