add waku weekly 20240515

This commit is contained in:
chair28980 2024-05-14 23:20:30 -07:00
parent 49523f9f7e
commit 5643c47b75
1 changed files with 147 additions and 0 deletions

View File

@ -0,0 +1,147 @@
---
title: 2024-05-15 Waku Weekly
tags:
- waku-updates
date: 2024-05-15
---
## Research Milestones
[Store Incentivisation](https://github.com/waku-org/pm/milestone/23)
- Status: In Progress
- Project: https://github.com/orgs/waku-org/projects/17
- in-progress:
- [nwaku] [feat: experimental incentivize store protocol](https://github.com/waku-org/nwaku/issues/1961)
[RLN in resource-restricted clients](https://github.com/waku-org/pm/issues/159)
- 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](https://github.com/waku-org/pm/issues/163)
- 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](https://github.com/waku-org/pm/milestone/21)
- 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](https://github.com/waku-org/pm/milestone/20)
- 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](https://github.com/waku-org/pm/issues/114)
- Status: In Progress
- Project: https://github.com/orgs/waku-org/projects/9/views/1
- completed:
- [js-waku] [refine Filter](https://github.com/waku-org/js-waku/issues/1890)
- [js-waku] [chore: protocol implementations in @waku/core should be as unopinionated as possible](https://github.com/waku-org/js-waku/issues/1886)
- [js-waku] [feat: SDK for redundant usage of filter/lightpush](https://github.com/waku-org/js-waku/issues/1463)
- [js-waku] [bug: lightPush is not able to keep node connections](https://github.com/waku-org/js-waku/issues/1966)
- [js-waku] [https://github.com/waku-org/js-waku/issues/2002](https://github.com/waku-org/js-waku/issues/2002)
- in-progress:
- [js-waku] [feat: peer management for protocols (with disconnection management)](https://github.com/waku-org/js-waku/issues/2002)
- next:
- [js-waku] [investigate suspended js-waku in suspended mode](https://github.com/waku-org/js-waku/issues/2000)
[DOS protection for req-res protocols and metrics](https://github.com/waku-org/pm/issues/66)
- 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](https://github.com/waku-org/nwaku/issues/2589)
- in-progress:
- [nwaku] [feat: Rate limit phase#3 - peer request rate registration and prioritization](https://github.com/waku-org/nwaku/issues/2683)
- [nwaku] [feat: Proper bandwidth metrics per shard](https://github.com/waku-org/nwaku/issues/1945)
- [nwaku] [feat: Enforce service specific rate limits](https://github.com/waku-org/nwaku/issues/2032)
- next:
- [nwaku] [feat: Failsafe mechanism (guide) for BW limiting](https://github.com/waku-org/nwaku/issues/1946)
[Bindings](https://github.com/waku-org/pm/issues/121)
- Status: In Progress
- Project: https://github.com/orgs/waku-org/projects/6/views/6
- [nwaku] [chore: support setting DiscV5 and DNS-discovery in libwaku](https://github.com/waku-org/nwaku/issues/2455)
## Other Work
### Bugs
#### In Progress
- [js-waku] [feat: map/use correct bootstrap nodes fleet according to the configured pubsub topic](https://github.com/waku-org/js-waku/issues/2011)
- [js-waku] [test: create scripts for running light-push/filter and measuring ratio of messages sent and received](https://github.com/waku-org/js-waku/issues/2007)
- [nwaku] [bug: flaky test fails on MacOS](https://github.com/waku-org/nwaku/issues/2701)
- [nwaku] [bug: nwaku <> js-waku interop tests failing](https://github.com/waku-org/nwaku/issues/2621)
- [nwaku] [bug: Peer Reconnection not working?](https://github.com/waku-org/nwaku/issues/2592)
- [nwaku] [bug: build error on new AMD cpu's (ubuntu 22.04 LTS)](https://github.com/waku-org/nwaku/issues/2560)
- [nwaku] [bug/regression: node ca be started on multiple clusters](https://github.com/waku-org/nwaku/issues/2552)
#### Next
- [js-waku] [bug: ApplicationInfo to PubsubTopic doesn't take clusterId into consideration](https://github.com/waku-org/js-waku/issues/1902)
- [nwaku] [bug: Deserialization error on POST /relay/v1/auto/messages with ephemeral field in body](https://github.com/waku-org/nwaku/issues/2643)
- [nwaku] [bug: running testwaku can hang in some cases of UPnP or nat-pmp networking](https://github.com/waku-org/nwaku/issues/2628)
- [nwaku] [bug: Store REST API returns invalid digest](https://github.com/waku-org/nwaku/issues/2615)
- [nwaku] [bug: autosharding resolves content topics to wrong shard](https://github.com/waku-org/nwaku/issues/2538)
### Enhancements
#### In Progress
- [js-waku] [feat: map/use correct bootstrap nodes fleet according to the configured pubsub topic](https://github.com/waku-org/js-waku/issues/2011)
- [nwaku] [feat: light protocol tester application](https://github.com/waku-org/nwaku/issues/2700)
#### Next
- [js-waku] [feat: improve reuse of pubsub/content topic configuration](https://github.com/waku-org/js-waku/issues/1814)
- [js-waku] [feat: better developer experience](https://github.com/waku-org/js-rln/issues/76)
- [nwaku] [feat: RLN-proofs as a lightpush service](https://github.com/waku-org/nwaku/issues/2593)
- [nwaku] [Add a flag to require minimum number of peers to publish a message on relay](https://github.com/waku-org/nwaku/issues/1004)
## 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](https://github.com/waku-org/waku.org/pull/76#issuecomment-2090271892) plans Added high level overview of waku simulation results