Optimizing Decentralized Message Routing with Waku v2 PubSub
Learn how Waku v2 leverages libp2p PubSub to reduce message latency and implement content-type filtering for more efficient decentralized application routing.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Learn how Waku v2 leverages libp2p PubSub to reduce message latency and implement content-type filtering for more efficient decentralized application routing.
When a Waku node subscribes to a topic but never receives messages, the culprit is often a subtle misconfiguration. This guide walks through the most common causes, how to verify each one, and practical fixes to restore message flow.
Waku offers Relay for live gossip, Store for durable history, and Light Push for thin clients. This guide compares the layers, explains trade-offs, and shows how to validate each path.
Waku's Lightpush protocol filters relay traffic at each hop, cutting bytes on sparse topics but adding CPU cost and misconfiguration risk. Here is how it works and how to measure it locally.
Waku Store lets late-joining nodes retrieve message history from peer-run logs instead of a central server. Here's how it works, how to verify it locally, and what it costs.
Learn how Waku’s content‑topic bloom filters let lightweight clients subscribe only to the topics they need, reducing bandwidth with a predictable false‑positive rate.
Waku's topic-based subscription filter uses GossipSub's scored peer swarm to forward only matching messages, cutting bandwidth for mobile wallets and light clients. Exact-match filtering keeps evaluation O(1) but requires deliberate topic design.
Waku pairs GossipSub mesh relay with a store-and-forward protocol so peers that drop offline can catch up. Here is how the pieces fit, a minimal js-waku example, and the limits to plan around.
Explore the architecture of Waku Store, a P2P persistence layer that enables offline message retrieval using local KV stores and cryptographic verification.