2024-07-08 Waku Weekly

Milestone - Store Service Upgrade §

• Store v3-beta - Message Hashes

  • achieved:
    • [research] take up reported bugfixes after afk; continue with service rollout
    • [chat] tuning store hash query to shorten the confirmation time of outgoing messages Reset MVDS epoch after peer is online
  • next:
    • [research] start with storev3 benchmarking test plan

• DOS protection for req-res protocols and metrics

  • achieved:
    • [Epic: nwaku] Node Bandwidth Management Features
      • BW metrics per shard: implemented per shard metric collection - feat: Proper bandwidth metrics per shard
      • Added dashboard panels for relay per shard traffic
      • Added dashboard panels for non-relay protocols data traffic
      • Added dashboard panels for non-relay protocols request rates
    • [nwaku] feat: Enforce service specific rate limits
      • Finalizing last phase of the feature:
        • Added per peer filtering of high users
        • Filter service specific limits for ping and subscribe per peer
  • next:
    • [nwaku] [Epic: nwaku] Node Bandwidth Management Features
      • Add distinction between gross/net inbound traffic of shards.
    • [nwaku] feat: Enforce service specific rate limits
      • finish testing, add more unit tests

• PostgreSQL Maintenance

  • achieved:
    • [nwaku] new issue to create sonda tool, a canary for store services: chore: create sonda tool
  • next:
    • [nwaku] start implementation of sonda tool

Milestone - Direct Message Reliability §

• Review connection management strategy and back-off and fix long disconnection issues

  • achieved:
    • [chat] feat: filter peers stored in cache by cluster-id in peer-exchange
    • [chat] feat: expose router and mesh peers to obtain list of peers in mesh
    • [chat] improve relay peer connectivity and refactor peerManager to support lightMode feat: modify peer-manager to consider relay target peers
    • [chat] enable peerExchange in relay for better peer discovery chore: enable pxClient in relay and increase relay peer connections
    • [chat] fix peerExchange peer source and enable peerExchange in lightClient fix: enable pxclient and filter peerExchange peers returned
    • [chat] query store node when back from sleep: missing communityRequestToJoin message
    • [chat] IMO of what to do regarding receive reliability: Receive message reliability for Status desktop
  • next:
    • [chat] expose rpc methods to obtain list of peers by topic, and list of peers in mesh
    • [chat] lightClient topic health reporting and peer connectivity improvements
    • [chat] when back online only request from store node since last time not 24 hours
    • [chat] investigate connection management for outgoing messages

• Tooling: filter and light push protocols

  • achieved:
    • [chat] optimize filter subscriptions by aggregating them feat: optimize filter subs and feat: aggregate filter subscriptions to do bulk subs with peer
    • [nwaku] stress test on waku-simulator
  • next:
    • [nwaku] add rln support
    • [nwaku] run lite-protocol-tester on shards.staging

• Reliability Protocol for Relay

  • achieved:
    • [chat] draft reliability for relay protocol spec feat: reliability for relay protocol
    • [nwaku] carry on with the implementation in nwaku - feat: enhance reliability thanks to StoreV3
  • next:
    • [chat] continue with the reliability protocol
    • [nwaku] submit first PR in nwaku - feat: enhance reliability thanks to StoreV3

• Reliability Protocol for Resource-Restricted Clients

  • achieved:
    • [nwaku] Accepted new lightpush protocol definition with detailed fail case support - Enhance light push protocol
    • [js-waku] filter uses dynamic peer management feat(filter): peer/subscription renewal with recurring Filter pings
    • [js-waku] reliability with renewals due to offline state feat!: improve offline state handling for Filter subscription
    • [js-waku] reliability RFC Add “req-res protocol reliability” spec
  • next:
    • [nwaku] Implement: feat: Enhance lightpush protocol error handlingwaku-org/nwaku/issues/2722
    • [js-waku] reliability RFC Add “req-res protocol reliability” spec
    • [js-waku] reliability with renewals due to offline state feat!: improve offline state handling for Filter subscription

• User apps for large scale dogfooding

  • achieved:
    • [js-waku] minor improvements to feat: add first version of dogfooding app and getting unblocked with latest nwaku release

• Review MVDS usage and fail path

  • achieved:
    • [chat] reset MVDS epoch after peer is back online Reset MVDS epoch after peer is online
  • next:
    • [chat] continue mvds review

Milestone - End-to-end reliability protocol §

• End-to-end reliability protocol - PoC
  • achieved:
    • [research] started exploring POC in go-waku as an example application
    • [research] researched Vac’s de-MLS protocol for possible integration
  • next:
    • [research] continue with the POC starting with a minimal working version first
  • blockers:

Milestone - Static Sharding - dedicated shards §

• Sharding peer management and discovery hardening
  • achieved:
    • [nwaku] added origin of peers in admin rest endpoint as per request, to debug and further understand discovery performance chore: adding origin to peers admin endpoint
    • [nwaku] discussed with nim-libp2p team and tested a version of logging errors on publish to understand how often messages are not sent without returning errors

Milestone - Scale 1:1 chat messages PoC §

• RLNv2 in nwaku

  • achieved:
    • [research] RLNv2 config for the Waku Network: chore: add TWN parameters for RLNv2
    • [research] bug fix in RLN, vulnerability: fix(rln): nullifierlog vulnerability
  • next:
    • [research] assist to deploy 0.30.0 release and integrate it in The Waku Network

• Maturing RLN variables/parameters revision

  • achieved:
    • [research] continuing the execution of RLN in resource-restricted network: [Epic: Dogfooding] Deliver RLN v2 + RLN in resource-restricted to The Waku Network
    • [research] simulations using the waku simulator for different purposes
    • [research] expanded RLNv2 testing, assisted with simulating and debugging vulnerabilities
  • next:
    • [research] assist to deploy 0.30.0 release and integrate it in The Waku Network
    • [research] complete execution of RLNv2 test scenarios

• Pay for RLN provision first PoC

  • achieved:
    • [research] added chain interaction to incentivization POC
  • next:
    • [research] draft a specification for RLN mainnet deployment

Other Work §

Enhancements §

• achieved:
  • [nwaku] deployment of release v0.30.1, which adds RLNv2
  • [js-waku] prepare for next release
• next:
  • [js-waku] release last reliability improvements

Bugs §

• achieved:
  • [chat] fix: panic due to enr having more than 300 bytes
  • [chat] fix: ignore ws from circuit relay addresses, and allow non multiaddresses in multiaddrs ENR key
  • [chat] fix failing wakuv2 tests
  • [nwaku] bug: build error on new AMD cpu’s
  • [nwaku] Various bug fixes:
    • From chat team:
      • bug: timestamp should be set to 0 if not provided in REST API
      • bug: Store REST API returns invalid digest
    • From Vac-QA:
      • bug: Some PeerStore metadata is not filled in
      • bug: PeerInfo instance affects listed protocols
      • bug: Lightpush’s publish type error
      • bug: Relay publish returns Failed to publish: timedout when a peer filter node is disconnected
      • bug: Test failure on test_all
      • handle rln_msg_limit issue
    • Nim 2.0 readiness:
      • [nwaku] bug: incorrect import paths pointing outside the repository
• next:
  • [nwaku] peer exchange returns nodes that no longer exist