ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Explore how Waku v2 uses namespaced content topics and a combination of relay and store nodes to enable efficient, decentralized pub/sub routing.
How to choose Waku relay message TTL and cache size so WAN messages survive partitions without overwhelming relay memory.
A decision guide for Waku v2 message history: compare Relay-only, Relay+Store, and Relay+Filter+App persistence across node cost, availability, privacy, and operational complexity. Includes a concrete Docker-based validation to measure real resource trade-offs.
Explore how Waku Relay uses stateless forwarding and TTL mechanisms to enable low-latency decentralized messaging without the overhead of local storage.
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.
waku