Summary: Codex is a durability engine built around erasure coding, proofs, and market-matched persistence. Useful, but still a secondary branch note next to IPFS, Filecoin, and Arweave.
What it does:
Lets users run Codex nodes that join a peer-to-peer network through bootstrap discovery and expose a REST API for uploads, retrievals, and diagnostics
Supports an altruistic sharing mode where files are chunked into 64 KB blocks, organized into Merkle trees, and retrieved from the network via manifests and CIDs
Supports a persistence mode where users post storage requests and providers automatically opt in when a request matches their configured price, duration, and collateral limits
Applies erasure coding to create parity blocks and distribute protected data across multiple storage nodes rather than relying on simple replication
Builds verifiable manifests that break blocks into smaller cells, hash them with Poseidon2, and aggregate slot roots into a verification root used for storage proofs
Ships CLI, installer, web app, and API surfaces for developers and node operators, with current public usage centered on testnet participation
Key claims:
Official Codex materials consistently describe the project as a Decentralised Durability Engine (DDE), which is the cleanest classification signal because it centers durability rather than generic cloud-storage replacement
The protocol-breakdown article says storage providers do not manually bid for contracts; instead they monitor the chain for requests matching their local rules, which means market structure and provider-side configuration are part of the real control surface
The same article distinguishes an altruistic CID-based sharing mode from a persistence mode with smart contracts, erasure coding, dispersal, and proof challenges, which is analytically useful because it separates basic peer sharing from durable storage guarantees
Codex’s verifiable-manifest flow adds slot roots and a final verification root above erasure-coded blocks, making zero-knowledge storage proofs central to the protocol’s persistence claims rather than an afterthought
The roadmap states that the tokenomics model treats CDX as payment, staking, and posted collateral, which means durability is intended to be enforced through an explicit incentive layer instead of best-effort altruism alone
Compared with IPFS, Codex is trying to make durability and persistence itself the product; compared with Filecoin, it emphasizes erasure-coded durability-engine design and provider auto-matching over storage-power consensus
Whitepaper: Codex publicly references an official whitepaper at https://docs.codex.storage/learn/whitepaper, but during this review that docs path redirected into the broader Logos tech-stack site. A primary-source packet for the current pass has been saved as ../whitepapers/codex-primary-sources-2026-05-09.md.