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
#waku-v2
Real questions. Useful conversations. Find the people who know your stack.
wakuTopic Versioning vs. In-Place Schema Updates for Waku v2 Payloads
Message Schema Evolution in Waku v2 When evolving the data structure of messages sent via Waku v2, developers must manage how peers with different Protocol Buffer definitions interpret the payload. Because Waku lacks a built-in schema registry or capability negotiation mechanism, schema changes can lead to decode failures or silent data corruption if field s
When a Waku filter subscription lapses, are missed messages replayed or dropped?
Goal: run an alert feed over Waku v2 where a light client subscribes via the filter protocol (13/WAKU2-FILTER) and receives only messages matching a narrow set of content topics — relevant alerts, minimal noise. Assume Waku v2; the v1 filter API differs and is out of scope. The filter protocol delegates content-topic matching to a service node, and subscript
Lightpush or Relay: Selecting a Default Publish Path for Bandwidth-Constrained Waku v2 Light Nodes
A Waku v2 light node on a mobile or metered connection must choose between two documented publishing mechanisms. Lightpush submits messages to a server that relays them, reducing outbound bandwidth and peer connections, while Relay gossips directly, avoiding trust concentration in a single operator and hiding the publish origin from any one server. The speci