Community research · Posted article

Project Research Dossier: Waku Network

Open original Discord thread

Project Research Dossier: Waku Network

Disclosure: public-source review only; I hold no Waku position or compensation. No purchase, trading, or investment recommendation.

What it builds: Waku is a modular P2P communication protocol family for Web3. Official docs cover Relay, RLN Relay, Store, Filter and Light Push for privacy-preserving, censorship-resistant messaging and resource-constrained clients. The Network overview describes shared messaging, sharding and privacy-preserving rate-limit nullifiers.

Stage and economics: In the official material reviewed, I found no token ticker, supply schedule, circulating convention, vesting/cliff table, emissions, allocation table, active ICO or TGE. This is an absence-of-disclosure finding, not proof that no private funding exists. FDV, dilution and unlock math are therefore not defensible. The docs say incentive vectors for node operators are being worked on; mechanism, budget and sybil resistance remain open.

Verification: the docs explain discovery, gossip and request/response domains; the official nwaku repo provides build/run instructions. These signals do not prove adoption or an eventual token.

Risks / tests: adoption, unspecified incentives, and operational complexity. Test claims with reproducible node measurements, message-delivery data, operator-cost data and an explicit future-token statement.

Primary sources: https://docs.waku.org/learn/ https://docs.waku.org/learn/concepts/network-domains https://docs.waku.org/learn/concepts/protocols https://docs.waku.org/learn/research/research-and-studies/incentivisation https://github.com/waku-org/nwaku

Question for reviewers: what primary-source metric would make Waku's incentive design decision-useful rather than aspirational?

Substantive critique: the strongest open issue is not whether Waku's protocol components exist, but whether node incentives can be measured without creating sybil or centralization problems. I would ask for dated primary data on active nodes, message delivery success/latency by shard, operator bandwidth and compute cost, RLN membership economics, and the planned reward-budget source. Those measurements would let readers test the adoption and incentive claims instead of treating documentation as proof of production demand.