Waku Update

  • 2024 Milestones have been defined, to be structured and prioritized this week, subject to change pending approval from stakeholders.
  • Remaining open TWN Gen 0 Milestone items to be priorirized in 2024 Milestones and Epics.

Waku Network Gen 0

Open Epics

January 29 Update

Waku’s development is divided among 6 teams: research, nwaku, go-waku, js-waku, chat-sdk, and ecosystem-development.

Research

rln-proof-witness Create RLN proof without having the whole tree

  • achieved:
    • Create proof of concept where light clients can generate their own rln proofs without having to sync the whole tree.
    • Dog food above PoC and get feedback
    • Start with rln in gossipsub paper

Waku Research - Post Gen 0 Milestones and Epics

TWN Connectivity

  • achieved: read Meridian paper and wrote how it could be used in TWN, reading on Discv5 topic advert design problems
  • next: discuss with VAC topic experts?

nwaku

feat: Enforce service specific rate limits

  • achieved: implemented a simple lightpush and store request rate limit with configurable defaults
  • next: prior PR need to finish some more tests

bug: access-control-allow-origin should be set to localhost

  • blocked: Eugen done a presto PR utilizing new chronos middleware design, added comments due we need some change on it prior able to use it.

feat: sharded peer management Round 2

  • achieved: added sharded peer management config flag, feedback
  • next: review & merge

chore: improved error handling when config uses cluster-id and pubsub topics

  • achieved: improved error handling for cluster and shard config
  • next: review & merge

bug: restart loop of current master

  • achieved: got feedback for the PR, implemented fix and merged

bug: RLN validator is only added for statically configured pubsub topics

  • achieved: analyzed issue, implemented a solution, tested and raised PR
  • next: get feedback on the PR, implement it and merge

feat: REST API - large messages does not seem to be rejected by relay auto api

  • achieved: investigated how to approach the issue using generalized validators, implemented a solution, tested and raised PR
  • next: get feedback on the PR, implement it and merge

go-waku

js-waku

Ecosystem-development

Community/Partners

Docs

Integrate benchmark and research into website

DevRel

  • achieved:
  • next:
    • complete all the tutorial videos
    • workshop presentations for ethlatam
    • more builder spotlight videos
    • calls with node operators

Status Integration

chat-sdk

  • achieved: started the conversation with Hanno on permission-less communities
  • next: agree on an approach on permission-less communities.
  • achieved: research and draft hash based message query to store node spec
  • next: discuss on the iteration of hash based message query