Codex

Decentralized Storage Network

Decentralized Durability Engine (DDE) and P2P storage protocol developed under the Logos technology stack (IFT/Status), designed for censorship-resistant, durable data storage using erasure coding, ZK-proof-based remote auditing, and a marketplace for incentivizing storage providers. Targets archival and cold storage use cases with 'lazy' data repair.

Community
Links
Visit Website See this tool in the graph Suggest an edit

Details

License Libre (MIT / Apache 2.0)
Dev Status 🔬 Beta
Dev Status Detail Beta (non-incentivized testnet launched Sept 2024; incentivized testnet and mainnet planned)
Owner IFT (formerly Logos/Status); Dmitriy Ryajov (CTO)
Governing Body Institute of Free Technology (IFT, formerly Logos/Status)
Country Global / distributed team (IFT is decentralized)
Start Year 2021
Stack Nim
Funding Personal investment / Foundation (IFT/Logos internal funding; part of Status/IFT ecosystem)
Last Investigated Mar 9, 2026

Topology view

This tool in the centre and the things it is directly related to. Each line names the kind of relationship.

Topology view: CodexThis tool in the centre and the things it is directly related to. Each line names the kind of relationship.CodexIPFS (Based on)IPFS
  • IPFS (Tool): Based on

Open in Graph Explorer

Use Case Domains

Platform Evolution & Sovereignty

Affordances

Self-hostable Local-first storage

Decentralized Storage Network Attributes

Origins Censorship-resistant archival storage / Logos ecosystem infrastructure
Database Distributed (erasure-coded blocks via DHT; content-addressed CIDs; nim-libp2p)
Query Language REST API
Data Formats Any binary; CID-addressed content blocks
Mobile Support N/A (infrastructure protocol)
Web Support Planned (API-accessible; no web UI yet)
Native Apps N/A (CLI node; no GUI yet)
Terms Self-hosting (run node); CDX token (planned for mainnet marketplace)
Funds Undisclosed (funded internally by IFT; no public fundraise disclosed)
Based On IPFS-influenced (uses CIDs, DHT, libp2p); custom erasure coding and ZK proof layer
P2P Architecture DHT (Kademlia-based via nim-libp2p; block exchange protocol similar to BitSwap)
Overlay Network Global
Content Addressing Yes (IPFS-compatible CIDs)
Local-First N/A (distributed storage)
E2EE Yes (planned; privacy-preserving design goal of Logos stack)
Byzantine Fault Tolerance Planned (ZK proof-based remote auditing for storage verification; marketplace with slashing)
Signature Ed25519 / ECDSA (libp2p standard); ZK-SNARKs (Poseidon2 hash for storage proofs)
Permissions N/A (currently open; marketplace-based permissions planned)
Semantic Web Compatibility N/A
Smart Contract Planned for future (Codex Marketplace contracts for storage agreements and payments)
Protocol Stack Position Application-layer (built on TCP/IP)
Asset / Value Embedding Application-layer add-on (CDX token planned for marketplace; not yet deployed)
Protocol Maturity / Standardization Pre-specification / Academic-Research (whitepaper published; testnet live; mainnet not yet launched; no standards body involvement)
Update Policy Immutable / Append-only (content-addressed blocks are immutable; appendable data planned as future feature)
Storage Proof Mechanism Hybrid: Erasure coding with ZK-SNARK audit (compact proofs of storage using SNARK circuits with Poseidon2 hashing; lightweight remote auditing without downloading data; slot recovery mechanism for 'lazy' repair)
Economic / Incentive Model Token rewards (CDX token planned): storage providers stake CDX as collateral; clients pay CDX for storage marketplace slots; validators earn CDX for processing challenges
Retrieval Guarantee Best-effort (incentivized via marketplace contracts; cryptographic proofs verify storage; lazy repair mechanism restores lost shards; mainnet guarantees not yet established)

Relationships

How this tool connects to other tools and organizations, from relationships reviewed by the OpenHaven data steward. They describe how projects connect, not how good they are.

Based on