Local paper copy saved as: research/crypto/whitepapers/waku-modular-p2p-protocols-2022.pdf
Key takeaways from primary sources
Waku is most useful as decentralized messaging infrastructure, not as a blockchain, wallet, or storage system. The docs explicitly say this and emphasize short-lived, privacy-focused communication for Web3 applications.
The protocol family is intentionally modular. Relay, RLN Relay, Filter, Store, and Light Push break the communication problem into separate functions so applications can choose different privacy / bandwidth / persistence tradeoffs instead of inheriting one rigid transport model.
RLN Relay is an especially important mechanism because it turns anti-spam into an explicit economic and cryptographic control surface rather than leaving it to central gateway moderation or social reputation alone.
The docs make clear that Store does not guarantee strong data availability and is mainly for missed-message retrieval. That means Waku should be compared to transport and coordination layers, not to durable decentralized storage networks.
The nwaku materials show that operators can selectively support different protocols and resource profiles. This implies practical authority can concentrate in relay / store topology, light-node dependency patterns, and the operators that serve constrained clients.
The research repo and arXiv paper reinforce that Waku’s design target is heterogeneous nodes, mobile / browser compatibility, mostly-offline retrieval, and censorship resistance. That makes it a useful comparison case for app-coordination layers that sit below wallets, state channels, social apps, and offchain coordination systems.
The current waku.org website now redirects into the broader Logos technology stack, where messaging appears as a module alongside blockchain and storage. That branding change matters because it suggests the communication layer is now being packaged as one subsystem in a larger modular privacy stack rather than standing alone.
Mechanism lens
Best current classification: decentralized messaging protocol / private transport infrastructure / spam-resistant peer-to-peer coordination layer.
Closest comparison classes in the current corpus:
Ceramic for decentralized application data transport, but Ceramic is more event-state and query-pipeline oriented while Waku is more ephemeral transport oriented.
wallet / intent coordination standards for how offchain coordination can shape user experience and authority, but Waku lives lower in the transport stack.
storage systems like Codex, Storacha, or Filecoin only as negative comparisons: Waku is not trying to be durable storage.
Reusable insight: once communication is modularized into relay, spam control, filtering, historical retrieval, and light-client publishing, authority can migrate into topic standards, membership / anti-spam systems, and operator topology even without a traditional blockchain governance surface.
Whitepaper / docs status
Waku has both live docs and a formal research paper.
For this pass, the docs were the clearest source for current protocol roles, while the paper was best for the explicit framing of the architecture and design goals.
Local paper path: research/crypto/whitepapers/waku-modular-p2p-protocols-2022.pdf