mirror of https://github.com/logos-co/roadmap.git
create waku weekly 2024-11-04 (#149)
This commit is contained in:
parent
9be4c9cd6b
commit
b5df4ea158
|
@ -0,0 +1,92 @@
|
||||||
|
---
|
||||||
|
title: 2024-11-04 Waku Weekly
|
||||||
|
tags:
|
||||||
|
- waku-updates
|
||||||
|
date: 2024-11-04
|
||||||
|
---
|
||||||
|
## [Milestone - Store Service Upgrade](https://github.com/waku-org/pm/milestone/28)
|
||||||
|
|
||||||
|
- [Store v3 - store synchronisation](https://github.com/waku-org/pm/issues/132)
|
||||||
|
- achieved:
|
||||||
|
- [research] message transfer protocol and integration with sync
|
||||||
|
- [research] More store sync investigations
|
||||||
|
- next:
|
||||||
|
- [research] encoding optimization, metrics, logs, spec
|
||||||
|
- [research] Continue with store sync testing, update test plan
|
||||||
|
|
||||||
|
## [Milestone - Static Sharding - dedicated shards](https://github.com/waku-org/pm/milestone/31)
|
||||||
|
|
||||||
|
- [Telemetry: Measure Bandwidth](https://github.com/waku-org/pm/issues/195)
|
||||||
|
- achieved: [chat] updated NetworkMonitor
|
||||||
|
|
||||||
|
- [Sharding peer management and discovery hardening](https://github.com/waku-org/pm/issues/172)
|
||||||
|
- achieved: [chat] add option to specify prefered peers for filter [feat: add option to specify preferred peers for filter](https://github.com/waku-org/go-waku/pull/1250) and [fix_: simple bad peer check logic for lightmode](https://github.com/status-im/status-go/pull/5964)
|
||||||
|
|
||||||
|
## [Milestone: Nwaku in Status Desktop](https://github.com/waku-org/pm/milestone/33)
|
||||||
|
|
||||||
|
- [Nwaku in Status Desktop](https://github.com/waku-org/pm/issues/203)
|
||||||
|
- achieved:
|
||||||
|
- [nwaku] [Support for discovery of circuit-relay peers](https://github.com/waku-org/nwaku/issues/2514)
|
||||||
|
- [nwaku] [feat: adding waku_dial_peer and get_connected_peers to libwaku](https://github.com/waku-org/nwaku/pull/3149)
|
||||||
|
- [nwaku] [feat: running periodicaly peer exchange if discv5 is disabled](https://github.com/waku-org/nwaku/pull/3150)
|
||||||
|
- [nwaku] [fix: libwaku's dns discovery multiaddresses](https://github.com/waku-org/nwaku/pull/3155)
|
||||||
|
- [nwaku] [chore: naming connect procedure](https://github.com/waku-org/nwaku/pull/3157)
|
||||||
|
- [nwaku] [feat_: dial, drop and retrieve connected peers](https://github.com/status-im/status-go/pull/6013)
|
||||||
|
- [nwaku] [feat: supporting peer exchange with nwaku](https://github.com/status-im/status-go/pull/5983)
|
||||||
|
|
||||||
|
## [Milestone: Incentivise running a Waku infrastructure node](https://github.com/waku-org/pm/milestone/35)
|
||||||
|
|
||||||
|
- [Service Incentivisation - Pay for RLN provision PoC](https://github.com/waku-org/pm/issues/245)
|
||||||
|
- achieved:
|
||||||
|
- [research] start working on service incentivization PoC
|
||||||
|
- [research] Started investigating private payments with SP1
|
||||||
|
- next:
|
||||||
|
- [research] continue with the PoC; prepare for team discussions at the Bangkok offsite
|
||||||
|
- [research] Evaluate feasibility (circom vs sp1 performance)
|
||||||
|
|
||||||
|
## [Milestone: Bandwidth optimization and protocol review](https://github.com/waku-org/pm/milestone/31)
|
||||||
|
|
||||||
|
- [Status usage of Waku scaling and bandwidth optimization recommendation](https://github.com/waku-org/pm/issues/197)
|
||||||
|
- achieved: [chat] test the bandwidth difference between relay and light mode [Bandwidth Usage Between Relay and Light](https://www.notion.so/Bandwidth-Usage-Between-Relay-and-Light-12a8f96fb65c802489f3eef02fb952a4)
|
||||||
|
|
||||||
|
- [Review usage of content topics in Status Chat and Communities protocol](https://github.com/waku-org/pm/issues/198)
|
||||||
|
- achieved:
|
||||||
|
- [chat] phase2 of content-topic change for communities [feat_: use content-topic override for all community filters](https://github.com/status-im/status-go/pull/5993)
|
||||||
|
- [research] draft PR opened for phase-2 changes [feat_: use content-topic override for all community filters](https://github.com/status-im/status-go/pull/5993)
|
||||||
|
|
||||||
|
### [Milestone: Demonstrate product-market fit](https://github.com/waku-org/pm/milestone/36)
|
||||||
|
|
||||||
|
- [Customer Interviews](https://github.com/waku-org/pm/issues/251)
|
||||||
|
- achieved: Had a meeting with one of the gaming projects, in doubt if there’s a fit;
|
||||||
|
- next: interviewing a network states project;
|
||||||
|
|
||||||
|
- [Co-design sessions](https://github.com/waku-org/pm/issues/252)
|
||||||
|
- achieved:
|
||||||
|
- have a soft commitment to co-design with one of the gaming projects
|
||||||
|
- another soft commitment to co-design with an L2
|
||||||
|
- Co-designing with an Activism/Privacy project
|
||||||
|
|
||||||
|
### [Milestone: Acquire first 10 customers](https://github.com/waku-org/pm/milestone/37)
|
||||||
|
|
||||||
|
- [5-10 Highly qualified leads](https://github.com/waku-org/pm/issues/254)
|
||||||
|
- achieved:
|
||||||
|
- Got Waku a workshop in the Credible intents event
|
||||||
|
- This should help find more leads in the intents vertical;
|
||||||
|
- We have confirmation that one project in the activism vertical is integrating Waku and they shared the use case document with us;
|
||||||
|
|
||||||
|
- [Review current integrations](https://github.com/waku-org/pm/issues/255)
|
||||||
|
- achieved:
|
||||||
|
- [chat] Devcon, Qaku improvement (progress on integrating Codex for persistency, fixing issues)
|
||||||
|
- [chat] Devcon portal - integrating UCANs based authentication
|
||||||
|
|
||||||
|
## Other Work
|
||||||
|
|
||||||
|
### Maintenance
|
||||||
|
|
||||||
|
- next:
|
||||||
|
- [nwaku] prepare Rust app for devcon workshop
|
||||||
|
- [nwaku] [Bump vendor dependencies for release 0.34.0](https://github.com/waku-org/nwaku/issues/3087) Vendor version upgrades are finished. Major achievement having latest web3, eth and libp2p libraries in nim-waku. Under review and testing.
|
||||||
|
|
||||||
|
### Bugs
|
||||||
|
|
||||||
|
- achieved: [chat] investigate various issues reported by status QA wrt message reliability and slow recovery after disconnections [Significant delay or missing messages on 4G in community (without re-login or app closure)](https://github.com/status-im/status-mobile/issues/21172) and [Messages are slow and some of them are marked as not delivered (1-1 chat between relay/light) when devise time is async](https://github.com/status-im/status-mobile/issues/21497)
|
Loading…
Reference in New Issue