Logos is a modular technology stack for building local first, decentralized applications. Logos consolidates previously separate efforts (Nomos, Codex, and Waku) under one public identity to reduce cognitive load and provide a unified developer experience.

This diagram is a conceptual view of Logos as a layered stack. Dapps use one or more Logos components (storage, messaging, blockchain, and user modules), which rely on shared networking and kernel layers underneath.

Inside Logos, the top row shows the subsystems that Dapps interact with most directly:

• Blockchain (decentralized compute) represents the main compute/state layer, with two responsibilities:

  • Data Availability and Consensus is the base layer that ensures (1) transaction data is published and retrievable by the network, and (2) nodes agree on a single, ordered history of blocks.
  • Execution Zone is where application logic runs and state is updated (separate from the layers that only order blocks and guarantee data availability).

• Messaging (coordination) is the peer-to-peer communication layer used by apps to publish or retrieve messages.

• Storage (serve frontends) provides the node-side content storage and retrieval functionality.

• User Modules represent pluggable modules that extend Logos' capabilities such as wallet and key management, messaging features, identity, access control, or module installation.

• Discovery, Peering, Mix-net is a shared networking layer. "Discovery" and "peering" are the fundamentals for finding and maintaining peer connections, while "mix-net" aligns with the stack's AnonComms goal (routing with improved metadata privacy) and capability discovery.

• Everything sits on the Logos Kernel, which is the lowest layer in the picture. In the public repos, you can see two building blocks that match that "kernel/runtime foundation" idea.

The sections below include the information and links for the things that you can do now in Logos.

Build and run the Logos App: Build the application from source using Nix and launch it locally with all required modules and dependencies loaded automatically.

• Build instructions
• Modules
• Build and run Logos App (alpha) to access Testnet v0.1 UIs — Build and launch the Logos App alpha release to access the Testnet v0.1 user interfaces.
• Run Logos Node in headless mode — Run a Logos node without a graphical interface for server or automated environments.

• Set up a wallet for the Logos Execution Zone — Install and configure a wallet to interact with the Logos Execution Zone.
• Transfer native tokens on the Logos Execution Zone — Send and receive native tokens between wallets on the Logos Execution Zone.
• Create and transfer custom tokens on the Logos Execution Zone — Mint your own custom tokens and transfer them on the Logos Execution Zone.
• Create and use an AMM liquidity pool in the Logos Execution Zone — Set up and interact with an automated market maker liquidity pool on the Logos Execution Zone.

• Start a Logos blockchain node using the CLI — Set up and run a Logos blockchain node from the command line.

• Use the Logos Storage module API from an app — Interact with the Logos Storage module API to store and retrieve data from your application.
• Store and retrieve a file using the Simple Filesharing App — Walk through storing and retrieving files using the Simple Filesharing application.

• Use the Logos Delivery Module API from an app — Integrate the Logos Delivery Module API into your application to send and receive messages.
• Use the Logos Chat Module API from an app — Integrate the Logos Chat Module API into your application to enable chat functionality.

• Discover nodes and send messages via the AnonComms Mixnet demo app — Use the AnonComms Mixnet demo application to discover network nodes and exchange messages anonymously.

Please open an issue in this repository describing what you are trying to complete and where you got blocked.

We are consolidating and updating previously fragmented materials into a single, coherent developer experience and source of truth, featuring consistent navigation and terminology. This process is ongoing, and we appreciate your patience as we work to provide comprehensive and up-to-date documentation.

We are also unifying public naming in our documentation to reflect Logos as a single technical stack: Nomos → Logos Blockchain, Codex → Logos Storage, and Waku → Logos Messaging. This consolidation makes the architecture easier to navigate by aligning documentation, examples, and terminology under one scheme. Legacy names may still appear in repositories and specifications, but going forward the Logos-first names will be used across our docs.

Our aim is to provide a predictable onboarding path for operators and developers, where they can find what they need and trust what they read.

In 2026 we will release documentation in phases aligned with the project milestones.

We will provide operator guides for those who want to run and support the Logos Blockchain, and developer guides for contributors building decentralized applications on the Logos stack (blockchain, storage, messaging).

We will update this page as sections go live and contribution paths open. Timelines may adjust as the system evolves.