roadmap/content/waku/updates/2024-08-19.md

title	tags	date
2024-08-19 Waku Weekly	waku-updates	2024-08-19

Milestone - Store Service Upgrade

• Store v3-beta - Message Hashes

  • achieved:
    • [research] Refined testing tools and query criteria for benchmark tests
    • [research] Obtained insightful data from store queries on the status.prod system
  • next:
    • [research] run some more queries and discuss findings
    • [research] run benchmark tests on isolated system and summarise findings

• Store v3 - store synchronisation

  • achieved:
    • [nwaku] PR merged to add Waku Sync Nwaku Sync
  • next:
    • [nwaku] Deploy an image with Waku Sync into status.staging to start the dogfooding

• PostgreSQL Maintenance

  • achieved:
    • [nwaku] Deployed a version in status.prod with hash query optimized Optimize hash queries with lookup table
    • [nwaku] Endurance of partition deletion faster retention policy when error and use of detach finalize when needed

Milestone - Direct Message Reliability

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

  • achieved:
    • [chat] limit the maximum number of message hashes by query hash
    • [chat] limit the maximum number of message hashes to request per query

• Reliability Protocol for Relay

  • achieved:
    • [nwaku] Almost completed implementation for filter enhance reliability thanks to StoreV3
  • next:
    • [nwaku] Carry on with filter and lightpush reliability-store awareness

Milestone - End-to-end reliability protocol

• End-to-end reliability protocol - PoC
  • achieved:
    • [research] PR approved and addressed review comments. POC dogfooding in progress. Identified and fixed a certain deadlock issue with new node joining the network.
  • next:
    • [research] share dogfooding doc, start exploring status-go for API spec

Milestone - Static Sharding - dedicated shards

• Sharding peer management and discovery hardening
  • achieved:
    • [nwaku] Tested different profilers to help us find the root cause of node getting stuck and missing messages
    • [nwaku] Supported nim-libp2p team with yamux Futures leak
  • next:
    • [nwaku] analyze results after DST runs their simulations with profiling tools

Milestone - Scale 1:1 chat messages PoC

• Maturing RLN variables/parameters revision
  • achieved:
    • [research] RLN contract mainnet spec ready for review Add WAKU2-RLN-CONTRACT spec for mainnet deployment
  • next:
    • [research] continue the discussion around the PR, present at Status-Waku and Tokenomics calls

Milestone - Scale up number of Communities

• Usage of Rendezvous
  • achieved:
    • [research] namespace, wrapper update
  • next:
    • [research] waku rendezvous spec
  • blockers:
    • [research] libp2p rendezvous limit what can be done at waku layer

Other Work

Enhancements

• achieved:
  • [chat] move outgoing message check from status-go to go-waku, extract message hash query for outgoing messages to go-waku
  • [chat] add sender api for publish messages with additional check chore: refactor sender api
  • [chat] move filter manager from status-go to go-waku, move filter mgr to go-waku
  • [chat] rebase gossipsub from libp2p update rebased gossipsub from libp2p, rebase from libp2p
  • [chat] chore: bump go-waku on status-go release branch to fix crashes: bump go-waku
  • [chat] refactor: remove status-im/rendezvous refactor: remove status-im/rendezvous
  • [nwaku] reviewed max-relay-peers configuration, added and tested a fix improving the connection management pruning excess in relay connections and closed review max-relay-peers config attribute in wakunode2
  • [nwaku] updated dependencies for release v0.32.0
  • [nwaku] Building a functional application to analyze the peer_exchange protocol on a remote node.
  • [nwaku] Encountered issues with [switch ↔ node] connections, so transitioning to a [node ↔ node] setup for the same functionality (learning point.)
• next:
  • [nwaku] Resolve the PR exchange issue. failed to retrieve peer info via peer exchange protocol

Bugs

• achieved:
  • [chat] fix issue that causes log flooding in mobile where DNS is not resolvable add ticker to check peers and update connection status, add ticker to check peers and update connection status
  • [chat] fix for crash wrt peer count use corrected connected peer count and add check to avoid crash
  • [chat] ping interval related fixes ping interval fixes, ping interval
  • [chat] fix proper reporting of connection change to filter manager reporting connection change to filter manager
  • [chat] return on insert error
  • [chat] fix: panic on MessageQueue.Push, keep channels open
  • [chat] fix: memory leak while waiting for storenode available signal tmp remove subscription to mailserver available signal to avoid mem leak, wait for mailserver available signal to change missing messages criteria
  • [nwaku] bug cleaning: discussed action items and started implementing them for RLNv2 in dynamic mode imposed rate limit after the first message while and RLNv2 rate limit imposed sooner than expected