mirror of https://github.com/logos-co/roadmap.git
create waku weekly 2024-08-05 (#105)
This commit is contained in:
parent
268890b983
commit
4862f6c238
|
@ -0,0 +1,118 @@
|
|||
---
|
||||
title: 2024-08-05 Waku Weekly
|
||||
tags:
|
||||
- waku-updates
|
||||
date: 2024-08-05
|
||||
---
|
||||
|
||||
## [Milestone - Store Service Upgrade](https://github.com/waku-org/pm/milestone/28)
|
||||
|
||||
- [Store v3-beta - Message Hashes](https://github.com/waku-org/pm/issues/131)
|
||||
- achieved:
|
||||
- [research] implemented basic testing tools for storev3 benchmarking
|
||||
- next:
|
||||
- [research] run some tests against status.prod to get an idea of query times and bottlenecks, expand testing from there
|
||||
|
||||
- [Store v3 - store synchronisation](https://github.com/waku-org/pm/issues/132)
|
||||
- achieved:
|
||||
- [research] store resume PR updates
|
||||
- next:
|
||||
- [research] merge store resume PR
|
||||
|
||||
- [PostgreSQL Maintenance](https://github.com/waku-org/pm/issues/119)
|
||||
- achieved:
|
||||
- [nwaku] Simplification of store legacy code to prevent wrong partition creation - [chore: Simplification of store legacy code](https://github.com/waku-org/nwaku/pull/2931)
|
||||
- [nwaku] Validate the need for bigger database servers because they were swapping too much
|
||||
|
||||
|
||||
## [Milestone - Direct Message Reliability](https://github.com/waku-org/pm/milestone/29)
|
||||
|
||||
- [Telemetry: direct message reliability](https://github.com/waku-org/pm/issues/182)
|
||||
- achieved:
|
||||
- [chat] report peer id and number of connection failures to telemetry [feat(telemetry)_: send connection failure metric](https://github.com/status-im/status-go/pull/5518), [feat: handle metric for peer connection failure](https://github.com/status-im/telemetry/pull/27)
|
||||
- next:
|
||||
- [chat] update dial function in go-waku to propagate dial failures to status-go
|
||||
- blockers:
|
||||
|
||||
- [Reliability Protocol for Relay](https://github.com/waku-org/pm/issues/184)
|
||||
- achieved:
|
||||
- [nwaku] Simplify implementation and start using callbacks for API clients [feat: enhance reliability thanks to StoreV3](https://github.com/waku-org/nwaku/issues/2819)
|
||||
|
||||
- [Reliability Protocol for Resource-Restricted Clients](https://github.com/waku-org/pm/issues/186)
|
||||
- achieved:
|
||||
- [js-waku] validating filter messages, and performing renewals [feat: validate messages for individual filter nodes & perform renewals](https://github.com/waku-org/js-waku/pull/2057)
|
||||
- [js-waku] health metric for node and protocols: [feat: node and protocols health](https://github.com/waku-org/js-waku/pull/2080)
|
||||
- next:
|
||||
- [nwaku] ongoing implementation [feat: Enhance lightpush protocol error handling](https://github.com/waku-org/nwaku/issues/2722)
|
||||
- [js-waku] message send retries for lightpush: [feat(lightpush): add retries to failing peers](https://github.com/waku-org/js-waku/issues/2069)
|
||||
- blockers:
|
||||
- [js-waku] store v3 blocked by nwaku 0.32 release: [feat!: store v3](https://github.com/waku-org/js-waku/pull/2036)
|
||||
|
||||
- [User apps for large scale dogfooding](https://github.com/waku-org/pm/issues/188)
|
||||
- achieved:
|
||||
- [js-waku] add light push error metric and generic metric to dogfooding app [feat: add light push error and generic waku metric](https://github.com/status-im/telemetry/pull/33), [feat: record light push errors in dogfooding](https://github.com/waku-org/lab.waku.org/pull/79)
|
||||
- next:
|
||||
- [js-waku] remove metric from queue on duplicate key error [dogfooding: remove metric from queue on duplicate key error](https://github.com/waku-org/lab.waku.org/issues/82)
|
||||
|
||||
- [Review MVDS usage and fail path](https://github.com/waku-org/pm/issues/189)
|
||||
- achieved:
|
||||
- [chat] bump mvds for clearing old states [chore_: bump mvds](https://github.com/status-im/status-go/pull/5623)
|
||||
- next:
|
||||
- [chat] move message hash query for outgoing messages to go-waku
|
||||
- [chat] continue the request to join community test
|
||||
- blockers:
|
||||
|
||||
## [Milestone - Static Sharding - dedicated shards](https://github.com/waku-org/pm/milestone/31)
|
||||
|
||||
- [Sharding peer management and discovery hardening](https://github.com/waku-org/pm/issues/172)
|
||||
- achieved:
|
||||
- [nwaku] Investigated [bug: node getting stuck and missing messages](https://github.com/waku-org/nwaku/issues/2921). Created images for DST team to run and analyzed the resulting logs
|
||||
- [research] added new metric and grafana dashboard focused on discovery, PR adding cluster filtering to Waku peer exchange
|
||||
- next:
|
||||
- [nwaku] Continue investigating the issue, now trying to understand how async futures are handled by the dispatcher
|
||||
- [research] rendez-vous discovery
|
||||
|
||||
## [Milestone - Scale 1:1 chat messages PoC](https://github.com/waku-org/pm/milestone/35)
|
||||
|
||||
- [RLNv2 in nwaku](https://github.com/waku-org/pm/issues/204)
|
||||
- achieved:
|
||||
- next:
|
||||
- blockers:
|
||||
|
||||
- [Maturing RLN variables/parameters revision](https://github.com/waku-org/pm/issues/205)
|
||||
- achieved:
|
||||
- next:
|
||||
- blockers:
|
||||
|
||||
- [Provision RLN for light push clients PoC](https://github.com/waku-org/pm/issues/206)
|
||||
- next:
|
||||
- [research] Investigate how to use Paymasters aka gasless transactions for users, paid by a smart contract. Goal, PoC with go-waku-light
|
||||
|
||||
## Other Work
|
||||
|
||||
### Enhancements
|
||||
|
||||
- achieved:
|
||||
- [nwaku] Fixed failing js-waku interop tests and got CI to work again [chore: changing default pubsub topic to its static sharding version](https://github.com/waku-org/js-waku/pull/2083)
|
||||
- [nwaku] Improving docs [chore: updating doc reference to https rpc](https://github.com/waku-org/nwaku/pull/2937), [switching RPC provider instructions from websocket to https](https://github.com/waku-org/docs.waku.org/pull/205), [updating readme](https://github.com/waku-org/nwaku-compose/pull/109)
|
||||
- [nwaku] Bumped dependency for gcc 14 support [chore: bumping nim-bearssl](https://github.com/waku-org/nwaku/pull/2936)
|
||||
- [nwaku] Deploy v0.31.0 in waku.prod and status.prod
|
||||
- [chat] [refactor: move rate limiter and priority queue from status-go to API package](https://github.com/waku-org/go-waku/pull/1171)
|
||||
- [chat] [refactor: move missing messages logic from status-go to go-waku](https://github.com/waku-org/go-waku/pull/1174), [](https://github.com/status-im/status-go/pull/5638)
|
||||
- [chat] remove unused code from wakuv2 [refactor: extract missing messages logic to go-waku](https://github.com/status-im/status-go/pull/5651)
|
||||
- next:
|
||||
- [js-waku] peers used by different protocols to be different from one-another to increase footprint: [feat: peer selection for protocols](https://github.com/waku-org/js-waku/issues/2074)
|
||||
- [js-waku] filter API to be simple (reliability user story): [feat: use decoder as a seed for subscription](https://github.com/waku-org/js-waku/issues/2034)
|
||||
|
||||
|
||||
### Bugs
|
||||
|
||||
- achieved:
|
||||
- [nwaku] building testing tools to analyze peer-exchange protocol and its behavior [test: peer exchange testing tool](https://github.com/waku-org/nwaku/pull/2940)
|
||||
- [js-waku] continuous discovery updates for node information [chore(peer-exchange): support updates of previously discovered peer's addresses](https://github.com/waku-org/js-waku/issues/2051)
|
||||
- [chat] fix: missing wakuv2 fields in createAccountRequest toJson func [fix: missing wakuv2 fields in createAccountRequest toJson func](https://github.com/status-im/status-desktop/pull/15876)
|
||||
- [chat] [fix: storenode multiaddresses](https://github.com/status-im/status-go/pull/5630)
|
||||
- [chat] [fix: handle scenario where the node's ENR has no shard (due to shard update)](https://github.com/waku-org/go-waku/pull/1176)
|
||||
- next:
|
||||
- [nwaku] [bug: failed to retrieve peer info via peer exchange protocol](https://github.com/waku-org/nwaku/issues/2875)
|
||||
- [chat] verify missing messages to determine if storenode sync was executed
|
Loading…
Reference in New Issue