Logos Messaging: Difference between revisions

From Local Area Network
← Older edit
Second check fixes, plus material from the Circles handbook, Circle reports, LAN and Logos docs, source-checked
Course no longer cited as a source: views attributed to Logos, plain facts stated plainly
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
'''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]].
'''Logos Messaging''' is the messaging layer of the [[Logos]] technology stack, built for private, censorship-resistant communication between parties. Its main component, Logos Delivery, was formerly called Waku. With [[Logos Blockchain]] and [[Logos Storage]] it makes up the initial Logos stack, which people run on their own machines through [[Basecamp]].


== What it does ==
== 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 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. Among its use cases, Logos lists resilient, private messaging for coordination in hostile environments.


Among its use cases, the Logos website lists "Resilient, private messaging for coordination in hostile environments."
Logos describes the messaging layer as a transport layer, with chat as one of the things built on it. It lists three uses: coordination between people and groups that no platform is hosting, a channel the other modules and applications talk through, and a mixnet layer. In its words, the module removes "the platform that controls who can organise with whom."
 
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. The first is coordination between people and groups "that no platform is hosting". The second is a channel that the other modules and applications use to talk to each other. The third is a mixnet layer. The course says the module removes "the platform that controls who can organise with whom."


== How it works ==
== How it works ==
The documentation describes two modules.
Logos Messaging has 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, in which senders publish to topics and nodes receive the topics they subscribe to. Topics are labels that route messages. RLN Relay adds spam protection with rate limiting nullifiers (RLN). Each message carries a zero-knowledge proof in place of the sender's identity. The Messaging FAQ says the proof shows only that the sender belongs to a set of users allowed to send a certain number of messages in a given time. 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, and the FAQ "recommends using Logos Storage for long-term storage."
* '''Delivery''' is the peer-to-peer messaging network at the base of the messaging stack and the reference implementation of the Logos Messaging protocol. Applications combine a set of protocols. Relay handles publish and subscribe messaging, in which senders publish to topics, the labels that route messages, and nodes receive the topics they subscribe to. RLN Relay adds spam protection with rate limiting nullifiers (RLN). In place of the sender's identity, each message carries a zero-knowledge proof. In the Messaging FAQ's description, the proof shows only that the sender belongs to a set of users allowed to send a certain number of messages in a given time. 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, and Logos recommends Logos Storage for long-term storage.
* '''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.
* '''Chat''' is a protocol and library for end-to-end encrypted one-to-one and group conversations. It uses de-MLS for group messaging and Delivery as its transport.


The FAQ says Delivery encrypts the connections between nodes but applies "no default encryption method" to the data itself. Applications choose their own encryption for message contents.
Delivery encrypts the connections between nodes but applies no default encryption to the data itself, so applications choose their own encryption for message contents.


LAN Issue 2, the Logos movement's zine, explains what de-MLS changes. It says MLS, the standard for encrypted group chat, "assumes a server that is always online will do the job, which means whoever runs the server holds the member list." It says "Logos Messaging's version, de-MLS, removes that server and assigns the job to one member at a time, with the role rotating." Members propose adding or removing someone, and the group votes over the network. A protocol called Scalable Data Sync keeps every member in step, since each message points back to the messages that led to it. See [[Issue 2/Who Keeps the Member List?]].
LAN Issue 2, the Logos movement's zine, sets out what de-MLS changes. According to the zine, MLS, the standard for encrypted group chat, assumes an always-online server, so whoever runs the server holds the member list. The de-MLS version removes that server and gives the job to one member at a time, with the role rotating. Members propose adding or removing someone, and the group votes over the network. A protocol called Scalable Data Sync keeps every member in step, since each message points back to the messages that led to it. See [[Issue 2/Who Keeps the Member List?]].


Logos Messaging is built on libp2p, a widely used peer-to-peer networking library. 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.
Logos Messaging is built on libp2p, a widely used peer-to-peer networking library. On top of it, Logos Messaging adds a service network that anyone can use without running their own infrastructure, and spam protection, which libp2p does not provide.


The documentation sets out the privacy limits. Relay provides pseudonymity, so messages carry no real identity, and unlinkability, so messages are hard to tie to their sender. Store and Filter need a direct connection, so a node serving them can link a peer's identifier to the topics it asks for.
Its privacy has limits. Relay provides pseudonymity, so messages carry no real identity, and unlinkability, so messages are hard to tie to their sender. 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 ===
=== 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". For Testnet v0.2.1 the documentation describes 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." With Testnet v0.3, Logos says "Chat now uses RLN and Mix through Delivery." Mix is also available to developers through the Messaging API, and "the Mix module allows node operators to run mix nodes."
The networking layer of the Logos stack also includes a mixnet. It routes messages through a sequence of intermediary relay nodes that shuffle and delay traffic before forwarding it, and adds cover traffic. Logos describes the mixnet layer as running today as a demo. For Testnet v0.2.1 the documentation describes a separate desktop app, chat_ui_mix, built from a branch of the Logos Chat interface. It connects to a testnet-0.2 mix fleet and sends messages through the 3-hop mixnet so that they cannot be linked to their sender. With Testnet v0.3, Chat uses RLN and Mix through Delivery. Developers can also reach Mix through the Messaging API, and the Mix module allows node operators to run mix nodes.


== In Basecamp ==
== 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 for one-to-one chat, 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. That procedure says "Identity, conversations, and message history exist only while the app is running." Logos says that with Testnet v0.3 "Chat now keeps message history across sessions". It adds that "reopening chat creates a new account." The group procedure says conversations from an earlier launch "stay readable under Previous sessions but can't be sent to".
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 procedure for one-to-one chat, 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. In that version identity, conversations and message history exist only while the app is running. With Testnet v0.3 Chat keeps message history across sessions, although reopening it creates a new account. Conversations from an earlier launch stay readable under Previous sessions but cannot be sent to.


The group procedure, written for Testnet v0.3.0, describes end-to-end encrypted group conversations in the Chat app. Members are invited by address. It says "in this release membership only grows: members can't be removed and can't leave."
The group procedure, written for Testnet v0.3.0, covers end-to-end encrypted group conversations in the Chat app, with members invited by address. In that release membership only grows, as members cannot be removed and cannot leave.


Sending on the logos.test network needs an RLN membership. The documentation says "a node needs an active membership before any message it sends goes out." In Basecamp the membership is registered from the Delivery Demo app. The node pays for it in LEZ native tokens from a payer account that it derives itself, and "There is no faucet". The documentation lists Chat and its two modules among the Basecamp apps that run natively on Windows.
Sending on the logos.test network needs an RLN membership, and a node's messages do not go out until its membership is active. In Basecamp the membership is registered from the Delivery Demo app. The node pays for it in LEZ native tokens from a payer account that it derives itself, and there is no faucet. Chat and its two modules are among the Basecamp apps that run natively on Windows.


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.
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 is pre-1.0 and still moving, with every component at version 0.1.0 and the protocol not yet frozen.


== In use ==
== In use ==
Projects on the [[Tools]] page that use Logos Messaging include [[Booth]], [[Receiver]], [[Forumer]], [[KYM]], [[Perun]], [[Shrooms]], [[WhisperBox]], [[Backpack]], [[Whistleblower]] and [[Logos Autonomous Agent]]. [[LNS]], [[LEZ Atomic Swaps]] and [[Forum-protocol]] also use it. The Tools page lists those three under the Logos Execution Zone.
Projects on the [[Tools]] page that use Logos Messaging include [[Booth]], [[Receiver]], [[Forumer]], [[KYM]], [[Perun]], [[Shrooms]], [[WhisperBox]], [[Backpack]], [[Whistleblower]] and [[Logos Autonomous Agent]]. [[LNS]], [[LEZ Atomic Swaps]] and [[Forum-protocol]] also use it, though the Tools page lists those three under the Logos Execution Zone.


In October 2025 the [[Circles/Porto|Porto Circle]] proposed a privacy-first support tool for survivors of domestic violence, designed on Waku. Its proposal argued that "Existing helplines and police systems are centralised, easily traceable, and often unsafe."
In October 2025 the [[Circles/Porto|Porto Circle]] proposed a privacy-first support tool for survivors of domestic violence, designed on Waku. Its proposal argued that "Existing helplines and police systems are centralised, easily traceable, and often unsafe."


== Names ==
== 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. It keeps the name Waku for legacy work, older documents, upstream history and specific technical components.
Waku is an old name for the Logos Delivery component of the Logos stack. Among the Logos repositories, 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, notes that Logos Messaging was previously part of Waku. It asks for current module names in public-facing work and keeps the name Waku for legacy work, older documents, upstream history and specific technical components.


== See also ==
== See also ==
Line 72: Line 70:
* [https://github.com/logos-co/logos-chat-ui/blob/15c16ca4ad48efe63993daa0765cac8ca9f7c36d/metadata.json logos-chat-ui metadata.json], GitHub, as pinned in the catalogue on 1 November 2026
* [https://github.com/logos-co/logos-chat-ui/blob/15c16ca4ad48efe63993daa0765cac8ca9f7c36d/metadata.json logos-chat-ui metadata.json], GitHub, as pinned in the catalogue on 1 November 2026
* LAN, Issue 2, Logos, October 2026
* LAN, Issue 2, Logos, October 2026
* Building a Parallel Society, Logos activist course, 2026
* Logos Circles training material, 2026
* Logos Field Guide, Logos, 2026
* Logos Field Guide, Logos, 2026


{{Page status|Outline}}
{{Page status|Outline}}
[[Category:Logos]]
[[Category:Logos]]

Latest revision as of 23:55, 4 November 2026

Logos Messaging is the messaging layer of the Logos technology stack, built for private, censorship-resistant communication between parties. Its main component, Logos Delivery, was formerly called Waku. With Logos Blockchain and Logos Storage it makes up the initial Logos stack, which people run 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. Among its use cases, Logos lists resilient, private messaging for coordination in hostile environments.

Logos describes the messaging layer as a transport layer, with chat as one of the things built on it. It lists three uses: coordination between people and groups that no platform is hosting, a channel the other modules and applications talk through, and a mixnet layer. In its words, the module removes "the platform that controls who can organise with whom."

How it works

Logos Messaging has two modules.

  • Delivery is the peer-to-peer messaging network at the base of the messaging stack and the reference implementation of the Logos Messaging protocol. Applications combine a set of protocols. Relay handles publish and subscribe messaging, in which senders publish to topics, the labels that route messages, and nodes receive the topics they subscribe to. RLN Relay adds spam protection with rate limiting nullifiers (RLN). In place of the sender's identity, each message carries a zero-knowledge proof. In the Messaging FAQ's description, the proof shows only that the sender belongs to a set of users allowed to send a certain number of messages in a given time. 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, and Logos recommends Logos Storage for long-term storage.
  • Chat is a protocol and library for end-to-end encrypted one-to-one and group conversations. It uses de-MLS for group messaging and Delivery as its transport.

Delivery encrypts the connections between nodes but applies no default encryption to the data itself, so applications choose their own encryption for message contents.

LAN Issue 2, the Logos movement's zine, sets out what de-MLS changes. According to the zine, MLS, the standard for encrypted group chat, assumes an always-online server, so whoever runs the server holds the member list. The de-MLS version removes that server and gives the job to one member at a time, with the role rotating. Members propose adding or removing someone, and the group votes over the network. A protocol called Scalable Data Sync keeps every member in step, since each message points back to the messages that led to it. See Issue 2/Who Keeps the Member List?.

Logos Messaging is built on libp2p, a widely used peer-to-peer networking library. On top of it, Logos Messaging adds a service network that anyone can use without running their own infrastructure, and spam protection, which libp2p does not provide.

Its privacy has limits. Relay provides pseudonymity, so messages carry no real identity, and unlinkability, so messages are hard to tie to their sender. 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 networking layer of the Logos stack also includes a mixnet. It routes messages through a sequence of intermediary relay nodes that shuffle and delay traffic before forwarding it, and adds cover traffic. Logos describes the mixnet layer as running today as a demo. For Testnet v0.2.1 the documentation describes a separate desktop app, chat_ui_mix, built from a branch of the Logos Chat interface. It connects to a testnet-0.2 mix fleet and sends messages through the 3-hop mixnet so that they cannot be linked to their sender. With Testnet v0.3, Chat uses RLN and Mix through Delivery. Developers can also reach Mix through the Messaging API, and the Mix module allows node operators to run mix nodes.

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 procedure for one-to-one chat, 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. In that version identity, conversations and message history exist only while the app is running. With Testnet v0.3 Chat keeps message history across sessions, although reopening it creates a new account. Conversations from an earlier launch stay readable under Previous sessions but cannot be sent to.

The group procedure, written for Testnet v0.3.0, covers end-to-end encrypted group conversations in the Chat app, with members invited by address. In that release membership only grows, as members cannot be removed and cannot leave.

Sending on the logos.test network needs an RLN membership, and a node's messages do not go out until its membership is active. In Basecamp the membership is registered from the Delivery Demo app. The node pays for it in LEZ native tokens from a payer account that it derives itself, and there is no faucet. Chat and its two modules are among the Basecamp apps that run natively on Windows.

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 is pre-1.0 and still moving, with every component at version 0.1.0 and the protocol not yet frozen.

In use

Projects on the Tools page that use Logos Messaging include Booth, Receiver, Forumer, KYM, Perun, Shrooms, WhisperBox, Backpack, Whistleblower and Logos Autonomous Agent. LNS, LEZ Atomic Swaps and Forum-protocol also use it, though the Tools page lists those three under the Logos Execution Zone.

In October 2025 the Porto Circle proposed a privacy-first support tool for survivors of domestic violence, designed on Waku. Its proposal argued that "Existing helplines and police systems are centralised, easily traceable, and often unsafe."

Names

Waku is an old name for the Logos Delivery component of the Logos stack. Among the Logos repositories, 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, notes that Logos Messaging was previously part of Waku. It asks for current module names in public-facing work and keeps the name Waku for legacy work, older documents, upstream history and specific technical components.

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=886"