2025-11-10 Waku Weekly

Highlights §

This past week, Waku team members along with Status, Codex and VAC contributors convened in Budapest, Hungary for a strategic offsite focused on architectural alignment, product direction, and cross-team coordination as we advance toward Logos consolidation and prepare for launch activities.

Key discussion areas included:

• API standardization across Waku implementations (Waku API, Waku App API, Waku Chat API)
• Integration strategies for Chat SDK with Status backend logic and SDS
• Advanced discovery mechanisms including DHT and metastable networks
• Service incentivisation coordination and architecture
• Security and cryptographic infrastructure (De-MLS, Sender Key, zerokit integration)
• Infrastructure and platform strategy (nwaku as a research platform, RPC as a service)
• Developer experience improvements (WebRTC for low latency, Codex integration)
• Product strategy for The Waku Network and ecosystem development
• Logos launch planning and hackathon retrospective

Incentivise running a Waku infrastructure node §

• [Deliverable] Service Incentivisation - Pay for RLN provision PoC

  • achieved: Offsite session on service incentivisation coordination and architecture alignment

• [Deliverable] Service Incentivisation - Service incentivisation roadmap & spec

  • achieved: Cross-team coordination session on service incentivisation strategy and implementation approach
  • next: Continue refining coordination mechanisms and payment protocol design based on offsite discussions

Integrate nwaku in status desktop relay mode only §

• [Deliverable] Nwaku in Status Desktop
  • achieved: Discussion on nwaku as a platform for research and Status integration strategy

Introduce E2E Reliability in Status Communities §

• [Deliverable] SDS protocol in Status - basic integration
  • achieved: Session on SDS integration with Chat SDK and Status backend boundaries

Improve DevEx: API, TWN, Metrics, Docs §

• [Deliverable] Introduce Waku API in the Browser

  • achieved: Deep dive sessions on Waku API, Waku App API, and Waku Chat API standardization across implementations
  • next: Continue API specification work incorporating offsite feedback on consistency and developer experience

• [Deliverable] Introduce Waku API in nwaku

  • achieved: Discussion on nwaku API development and research platform positioning

Introduce Mixnet For Message Sending §

• [Deliverable] Integrate libp2p mix into lightpush
  • achieved: Presented Waku Mix research and progress updates

Streamline DevEx: Mobile, Rust and Web dev §

• [Deliverable] Waku as a Signal Network (WebRTC) PoC
  • achieved: Discussion on WebRTC integration for low latency meshes in browser environments
  • next: Continue WebRTC signaling implementation incorporating offsite architectural feedback

Create Chat SDK MVP §

• [Deliverable] Chat SDK Developer Preview
  • achieved:
    • Session on Chat SDK vs Status backend logic, refining boundaries and integration points
    • Discussion on key storage and database passing patterns for Chat SDK
    • De-MLS architecture review for Chat SDK security model
  • next: Implement key takeaways from offsite architecture sessions

Formalize and Expand Waku Web Apps §

• [Deliverable] Forum PoC

  • achieved: Discussion on Opchan development and productizing The Waku Network

• [Deliverable] Reliable Qaku & library

  • achieved:
    • Session on dogfooding Qaku at scale to validate production readiness
    • Product strategy discussion on packaging and presenting TWN with Apple-grade polish
  • next: Implement learnings from scale testing discussions

• [Deliverable] Codex for message archival PoC

  • achieved: Discussion on Codex integration with Status Desktop for message archival

• [Deliverable] Web3 RPC fallback for service nodes

  • achieved: Session on RPC as a service over Waku architecture and implementation strategy

Acquire first 10 Customers §

• [Deliverable] 5-10 Highly qualified leads
  • achieved:
    • Ecosystem development update and strategic discussions
    • Product thinking for Logos session to align positioning and value proposition
    • Hackathon retrospective to identify improvements for future developer engagement

Harden RLN Testnet Deployment §

• Zerokit is used in the Browser for Credentials Management

  • achieved: Discussion on zerokit usage patterns for js-waku and nwaku implementations

• Implement basic discovery for mix

  • achieved: Session on discovery mechanisms including Waku DHT and metastable networks for improved peer finding

Extend Chat SDK with Group Conversations §

• [Deliverable] Aligning on Group chat prerequisites [MLS]
  • achieved:
    • Cross-team session aligning on group chat prerequisites with Chat and VAC-ACZ teams
    • Discussion on MLS integration strategy and sender key approaches
  • next: Implement MLS integration based on aligned prerequisites from offsite

Strategic Initiatives §

• achieved:
  • Logos consolidation discussions and cross-team alignment
  • Engineering practices presentation to establish team standards
  • Issue cleanup sessions across nwaku, js-waku, and chat-sdk repositories
  • Logos launch planning and open discussion
  • Product strategy discussions for The Waku Network positioning and go-to-market

Maintenance §

• achieved: Collaborative issue triage and cleanup across repositories to improve project health