Codex primary sources — 2026-05-09

Notes

• Codex now sits inside the broader Logos branding stack, and several historical docs URLs redirect into Logos pages.
• The official Codex whitepaper URL is still referenced by official materials, but during this pass it redirected instead of returning the paper itself.
• Because of that, this packet leans on official Codex blog posts plus Codex GitHub repositories for mechanism details.

Primary sources reviewed

• https://codex.storage/
  • Official project site.
• https://blog.codex.storage/the-codex-roadmap-for-2025-and-beyond/
  • Official roadmap post describing Codex as a Decentralised Durability Engine (DDE) and outlining tokenomics, incentivized testnet, and mainnet-readiness milestones.
• https://blog.codex.storage/protocol-breakdown-how-the-codex-p2p-network-works/
  • Best high-level mechanism explainer reviewed this pass; covers bootstrap discovery, altruistic mode, persistence mode, erasure coding, manifests, and verification roots.
• https://blog.codex.storage/how-to-interact-with-a-codex-node/
  • Good operational source for CLI installer, ports, REST API, app interface, and current testnet usage.
• https://docs.codex.storage/learn/whitepaper
  • Official whitepaper endpoint referenced by Codex materials; redirected during this pass.
• https://api.codex.storage/
  • Official API surface referenced by Codex blog posts.
• https://github.com/codex-storage/codex-spec
  • Official specs repository; describes Codex as building a decentralized durability engine and notes specs remain under active discussion.
• https://github.com/codex-storage/nim-codex
  • Official implementation repository; describes the client as a decentralized durability engine / file-sharing client under active development.

Key takeaways captured for corpus

• Codex separates altruistic CID-based sharing from persistence mode with explicit incentives and proofs.
• Persistence mode relies on erasure coding, dispersal, smart-contract storage requests, and zero-knowledge proof machinery.
• Provider matching is passive/automatic against local policy constraints rather than direct manual client selection.
• Codex’s control surface appears to sit in contract parameters, collateral/payment policy, erasure/verification design, and provider auto-matching behavior.