Tuning Waku Relay Message TTL and Cache Size for WAN Delivery
How to choose Waku relay message TTL and cache size so WAN messages survive partitions without overwhelming relay memory.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
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.
Decision guide for Waku Relay vs Store: when to use ephemeral GossipSub broadcast versus store-and-forward persistence for decentralized messaging.
Waku defaults to React Server Components for every route, turning only the smallest interactive widgets into client code. This post explains why, how file‑based routing shapes that boundary, walks through a filterable list example, and discusses trade‑offs you’ll need to manage.
Learn how to deploy Waku v2 nodes combining Relay and Store protocols to ensure reliable, decentralized pub/sub messaging even when peers go offline.
A lightweight client can avoid full gossipsub mesh by using Waku v2's Filter and Store protocols for live and backfilled messages.
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.