Logos Messaging is the messaging stack of the Logos project — a unified, privacy-by-default decentralized technology stack.
We build the protocols and libraries that move messages between people, devices, and applications without depending on centralized servers, surveillance infrastructure, or single points of failure.
| Website | logos.co |
| Builder Hub | build.logos.co |
| Specifications | lip.logos.co |
| Roadmap | roadmap.logos.co/messaging |
| Forum | forum.logos.co |
| Discord | discord.gg/logosnetwork |
| X | @Logos_network |
| Logos GitHub org | github.com/logos-co |
Logos Messaging is composed of two complementary layers, both designed to run standalone or as modules inside the broader Logos stack.
The transport layer. A peer-to-peer messaging network with DoS protection via RLN (Rate Limiting Nullifiers). Any application can use it to send and receive messages over an open, censorship-resistant network.
| Repository | Description |
|---|---|
logos-delivery |
Reference Nim implementation — the network's main node |
logos-delivery-compose |
Run a node with docker-compose |
The chat layer. A protocol and library that provides 1:1 and group conversations with end-to-end encryption using de-MLS - everything an application needs to add private chat without rolling its own protocol.
| Repository | Description |
|---|---|
libchat |
Logos Chat library (Rust) |
| Repository | Description |
|---|---|
specs |
Protocol specifications (published specs migrate to lip.logos.co) |
pm |
Roadmap, milestones, and deliverables — see the public roadmap |
awesome-logos-delivery |
Community-curated list of resources and projects |
Logos is built in the open by a global community of contributors. Whether you're building applications on top of Logos Messaging, contributing to the protocols themselves, or running a node — there's a place for you.
- Build something. The Logos Builder Hub has guides for using the Delivery Module API and the Chat Module API from your own application.
- Run a node. Spin up Logos Delivery with docker-compose and join the testnet.
- Pick up an issue. Browse
good first issuelabels across our repositories, or check the Logos contribute portal. - Ask questions. The fastest way to get an answer is Discord. Longer-form discussion happens on the forum.
Logos Messaging was previously known as Waku. You will still see the legacy names in code, branches, and older issues:
- Logos Delivery ← Waku, nwaku, nim-waku, logos-messaging-nim
- Logos Chat ← Chat SDK, ChatSDK, nim-chat-poc
The migration is happening gradually. Please use the current names in new code, documentation, and external communications.
*Logos Messaging is part of the broader Logos stack.
