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

4.3 KiB

title tags date draft
2024-01-08 Waku weekly
waku-updates
2024-01-08

2024-01-08 Waku weekly

Waku Network Can Support 10K Users

Targeted dogfooding for Status Communities

  • achieved: status-mobile dogfooding, debug and attempt to identify root cause of filter delay issue
  • achieved: attempt to identify root cause of filter delay issue, work on upgrading status-go to use Go 1.21 (to use latest go-libp2p), use latest go-waku version and identify missing commits between release and develop branch
  • next: continue dogfooding / fixing issues

Waku Network Gen 0 - 2023-12-01

1.5: Launch and dogfood integrated public Waku Network MVP

  • achieved: add new metrics and make go-waku-compose dashboard functional, dogfooding the network with go-waku node
  • next: fix few pending items in dashboard

Other Work

Enhancements

[nwaku] feat: Have additional Admin REST API endpoints that helps node operator in monitoring

  • achieved: got feedback about improved error handling. Added it to the code, got a segfault from the testing framework, investigated and found the root cause.
  • next: define how to proceed based on the testing issue and merge the PR

[nwaku] feat: Have additional Admin REST API endpoints that helps node operator in monitoring

  • achieved: improved initial implementation. Added unit tests, updated documentation, opened and got approved PR.
  • next: verify if there's other places where the new endpoint should be documented before merging

[waku-rust-bindings] Peer discovery & management

  • achieved: Added dns discovery parameters to the node config

[research] Sync store baseline understanding

  • achieved: 1-day work this week due to time off, nim implementation of Prolly trees
  • next: Diff protocol discussion, Sync mechanism on wire query protocol discussion, generating some operational data details such as memory consumption using RLN specs.

[go-waku] feat: parameterizable number of connections per IP

  • achieved: Maintain parity between nwaku and go-waku clients

Bugs

[nwaku] bug: sort order ignored in store nodes

  • achieved: created v0.23.1-rc.0 and deployed in status.test fleet.
  • next: Deploy v0.23.1 to both status.test and status.prod after having the approval from @richard-ramos and @mprakhov

[nwaku] bug: lack of error checking in publish

  • achieved: fixed compilation errors, got it to work and tested it
  • next: add test cases to the codebase and open PR

[go-waku] bug: filter/v2/subscriptions take a lot of time and even timeout sometimes

  • achieved:fix panic when static peer is also discovered dynamically, fix ENR Waku field population for Fitler, analyze data races identified

[go-waku] bug: update examples to use autosharding

  • achieved: update basic_relay example to use static and autosharding

Documentation

[go-waku] bug: update examples to use autosharding

  • achieved: update basic_relay example to use static and autosharding

[go-waku] chore: create docs for setting up a systemd service and exit codes

  • achieved: Added systemd template and docs
  • next: Add env variables suggested by infra

PM

[pm] Waku Research - Post Gen 0 Milestones and Epics

  • achieved: Significantly refined milestones and epics and started getting feedback from stakeholders
  • next: Further stakeholder engagement. Define work needed to improve RFC process.

Chores

[nwaku] Bump vendor dependencies for release 0.24.0

  • achieved: bump dependencies to prepare the v0.24.0.