2024-05-15 Waku Weekly

Research Milestones §

Store Incentivisation

• Status: In Progress
• Project: https://github.com/orgs/waku-org/projects/17
  • in-progress:
    • [nwaku] feat: experimental incentivize store protocol

RLN in resource-restricted clients

• Status: In Progress
• Project: https://github.com/orgs/waku-org/projects/18/views/1
  • achieved: PR for message validation in lightpush before relaying.
  • next: continue lightpush attaching RLN proofs to messages received from clients.

RLNv2

• Status: In Progress
• Project: https://github.com/orgs/waku-org/projects/21/views/1
  • achieved: Test implementation WIP.
  • next:
    • Continue planning for next waku fork (RLNv2 + onchain root/proofs) See: https://github.com/waku-org/research/issues/96 (future section). RLN v2 testing. New smart contract with both features. Prepare presentation for DLT conference.
    • Test implementation continued and testing.

Store v3 - Waku Sync

• Status: In Progress
• Project: https://github.com/orgs/waku-org/projects/20/views/1
  • achieved:
    • Explored if there is a way to prune the negentropy storage based on timestamp.
    • Ttype state machine implementation and pruning mechanism.
  • next:
    • write subrange wrappers for negentropy and use subranges to sync.
    • using hashes to fill the archive with the missing messages.

Store v3 - message hashes

• Status: In Progress
• Project: https://github.com/orgs/waku-org/projects/16/views/1
  • achieved:
    • bug fixes
  • next:
    • fix compatability with Waku sync

Engineering Milestones §

Composing Waku Protocols to Improve Reliability

• Status: In Progress
• Project: https://github.com/orgs/waku-org/projects/9/views/1
  • completed:
    • [js-waku] refine Filter
    • [js-waku] chore: protocol implementations in @waku/core should be as unopinionated as possible
    • [js-waku] feat: SDK for redundant usage of filter/lightpush
    • [js-waku] bug: lightPush is not able to keep node connections
    • [js-waku] https://github.com/waku-org/js-waku/issues/2002
  • in-progress:
    • [js-waku] feat: peer management for protocols (with disconnection management)
  • next:
    • [js-waku] investigate suspended js-waku in suspended mode

DOS protection for req-res protocols and metrics

• Status: In Progress
• Project: https://github.com/orgs/waku-org/projects/11/views/1
  • completed:
    • [nwaku] chore: Address more attack vectors in rate limiting non-relay protocols
  • in-progress:
    • [nwaku] feat: Rate limit phase#3 - peer request rate registration and prioritization
    • [nwaku] feat: Proper bandwidth metrics per shard
    • [nwaku] feat: Enforce service specific rate limits
  • next:
    • [nwaku] feat: Failsafe mechanism (guide) for BW limiting

Bindings

• Status: In Progress
• Project: https://github.com/orgs/waku-org/projects/6/views/6
  • [nwaku] chore: support setting DiscV5 and DNS-discovery in libwaku

Other Work §

Bugs §

In Progress §

• [js-waku] feat: map/use correct bootstrap nodes fleet according to the configured pubsub topic
• [js-waku] test: create scripts for running light-push/filter and measuring ratio of messages sent and received
• [nwaku] bug: flaky test fails on MacOS
• [nwaku] bug: nwaku <> js-waku interop tests failing
• [nwaku] bug: Peer Reconnection not working?
• [nwaku] bug: build error on new AMD cpu’s (ubuntu 22.04 LTS)
• [nwaku] bug/regression: node ca be started on multiple clusters

Next §

• [js-waku] bug: ApplicationInfo to PubsubTopic doesn’t take clusterId into consideration
• [nwaku] bug: Deserialization error on POST /relay/v1/auto/messages with ephemeral field in body
• [nwaku] bug: running testwaku can hang in some cases of UPnP or nat-pmp networking
• [nwaku] bug: Store REST API returns invalid digest
• [nwaku] bug: autosharding resolves content topics to wrong shard

Enhancements §

In Progress §

• [js-waku] feat: map/use correct bootstrap nodes fleet according to the configured pubsub topic
• [nwaku] feat: light protocol tester application

Next §

• [js-waku] feat: improve reuse of pubsub/content topic configuration
• [js-waku] feat: better developer experience
• [nwaku] feat: RLN-proofs as a lightpush service
• [nwaku] Add a flag to require minimum number of peers to publish a message on relay

Ecosystem Development §

BD §

• Qualified two leads
• Advanced one lead toward deal
• Set up two meetings with potential partners

Dev Rel §

• The Waku Network hit 500 nodes - yay!
• Events page update
• The Graph blog article draft
• The Graph interview

Comms and Events §

• X: +489
• Linkedin: +7
• Discord: +44
• Waku intro finalized - https://www.youtube.com/watch?v=nIWx5Vp_Qxk
• 2 “how to run nodes” tutorials went live
• Published Montly newsletter
• Railgun interview went live
• Builder Spotlight went live

Docs §

• Implemented a script on waku.org for automatic creation and updating of the specs section
• Submitted a pull request to the specs repository to fix broken links and adjust the front matter
• Got the specs repo PR approved and merged Follow up with Hanno on RFC website plans Added high level overview of waku simulation results