iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Waku is an open-source family of peer-to-peer communication protocols. It lets applications exchange short, mostly real-time messages without sending them through one central messaging server. It is not a blockchain, and it is not a long-term storage network. Developers use it as a communications layer for chat and for app-to-app or device-to-device data exchange.
What Waku is, and what it is not
- It is a protocol family, not an app or a chain. Waku defines how messages are sent, relayed and retrieved. Any application can build on it.
- It does not require blockchain transactions. Waku’s FAQ states that sending and receiving messages does not require a gas fee.
- It is not durable storage. It is designed for short, ephemeral messages. Its Store component offers temporary retrieval, and the FAQ says availability is not guaranteed.
- It is not the React framework also called Waku. The two share a name and nothing else. This article covers only the messaging protocol.
The protocol pieces
Waku splits its work into separate components. Each one solves a different connectivity problem, and each carries its own trade-offs.
| Component | What it does | What it depends on |
|---|---|---|
| Relay | Broadcasts messages across peers using a publish/subscribe model | Peers that stay online and forward traffic |
| Filter | Lets a lighter client request only the messages it selected | A service peer that holds and serves those messages |
| Light Push | Lets a constrained client ask a peer to publish a message into the relay network | A service peer willing to publish on its behalf |
| Store | Helps a client retrieve messages it missed while offline | A peer that retained the messages; availability is not guaranteed |
Relay: gossip across the network
Relay is the backbone. It is built on libp2p GossipSub. Nodes subscribe to topics and pass messages along to their peers, so no single server sits in the middle of every conversation. A node running Relay carries traffic for others, which is why it needs to stay online and have bandwidth to spare.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsFilter and Light Push: for clients that cannot relay everything
Phones and browsers often cannot stay connected as full relay nodes. Filter lets such a client ask a service peer for a subset of messages instead of the whole stream. Light Push lets it hand a message to a peer and ask that peer to publish it into the relay network.
#1 Best Overall
The trade-off is dependence. A light client relies on a service peer for those operations, so it is not identical to a continuously connected relay node. What it sees depends on what that peer chooses to serve or forward.
Store: catching up on missed messages
Store helps a client recover messages it missed while it was offline. Treat it as a short-term catch-up mechanism. It is not an archive. Anyone building a product that must keep records should plan a separate storage system.
Privacy: what Waku promises and what it leaves to the application
Waku is designed with privacy and censorship resistance as goals. Those goals do not mean every message is encrypted end to end. The official FAQ separates transport protection from payload encryption, and the difference matters.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Transport encryption
Node-to-node connections use libp2p Noise. That protects the link between two peers. It does not, by itself, protect the content of a message from every node that carries it.
Payload encryption is the application’s job
There is no default encryption for the data payload. An application must choose and implement a suitable payload-encryption method. Any claim that a Waku-based app is end-to-end encrypted depends on that application-layer work, not on the protocol alone.
Sender and receiver privacy by design
The Waku team’s explainer “The Basics of How P2P Messaging Works on Waku,” dated November 19, 2024, describes topic-based pub/sub and says the model is designed to keep sender and receiver identities private. Read that as design intent. Actual privacy depends on protocol choices, network topology, client behavior and the encryption a developer adds. Metadata may still be visible to some observers in some deployments.
Spam control with Rate Limiting Nullifiers
Waku uses Rate Limiting Nullifiers (RLN) to limit how fast a publisher can send messages. RLN is a zero-knowledge mechanism. Each message carries a proof that relay nodes can verify against the publisher’s allowance, and the design aims to avoid exposing the publisher’s private information. The stated purpose is to reduce spam and control bandwidth use across the network.
The Waku team’s March 26, 2024 technical overview describes the mechanism’s configuration with figures, some explicitly labelled tentative. Use those figures to understand how the system is meant to work, not as the limits a live network enforces today.
Storage and use cases
Waku suits short, ephemeral, real-time messaging. The FAQ puts the contrast with IPFS this way: “Waku focuses on short, ephemeral, real-time messages, while IPFS focuses on large, long-term data storage.” IPFS or another storage system handles the second job.
Rank #4
The official introduction lists possible applications, including chat messengers, voting and proposals, NFT-marketplace interactions, state channels, multisignature-wallet signature exchange, game communication, Layer 2 coordination and social platforms. These describe what the protocol can support. They do not show that each category has a mature or widely deployed Waku service.
The Waku Network
The Waku Network is one shared network built from the protocol family. Its documentation describes traffic sharded across eight pubsub topics, with automatic shard selection based on the content topic of each message. It also describes services for resource-restricted nodes.
The documentation page reviewed for this article does not show a publication date. Treat the count of eight as the configuration described at the time of that source, not as a permanent property of the protocol.
Best Value
Implementations
Waku is modular and not tied to one language. The architecture documentation names the following reference and integration implementations.
| Implementation | Language or environment | Role |
|---|---|---|
| nwaku | Nim | Reference implementation |
| go-waku | Go | Integration for Go applications |
| js-waku | JavaScript | Browser environments |
SDKs also exist for several other platforms. Before setting up a node or client, check each project’s repository for its current version and release status. Version numbers in older documentation may no longer match what is current.
Waku compared with blockchains and storage networks
Waku is often mistaken for a blockchain because of the decentralized-application context. The two solve different problems. A blockchain records shared state and transactions. Waku moves messages between peers. Messages sent over Waku do not need to be on-chain transactions, and sending them carries no gas fee, according to the FAQ.
Waku is also not a storage network. If your application needs data to last, or needs large files kept available over time, choose a storage system designed for that job.
Before you build on Waku
- Confirm the current documentation and implementation versions. The sources reviewed for this article are from 2024, and the network description is undated.
- Add payload encryption at the application layer. Transport protection alone does not hide message content.
- Plan for light clients to depend on service peers for Filter, Light Push and Store.
- Do not use Store as your only copy of important messages.
With those points in mind, Waku is best understood as messaging plumbing for decentralized applications: useful for short, real-time traffic, and not a complete privacy solution or a database.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
