update waku sept 18

This commit is contained in:
chair28980 2023-09-19 17:37:48 -07:00
parent c4494831c5
commit fe74d4604e
1 changed files with 23 additions and 12 deletions

View File

@ -3,7 +3,7 @@ title: 2023-09-18 Waku weekly
tags:
- waku-updates
date: 2023-09-18
lastmod: 2023-09-18
lastmod: 2023-09-19
draft: false
---
@ -13,7 +13,7 @@ draft: false
- [x] LordGhostX
- [x] NagyZoltanPeter
- [x] SionoiS
- [ ] alrevuelta
- [x] alrevuelta
- [x] chaitanyaprem
- [ ] danisharora099
- [ ] fryorcraken
@ -26,6 +26,8 @@ draft: false
- [ ] vpavlin
- [x] weboko
2023-09-18 Waku weekly
---
### Epics
@ -46,42 +48,51 @@ draft: false
- _achieved_: added guide on advanced nwaku and WebSocket configurations
- _next_: add guide for enabling node monitoring
---
### Research
**[RLN Key Benchmarks](https://github.com/waku-org/research/issues/23)** {E:3.2: Basic DoS protection in production}
* *achieved*: benchmark rln, see issue with report.
---
### nwaku
**[feat: HTTP REST API: lightpush ](https://github.com/waku-org/nwaku/issues/2040)**
- _achieved_:
- _achieved_:
- _next_: LightPush REST endpoint will be implemented fully and put on PR review
- _blocking_:
**[bug: wrong user_version in sqlite database that blocks the run of a Waku node](https://github.com/waku-org/nwaku/issues/2027)** {bug}
- _achieved_: bug fix that prevented a _Store_ `nwaku` to start if the _SQLite_ db was created with versions [0.14.0 - 0.18.0]
- _next_: -
**[feat: Autosharding API for (relay) subscriptions](https://github.com/waku-org/nwaku/issues/1936)** {E:1.2: Autosharding for autoscaling}
- _achieved_: many PR fixes,
- _blocker_: explicit subscriptions in js-waku tests
**[chore: do not advertise MAs with port 0](https://github.com/waku-org/nwaku/issues/1883)** {bug}
**[chore(rln-relay): Requirements to consider RLN ready (non experimental)](https://github.com/waku-org/nwaku/issues/1906)** {E:3.1: DoS requirements and design}
- _achieved_: tested two different solutions: updating the port with an addressMapper, and not allowing the user to use port 0. Analyzed and discussed technical implications of both solutions. Initially followed decision to proceed with 2nd solution for now, with intention of implementing the first solution in the future.
Opened a draft PR and updated tests for the solution of not allowing the user to choose port 0.
* *achieved*: waku rln is not an experimental feature anymore, and is part of nwaku code base. from now on experimental features are hidden behind a flag and not in different build
**[chore: do not advertise multiaddr with port 0](https://github.com/waku-org/nwaku/issues/1883)** {bug}
- _achieved_: tested two different solutions: updating the port with an addressMapper, and not allowing the user to use port 0. Analyzed and discussed technical implications of both solutions. Initially followed decision to proceed with 2nd solution for now, with intention of implementing the first solution in the future.
Opened a draft PR and updated tests for the solution of not allowing the user to choose port 0.
- _next_: after further feedback received today, we have to complete the discussion of how to move forward and either review and proceed with current PR, or plan and implement solution that updates all the data structures consistently across the node
**[feat: HTTP REST API: Filter support v2](https://github.com/waku-org/nwaku/issues/1872)** {E:REST API service node}
- _achieved_: Filter v1 & v2 REST API endpoints merged to master
- _next_: LightPush REST endpoint
- _blocking_:
**[chore: update resolved enr ip when using `dns4-domain-name` flag](https://github.com/waku-org/nwaku/issues/1576)** {enhancement}
- _achieved_: implemented solution that does DNS IP resolution during node bringup when no external IP is found but a DNS address is provided.
Validated and tested "happy paths" of the solution, raised draft PR and got feedback about the solution
-_next_: discuss and define the system's behavior on errors, implement error handling and adding tests for this feature.
Validated and tested "happy paths" of the solution, raised draft PR and got feedback about the solution
-_next_: discuss and define the system's behavior on errors, implement error handling and adding tests for this feature.
---
### js-waku
@ -94,7 +105,7 @@ draft: false
**[Cover Several Environments As Part of Testing](https://github.com/waku-org/js-waku/issues/52)** {test}, {E:2023-qa}
- _achieved_: got reviews on playwrights tests
- _next_: maybe add bounty, check Karma testing
- _next_: maybe add bounty, check Karma testing
---
### go-waku
@ -106,7 +117,7 @@ draft: false
**[RLN enabled by default](https://github.com/waku-org/go-waku/issues/655)** {E:3.2: Basic DoS protection in production}
- _achieved_: isReady verif in /health endpoint, make RLN available in service nodes and library usage by default, update docs and docker image, use zerokit 0.3.4, allow running service node with no RLN credentials
- _achieved_: isReady verif in /health endpoint, make RLN available in service nodes and library usage by default, update docs and docker image, use zerokit 0.3.4, allow running service node with no RLN credentials
- _next_: bandwidth validation, subcommand to list credentials
**[Maintenance](https://github.com/waku-org/go-waku/issues/634)** {E:2023-qa}