roadmap/content/waku/updates/2024-04-26.md

158 lines
7.5 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

---
title: 2024-04-26 Waku Weekly
tags:
- waku-updates
date: 2024-04-26
---
## Research Milestones
[Store Incentivisation](https://github.com/waku-org/pm/milestone/23)
- Status: In Progress
- Project: https://github.com/orgs/waku-org/projects/17
- achieved: discuss incentivization with Akhil
- next: plan out incentivization PoC (Lightpush instead of Store?)
- blockers: (no longer a blocker) the deadline for the academic paper final version
[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: New Merkle tree integration (LazyIMT) integrated https://github.com/alrevuelta/go-waku-light/pull/2 and new version of contract using said tree https://github.com/vacp2p/rln-contract/pull/31 (with Ar. help). PoC ready to get Merkle proofs from the contract using the finally merged https://github.com/privacy-scaling-explorations/zk-kit/pull/162. With this tree, we can assume the increase in gas cost and in exchange we get roots and merkle proofs onchain.
- next: Continue work in go-waku-light and prepare an end to end PoC to showcase this new feature. Write a report with findings and tradeoffs for future reference.
- blocker: "VacRlnContract" is not compatible with "WakuRlnContract". This https://github.com/vacp2p/rln-contract/pull/31 should be adapted to work with waku nodes (required for the PoC). Awaiting Vac's support.
[RLNv2](https://github.com/waku-org/pm/issues/163)
- Status: In Progress
- Project: https://github.com/orgs/waku-org/projects/21/views/1
- achieved: merged PR to remove go-waku from waku-simulator
- next: update to RLNv2
- blockers: deployment still not working on wakusim host, but there is an issue for infra to debug and I can continue by using the wakudev host
[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
[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
## Status Integration
- Status: In Progress
- Project: https://github.com/orgs/waku-org/projects/5/views/2
- in-progress:
- [nwaku] [Add logging of hashes to all nodes](https://github.com/waku-org/nwaku/issues/2474)
## Engineering Milestones
[JSON RPC Deprecation](https://github.com/waku-org/pm/issues/125)
- Status: Completed
- Project: https://github.com/orgs/waku-org/projects/8/views/1
[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] [chore: protocol implementations in @waku/core should be as unopinionated as possible](https://github.com/waku-org/js-waku/issues/1886)
- in-progress:
- [js-waku] [feat: Store reliability](https://github.com/waku-org/js-waku/issues/1685)
[Operator Feature Requests](https://github.com/waku-org/pm/issues/152)
- Status: In Progress
- Project: https://github.com/orgs/waku-org/projects/13/views/1
- completed:
- [nwaku] [chore: detailed json report on /health endpoint](https://github.com/waku-org/nwaku/issues/2020)
- [nwaku] [chore: Extend node isReady with more mature checks and result returned](https://github.com/waku-org/nwaku/issues/2019)
[Bindings (Rust, NodeJS, Golang)](https://github.com/waku-org/pm/issues/121)
- Status: In Progress
- Project: https://github.com/orgs/waku-org/projects/6/views/6
- in-progress:
- [nwaku] [chore: migrate DiscV5 and DNS Discovery from app.nim to waku_node.nim](https://github.com/waku-org/nwaku/issues/2452)
- next:
- [nwaku] [chore: support setting DiscV5 and DNS-discovery in libwaku](https://github.com/waku-org/nwaku/issues/2455)
[Node Bandwidth Management Mechanism](https://github.com/waku-org/pm/issues/66)
- Status: In Progress
- Project: https://github.com/orgs/waku-org/projects/11
- in-progress:
- [js-waku] [feat: prefer error code for req-res protocol over exception](https://github.com/waku-org/js-waku/issues/1694)
## Other Work
### Bugs
#### In Progress
- [js-waku] [bug: lightPush is not able to keep node connections](https://github.com/waku-org/js-waku/issues/1966)
- [js-waku] [bug: remote peer fault](https://github.com/waku-org/js-waku/issues/1961)
- [js-waku] [bug: filter subscription stops without occasional pings](https://github.com/waku-org/js-waku/issues/1923)
- [nwaku] [bug: wakunode2 systemd unit restarts about 10-15x per day](https://github.com/waku-org/nwaku/issues/2173)
- [nwaku] [bug: SIGSEGV with RLN](https://github.com/waku-org/nwaku/issues/1934)
- [nwaku] [bug: build error on new AMD cpu's (ubuntu 22.04 LTS)](https://github.com/waku-org/nwaku/issues/2560)
- [nwaku] [bug: Peer Reconnection not working?](https://github.com/waku-org/nwaku/issues/2592)
- [nwaku] [bug: nwaku <> js-waku interop tests failing](https://github.com/waku-org/nwaku/issues/2621)
#### Next
- [nwaku] [bug/regression: node ca be started on multiple clusters](https://github.com/waku-org/nwaku/issues/2552)
- [nwaku] [bug: autosharding resolves content topics to wrong shard](https://github.com/waku-org/nwaku/issues/2538)
- [nwaku] [bug: Store REST API returns invalid digest](https://github.com/waku-org/nwaku/issues/2615)
### Enhancements
#### In Progress
- [nwaku] [chore: review waku-simulator deployment and improve tracking processes](https://github.com/waku-org/nwaku/issues/2342)
- [nwaku] [feat: add WakuMessage's meta field to db schema](https://github.com/waku-org/nwaku/issues/2432)
- [nwaku] [chore: Address more attack vectors in rate limiting non-relay protocols](https://github.com/waku-org/nwaku/issues/2589)
- [js-waku] [feat: filter.createSubscription accept ShardParams](https://github.com/waku-org/js-waku/issues/1967)
#### Next
- [js-waku] [chore: move to js-waku repo](https://github.com/waku-org/js-noise/issues/45)
- [js-waku] [feat: better developer experience](https://github.com/waku-org/js-rln/issues/76)
## Ecosystem Development
### BD
- Calls with prospects
- Advancing ongoing going leads
- Qualified prospects
- Created a validation tracking database
- Event planning done for the upcopming quarters
### Solution Engineering
- Working on slides for talks in May/June
- Trying to get js-waku working in projects again - so far resulted in filed issues
- updated nwaku to 0.27.0 in awesome-akash
- calls with BD
- assisting Portrait with some architectural decisions
- assisting Dria with nwaku REST API
### Dev Rel
- token2049 (20+ leads)
- libp2p rpgf nomination completed
- sorting out ethdenver leads, sorting out crm
- drafting Railgun blog article
- forwarding portrait.so interview to comms
- interview preparation for Railgun <> waku
- Ethdam feedback/summary
### Comms and Events
- X: 1441 new followers ( +11%), 47.8% engagement rate ( +58%), 15889 likes (+47%) - we hit 10k on Twitter - yay!
- Linkedin: 11 new followers
- Discord: +44 (2.6%)
- 1 PR went live, about W3PN and Logos, mentioning Waku - https://cointelegraph.com/press-releases/logos-partners-with-web3privacy-now-to-advance-digital-privacy
- Wev interviewed Portrait founder at ETHDam - video sent for editing
### Events
- Ivan gave a presentation and spoke at the panel at https://web3fc.xyz/
- Guru attended token2049
- ETHDam summary doc - https://docs.google.com/document/d/1kgR8q-WMWJ56kGav6MiFYqkA2eDudc_lFUpdYM3sQ8s/edit and photos
### Docs
- merged the general FAQ
- deprecated the JSON-RPC RFC spec
- Waku RFC website followup