Using Waku’s Content‑Topic Bloom Filters to Cut Unwanted Traffic
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.
Loading…
ReadMeFeed / Community knowledge
#libp2p
Real questions. Useful conversations. Find the people who know your stack.
wakuHow Waku's Topic Filters Cut Bandwidth for Resource-Constrained Nodes
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's Store-and-Forward Gossip: Reliable Messaging When Peers Keep Disappearing
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.
Waku Store Architecture: Designing for Peer-to-Peer Offline Retrieval
Explore the architecture of Waku Store, a P2P persistence layer that enables offline message retrieval using local KV stores and cryptographic verification.
Reducing Bandwidth Waste with Waku v2 Topic Filtering
Learn how Waku v2 uses topic-based filtering at the relay level to reduce bandwidth waste and improve privacy in decentralized pub/sub networks.
Waku v2 meshsub heartbeat limits in high-churn production environments
Waku v2 uses libp2p gossipsub with meshsub for message propagation across the peer-to-peer network. While local development often runs with default heartbeat intervals, production deployments face higher peer churn and variable network conditions that can destabilize the mesh. The meshsub protocol relies on periodic heartbeat messages (IHAVE/IWANT) to mainta
Waku v2 store node retention boundaries and offline delivery guarantees
Waku v2 routes messages by content topic rather than recipient address, and store-and-forward nodes can retain messages for offline peers. However, retention is operator-configured rather than a protocol-wide guarantee, and delivery is best-effort. When no store node is available while a recipient is offline, a message may be dropped without retry. The unres
Interoperability of nwaku (Nim) and js-waku (JavaScript) on Waku v2 Store Protocol
Interoperability of nwaku (Nim) and js-waku (JavaScript) on Waku v2 Store Protocol The objective is to verify that a nwaku node can discover, connect to, and exchange messages with a js-waku node using the Waku v2 Store protocol when the js-waku node was offline during an upgrade, relying on its configured retention window. Key constraints include compatible