2025-05-12 Waku Weekly

Highlights §

• nwaku: Deprecation of sync/local Merkle tree completed.

The Waku team met up in Split, Croatia for a team off-site, where they explored the development of the protocol, discussed ongoing research, and connected with peers.

This event also offered the opportunity for Waku to align with other IFT projects and work closely with the Codex and Nomos teams on building out and refining the Logos tech stack.

RLN Mainnet §

• Implement RLN smart contract for paid, multilevel memberships

  • achieved: [research] reviewed related PR (merkle tree deprecation) and cleaned up own PR
  • next: [research] use waku-rlnv2-contract submodule to deploy new contract for testing in nwaku

• Testnet L2 with on-chain tree

  • achieved: [nwaku] Deprecate sync / local merkle tree
  • next: [nwaku] Move from epoch based gap to timestamp based

• RLNv2 Web management interface

  • blockers: [js-waku] update nwaku-compose

Foundation for Communities Optimization §

• Define and implement sharding for Communities messages
  • achieved: [chat] stage 1 communities in own shard

Hardening and scaling foundations for private chats §

• Specify private chat protocol

  • achieved:
    • [chat] reviewed the segmentation logic in status-go
    • [chat] setup nim-chat-sdk repo

• Private chat rate limit PoC

  • achieved: [chat] update the kv_store PR

Upgrade Waku for the Web §

• Scalable Data Sync in browser
  • next:
    • [js-waku] create participant state data structures
    • [js-waku] process all messages synchronously

Logos Web apps §

• Reliable Qaku & library
  • achieved:
    • [chat] Logos Core container & GH action: add Dockerfile to build logos-core in a container, add draft workflow
  • next:
    • [chat] Qaku
    • [chat] Logos Core example module

Explore Peer Discovery Gap §

• Mixnet PoC
  • achieved:
    • [research] fixed an issue where stream was left open at exit node. also helped debug similar issue in gossipsub mix poc.
    • [research] going through Nym whitepaper and understanding of SURB’s for replies.
  • next: [research] integrate reply for lightpush once SURB is ready (hopefully by next week)

Messaging API §

• Messaging API: js-waku
  • next:
    • [js-waku] event driven Filter API
    • [js-waku] improve messaging types and sharding

Maintenance H1 2025 §

• achieved:
  • [nwaku] Allow multiple rln eth clients
  • [nwaku] Avoid double relay subscription
  • [nwaku] Separate internal and CLI configurations
  • [nwaku] Fix addPeer behavior in peer manager
  • [js-waku] enable peer-exchange by default for LightNode
• next:
  • [js-waku] make README more useful for contributors
  • [js-waku] use yamux instead of mplex
  • [nwaku] Enhance error msgs libwaku
  • [nwaku] Fix nwaku does not relay lightpush message with peers in the mesh
  • [nwaku] Adapt lite-protocol-tester for Lightpush v3
• blockers: [js-waku] unskip interop tests

Acquire first 10 Customers §

• 5-10 Highly qualified leads
  • achieved:
    • [BD] Started talking with Across again, now that the founder is in the groupchat
    • [BD] Also talking to their devrel in parallel as i have known him for a while and he joined them some months ago
    • [BD] Pinged Think Agents (6079 ai), Mikey gave me the update that we will continue planning the waku implementation as soon as they ship the agent client
    • [BD] Pinged Seda, they are still working on v1 and waku would only be for v2