roadmap/content/waku/updates/2024-10-28.md

title	tags	date
2024-10-28 Waku Weekly	waku-updates	2024-10-28

Milestone - Store Service Upgrade

• Store v3 - store synchronisation

  • achieved:
    • [research] Waku sync 2.0 POC
    • [research] Debugged some issues with store sync
  • next:
    • [research] abstraction refinements and serde optimization
    • [research] Continue with store sync testing

• PostgreSQL Maintenance

  • achieved: [nwaku] chore: dbconn - allow uuid in requestId by allowing hyphen
  • next: [nwaku] Reach a conclusion on whether we need time-sortable msgHash chore: make the msg hash time-sortable

Milestone - Direct Message Reliability

• Tooling: filter and light push protocols

  • achieved:
    • [nwaku] New repository lpt-runner is now public and capable to ease configuration and running tests on any waku network.
    • [nwaku] New build and deployment job is created for lite-protocol-tester
  • next: [nwaku] chore: add dashboard for liteprotocoltester runs

• Reliability Protocol for Resource-Restricted Clients

  • achieved: [nwaku] nwaku implementation of the new lightpush protocol version ready
  • next: [nwaku] Lightpush v2: libp2p extension is being developed, rebase needed after vendor bumps for v0.34.0 is ready feat: Enhance lightpush protocol error handling

Milestone - End-to-end reliability protocol

• End-to-end reliability protocol - Status integration
  • achieved: [research] rolling bloom filter in nim, thread safety, logging and helper functions for API
  • next: [research] get feedback and iterate on bloom filter & core functions of API

Milestone - RLN Mainnet

• Public dogfooding RLNaaS web app
  • achieved: [js-waku] filter subscription flakiness on cold start bug: filter subscription is not working on cold start
  • next:
    • [js-waku] working on user facing dogfooding app [Subtask] Create user facing dogfooding app
    • [js-waku] limit max amount of open connections to prevent spamming of TWN
    • [js-waku] encapsulate filter subscription logic into separate entity and make it reactive to network changes feat: maintain max open connection & prune unhealthy connections from peer store
    • [js-waku] enhance peer management with better coupling with connection objects and disposal of it feat: improve peer manager and re-integrate to light push

Milestone - Scale up number of Communities

• Usage of Rendezvous
  • blockers: [research] waiting on new nim-libp2p version

Milestone: Nwaku in Status Desktop

• Nwaku in Status Desktop

  • achieved:
    • [nwaku] chore: add to libwaku peer id retrieval proc
    • [nwaku] chore: updating available procs in golang example
    • [nwaku] chore: decreasing wait time for updating px cache on startup
    • [nwaku] fix: peer exchange libwaku response handling
    • [nwaku] feat(nwaku)_: message publisher and sent verifier
    • [nwaku] feat(nwaku)_: storenode requestor for missing message retrieval and result iterator impl
    • [nwaku] refactor: use protobuffer for API storenode queries
  • next:
    • [nwaku] refactor: extract ping interface
    • [nwaku] feat(libwaku): ping peer
    • [nwaku] Support for discovery of circuit-relay peers

• Nwaku on Windows

  • achieved:
    • [nwaku] feat: windows support
    • [nwaku] Add a counter for the remaining proofs per epoch in the dashboard. chore: create new RLN Grafana panel that counts the number of attached proofs per light client
    • [nwaku] Able to create wakunode2 executable (.exe) of wakunode2. feat: windows support
    • [nwaku] Automate build as much as possible and cross-platform support
  • next: [nwaku] Further Dogfooding of windows support and remove waku_sync bypass.

Milestone: Incentivise running a Waku infrastructure node

• Service Incentivisation - Service incentivisation roadmap & spec
  • achieved: [research] preliminary roadmap for RLN contract mainnet deployment on Linea [Deliverable] Deploy RLN smart contract to a L2 mainnet
  • next: [research] service incentivization spec update for PoC

Milestone: Bandwidth optimization and protocol review

• Review usage of content topics in Status Chat and Communities protocol
  • achieved: [research] addressed all flows in first phase of single content-topic usage in status communities. dogfooding is also complete. feat_: use a single content-topic for all community chats
  • next: [research] address review comments(if any) and start working on second phase change of single content-topic usage in communities

Milestone: Demonstrate product-market fit

• Define potential USPs

  • achieved: added more info to the validation matrix
  • next: continue using information from prospect calls to populate it

• Define target customers

  • achieved: talking with 3 teams for potential events where we can have a targeted audience in the web3 social, intents and AI verticals
  • next: deciding whether to sponsor any of these events or not

Other Work

Maintenance

• achieved:
  • [nwaku] chore: Update prepare_release.md to add js-waku update
  • [nwaku] chore: peer_manager - prevent too intense loop when no peers connected
  • [nwaku] chore: saving peers enr capabilities
  • [nwaku] feat: missing messages in the last hour
• next:
  • [nwaku] prepare Rust app for devcon workshop
  • [nwaku] Bump vendor dependencies for release 0.34.0 Vendor version upgrades are finished - major achievement having latest web3, eth and libp2p libraries in nim-waku. Under review and testing.
  • [js-waku] upgrade e2e test to facilitate latest nwaku chore: upgrade nwaku to 0.33.0 and check interop tests