ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Frameworks & web · #waku
Explore the architecture of Waku Store, a P2P persistence layer that enables offline message retrieval using local KV stores and cryptographic verification.
Learn how Waku v2 uses topic-based filtering at the relay level to reduce bandwidth waste and improve privacy in decentralized pub/sub networks.
A diagnostic guide for troubleshooting silent message delivery failures in Waku, focusing on topic filter mismatches, relay propagation, and version compatibility.
Waku's RLN Relay uses zero-knowledge rate-limiting nullifiers to stop spam in a permissionless pub/sub network — exceeding your message rate exposes your own secret key. Here's how it works and what it costs.
Gossip Propagation and Sequencing Waku employs a decentralized gossip-based protocol to propagate messages across a peer-to-peer network. While the store-and-forward mechanism ensures that offline peers can eventually retrieve missed data, the protocol does not natively guarantee a global deterministic order for message arrival across varying network topolog
Waku Store provides historical message retrieval from a local database on full nodes. The protocol defines the store query interface but does not mandate retention duration, pruning intervals, or resource caps. Retention, pruning and max peer settings are implementation choices, so behavior differs across clients and deployments. The design goal is to operat
Dial timeout due to private IP advertisement in Waku Relay When a Waku Relay node is started with the default bootstrap list and no explicit public address, it successfully discovers peers via mDNS in a local test environment but, in a production deployment, logs show a dial timeout or missing address error because the node continues to advertise only privat