2025-02-03 Waku Weekly

Milestone - Messaging API §

• Messaging API: js-waku
  • next:
    • [js-waku] speed up core operations by avoiding PeerStore
    • [js-waku] fix health state management and make it lighter

Milestone - Scale one-to-one chats and app protocols §

• Specify one-to-one protocol stack
  • next: [chat] documenting one-to-one content topics

Milestone - Store Service Upgrade §

• Store v3 - store synchronisation
  • achieved: [research] last minute bug fixes and PRs merged
  • next: [research] shard support, coordinating fleet testing

Milestone - Direct Message Reliability §

• Reliability Protocol for Resource-Restricted Clients
  • next:
    • [nwaku] nwaku implementation of the new lightpush protocol version
      • nim-libp2p extension is under development feat: Enhance lightpush protocol error handling
        • Optimizing observers for better performance.
        • Proper error reporting from publish
    • [nwaku] PRs to both nwaku and nim-libp2p will be added shortly.
• PostgreSQL Optimisation phase 1
  • achieved: [nwaku] chore: waku_archive add protection against queries longer than 24h

Deploy RLN onchain tree on L2 Testnet §

• Public dogfooding RLNaaS web app

  • achieved:
    • [js-waku] add particular node to be used for Store
    • [js-waku] make peer management and filter subscriptions event driven and lighter
  • next: [nwaku] deprecate tree sync strategy chore(rln-relay): deprecate tree sync strategy

• Implement RLN smart contract for paid, multilevel memberships

  • achieved:
    • [research] published a forum post with multisig suggestion (https://forum.vac.dev/t/multisig-for-rlnv2-contract/429)
    • [research] planned the work required for integrating new contract in nwaku
  • next:
    • [research] continue multisig discussion
    • [research] update contract address in nwaku and verify

• RLNv2 Web management interface

  • next: [js-waku] migrate to RLNv2 contract

Upgrade Waku for the Web §

• Scalable Data Sync in browser
  • achieved: [js-waku] port probabilities table and BloomFilter constructor from nim-sds
  • next: [js-waku] implement double-hashing strategy for BloomFilter hash functions

Milestone: Nwaku in Status Desktop §

• Nwaku in Status Desktop
  • achieved:
    • [nwaku] Fixed nwaku compilation as a dependency of status-desktop: https://github.com/waku-org/nwaku/pull/3262
    • [nwaku] Merged https://github.com/waku-org/nwaku/pull/3234 and https://github.com/waku-org/waku-go-bindings/pull/16
    • [nwaku] Created https://github.com/status-im/status-desktop/pull/17134 and https://github.com/status-im/status-go/pull/6283 in status-desktop and status-go respectively, to develop the integration of status-go with nwaku into status-desktop
    • [nwaku] Was able to start a status-desktop which uses nwaku through the waku-go-bindings. The node starts and relays messages but a few seconds after logging in it has an error related to concurrency and the application crashes with a segfault
  • next: [nwaku] Investigate, fix crash, and continue with the integration of waku-go-bindings into status-desktop

Logos Web Apps §

• Reliable Qaku & library
  • achieved: [chat] Discussion with Comms and new UI design

Maintenance H1 2025 §

• achieved:
  • [nwaku] chore: move mount store before relay and rln relay
  • [nwaku] Enhance filter issues (needed by Railgun) - facing test issues
    • bug: filter service node creates a new stream for every single message
    • bug: filter not accepting more subscriptions under moderate usage
  • [nwaku] Fixed interop tests after merging PR using message hash as a hex string chore: updating the hash-computing function to use hex
  • [js-waku] fix CI jobs failures and hangouts
  • [js-waku] fix naming of test reporting jobs
• next:
  • [nwaku] New v.35.0 release
  • [nwaku] js-waku - nwaku interoperability test stabilization
  • [js-waku] js-waku interoperability investigations