Efficient Topic Filtering in Waku v2 for Lightweight Nodes
Waku v2 lets lightweight nodes subscribe to specific topic hashes via gossipsub, reducing bandwidth while preserving reliable delivery in decentralized apps.
Loading…
ReadMeFeed / Community knowledge
#gossipsub
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 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 topic filter subscriptions stop matching after upgrading past v0.24
Symptom After upgrading Waku nodes from a pre-v0.24 release, subscriptions that previously matched published messages no longer deliver them, even though the topic names and publisher code are unchanged. The goal is to restore selective delivery on topic-based pub/sub without falling back to receiving every message on the Gossipsub subgraph. Context and cons