Logos Assembly

Article: Introducing Logos Storage — Decentralized Storage for the Logos Tech Stack

5 min read

Summary

The first in-depth introduction to Logos Storage — the decentralized storage layer of the Logos tech stack. This article establishes what Logos Storage is, why it exists, how it fits into the broader Logos ecosystem (as introduced in the “Logos as Operating System” and “Modular Architecture” articles), and what it’s designed to accomplish. It draws on the project’s original SRS to frame the full vision — erasure-coded data persistence with storage proofs, a marketplace for storage providers, content discovery, and privacy as a foundational design constraint — while grounding readers in what’s concretely available today in testnet v0.1: a simple filesharing app and a storage module API.

Formerly known as Codex (mentioned briefly, not dwelled on). The rebrand narrative and detailed technical updates (DHT migration, block exchange refactoring, Status integration, etc.) are reserved for a future technical update article.

Audience

Primary: Developers and infrastructure engineers interested in understanding what Logos Storage is and how it fits into the Logos ecosystem. Readers of the prior “Logos as Operating System” and “Modular Architecture” articles who want to go deeper on the storage layer. Secondary: Privacy engineers, IPFS/Filecoin developers looking at alternatives, anyone evaluating decentralized storage solutions.

Key Angles

What Logos Storage Is

  • The decentralized storage and data persistence layer for the Logos tech stack
  • Formerly known as Codex (brief mention — not a narrative focus)
  • A peer-to-peer file-sharing system built on content-addressed blocks
  • Designed as one of the three foundational Logos modules (alongside Messaging and Blockchain)

How It Fits Into the Logos Stack

  • References the layered architecture from “Logos as Operating System”: kernel → networking → modules → dapps
  • Storage is one of the three default modules shipped with Logos
  • Integrates through the Logos Core module system (as described in the “Modular Architecture” article)
  • Available as a Logos Core module (logos-storage-module) with C bindings, headless mode, and developer tutorials
  • Interacts with the networking layer’s mix-net for privacy, and with the blockchain layer for marketplace operations

What’s Available Today (Testnet v0.1)

  • Simple Filesharing App in the Logos App: store a file, enter a CID and get it back
  • Storage module API for developers to test against
  • Storage Node loadable through Logos Core (headless or with UI)
  • Privacy features (anonymous downloads via mixnet, anonymous publishing) are in active research

What Differentiates Logos Storage

  • Privacy-first design — most decentralized storage projects leak metadata at discovery, transfer, and publishing stages
  • Integration with the Logos mixnet for anonymous file retrieval (in research)
  • Native integration with the Logos ecosystem (module system, blockchain marketplace, mix-net privacy)
  • Not a standalone product — designed as infrastructure for Logos

Article Structure (Proposed)

  1. Introduction — What Logos Storage is and where it sits in the stack. Brief mention of formerly being called Codex. Reference to prior articles for ecosystem context.
  2. The Problem — Why decentralized storage matters. What centralized alternatives get wrong. What existing decentralized storage (IPFS, Filecoin, Arweave) gets right but also where they fall short on privacy.
  3. The Design — Core architecture: content-addressed blocks, Merkle trees, content discovery.
  4. Privacy by Design — The privacy dimension that distinguishes Logos Storage. Discovery, transfer, and publishing metadata leaks. How the protocol addresses each.
  5. Where It Stands Today — Testnet v0.1 scope: what you can do right now. The storage module, the filesharing app, the developer API.
  6. What Comes Next — privacy features moving from research to implementation, deeper ecosystem integration, exploration into the variety of persistence needs and their associated mechanisms of providing for them.

Sources

Core Reference

  • Testnet v0.1 scope: roadmap/content/testnets/v01.md

Prior Articles in Series

  • “Understanding the Logos Tech Stack: An Operating System for Sovereignty” — establishes the layered architecture
  • “Building on Logos Core: The Modular Architecture and Package Manager” — explains how modules work

Code & Tools

Specs

Research & Privacy

Notes

  • This is now framed as the introductory article for Logos Storage, not a technical update.
  • Detailed engineering updates (DHT migration, block exchange refactoring, Status integration, Storage Module headless improvements) should be saved for a separate technical update article later.
  • Keep the Codex mention brief — “formerly known as Codex” — no need to explain the rebrand rationale.
  • Readers should come away understanding: (1) what Logos Storage will be, (2) how it fits into Logos, (3) what they can try today, (4) what’s coming.
  • If the blockchain module can be see as on-chain persistence and compute, the storage module looks to provide ways to enable offline persistence and compute.

Graph View

Backlinks