ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Frameworks & web · #waku
Learn how Waku Relay v2 uses SHA‑256 hashes and a Bloom filter to drop duplicate messages, saving bandwidth while preserving privacy guarantees that make Waku suitable for decentralized messaging.
Run a Waku Relay node with the Store plugin and verify that offline subscribers receive missed messages after reconnection.
Learn how to configure a Waku Relay’s store‑and‑forward feature so light clients can query recent messages after going offline, with a step‑by‑step example and notes on trade‑offs.
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.
Learn how to enable Waku Store for persistent messaging, configure a Go node with BadgerDB, publish and query messages, and understand storage limits and common pitfalls.
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.
Learn how to enable Waku Relay’s store‑and‑forward feature so offline subscribers receive messages after they reconnect.
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.
Learn how to implement asynchronous messaging in Waku using Relay nodes for store-and-forward delivery, ensuring data persistence for offline peers without compromising privacy.
docker