Logos Messaging

From Local Area Network
Revision as of 19:21, 4 November 2026 by Eleutherious (talk | contribs) (New article from the Building a Parallel Society course, source-checked)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Logos Messaging is the messaging layer of the Logos technology stack. Logos describes it as "Private, censorship-resistant communication between parties." Its main component, Logos Delivery, was formerly called Waku. Together with Logos Blockchain and Logos Storage it makes up the initial Logos stack, and people run it on their own machines through Basecamp.

What it does

The Logos documentation says Logos Messaging lets applications "send messages, relay data, and coordinate with one another without relying on centralised servers or exposing metadata." Messages travel across a peer-to-peer relay network "with no central broker". It supports one-to-one messages, group messages and public broadcast channels. Anyone can run a node, and there is no gas fee for sending or receiving messages.

The Logos website calls it "Resilient, private messaging for coordination in hostile environments."

The Logos activist course Building a Parallel Society (2026) describes Logos Messaging as a transport layer. It says chat is one of the things built on it. The course lists three uses: coordination between people and groups "that no platform is hosting", a channel that the other modules and applications use to talk to each other, and a mixnet layer. It says the module removes "the platform that controls who can organise with whom."

How it works

The documentation describes two modules.

  • Delivery is "the peer-to-peer messaging network at the base of the messaging stack". It is the reference implementation of the Logos Messaging protocol. Applications combine a set of protocols. Relay handles publish and subscribe messaging. RLN Relay adds spam protection with rate limiting nullifiers, which check a zero-knowledge proof in place of the sender's identity. Filter, Store and Light Push serve nodes with little bandwidth. Store keeps messages for a time so that offline peers can catch up. It does not guarantee that they stay available.
  • Chat is "a protocol and library that provides one-to-one and group conversations with end-to-end encryption, using de-MLS for group messaging." It uses Delivery as its transport.

Logos Messaging is built on libp2p. The documentation says it adds a service network that anyone can use without running their own infrastructure, and spam protection that libp2p does not provide.

The documentation states the privacy limits openly. Relay provides pseudonymity and unlinkability. Store and Filter need a direct connection, so a node serving them can link a peer's identifier to the topics it asks for.

Mixnet

The Logos stack also has a mixnet in its networking layer. The documentation says messages are "routed through a sequence of intermediary relay nodes that shuffle and delay traffic before forwarding it", with cover traffic. The course calls the mixnet layer "running today as a demo". The Logos documentation describes its current state as a separate desktop app, chat_ui_mix, built from a branch of the Logos Chat interface. The app connects to a "testnet-0.2 mix fleet" and sends messages "sender-unlinkably through the 3-hop mixnet." That procedure is marked accurate for Testnet v0.2.1.

In Basecamp

The Logos website lists a Chat app in Basecamp for "Encrypted one-to-one chat. Peer to peer, with no server in the middle." The Logos procedure, marked accurate for Testnet v0.2.1, installs Chat from the Basecamp Package Manager. Installing it also brings in the chat module and the delivery module. The app gives each instance an address that another instance uses to open a conversation. The procedure notes that "Identity, conversations, and message history exist only while the app is running."

On 1 November 2026 the official module catalogue, logos-co/logos-modules-release on GitHub, listed seven Logos Messaging modules. They include the delivery and chat modules, the Chat interface, a libp2p networking module, two rate limiting nullifier modules and an educational Delivery Demo. The catalogue pinned the delivery module at version 0.3.3 and the chat module and Chat interface at 0.3.0. The underlying chat library describes itself as "pre-1.0, and moving", with every component at version 0.1.0 and the protocol not yet frozen.

Names

The Logos documentation glossary defines Waku as "An old name for the Logos Delivery component of the Logos technology stack." Its list of repositories says logos-delivery was "formerly nwaku" and logos-delivery-js was "formerly Waku v2". The documentation still links to Waku pages and specifications in places. The Logos Field Guide (2026), a guide for anyone publishing or building under Logos, says "Logos Messaging was previously part of Waku." It asks for current module names in public-facing work and says Nomos, Waku and Codex are used "only when helping people map old names to current modules."

See also

Sources

Page status: Outline. Stub · Outline · Usable · Guide · Star. Anyone can improve this page and change its status.
Retrieved from "https://alienware-1.tailb5c716.ts.net/index.php?title=Logos_Messaging&oldid=796"