roadmap/content/waku/updates/2023-09-11.md

135 lines
6.3 KiB
Markdown

---
title: 2023-09-11 Waku weekly
tags:
- waku-updates
date: 2023-09-11
lastmod: 2023-09-11
draft: false
---
2023-09-11 Waku weekly
---
### Research
**[1.1 Network requirements and task breakdown](https://github.com/waku-org/pm/issues/62)** {E:1.1 Network requirements and task breakdown}
- _achieved:_ Opened first raw version of Waku Network RFC for review.
- _next:_ Address any feedback on the Waku Network RFC and complete under-defined sections.
---
### Docs
**[Review Usage and Metrics 2023 Q3](https://github.com/waku-org/docs.waku.org/issues/107)** {E:Define network and community metrics}
- _achieved_: published the language/SDK poll on Discord
- _next_: publish the poll on socials for more visibility and responses
**[Docs general improvement/incorporating feedback (2023)](https://github.com/waku-org/docs.waku.org/issues/102)**
- _next_: refactor the layout of the docs to match the new designs
---
### nwaku
**[feat(rest): Add /health endpoint to rest api](https://github.com/waku-org/nwaku/issues/1988)** {E:REST API service node}
- _achieved_: Feature /health endpoint added. PR merged: https://github.com/waku-org/nwaku/pull/2011
**[feat: Autosharding API for (relay) subscriptions](https://github.com/waku-org/nwaku/issues/1936)** {E:1.2: Autosharding for autoscaling}
- _achieved_: Refactored and simplified the core logic
- _next_: More PR feedback
**[Release Process Improvements](https://github.com/waku-org/nwaku/issues/1889)** {E:Automated release processes}
- _achieved_: execute js-waku tests from nwaku workflows against PRs, nightly and release candidates
- _next_: adding Linux arm64 binaries and images
**[PostgreSQL](https://github.com/waku-org/nwaku/issues/1888)** {E:2.1: Production testing of existing protocols}, {E:PostgreSQL}
- _achieved_:
- Created a `jmeter` test plan to stress _Store_ queries through REST _Store_. As a conclusion, the node with _Store_ _Postgres_ showed worse performance than the one with _SQLite_.
https://github.com/waku-org/test-waku-query/pull/5
- Added reconnection feature. If the connection with _Postgres_ is lost, the `nwaku` node tries to reconnect again. https://github.com/waku-org/nwaku/pull/1997
- The `wakuv2.shards` fleet had been de-prioritized in favor of the `status.shards` one.
https://github.com/status-im/infra-nim-waku/issues/74#issuecomment-1710514544
- _next_: Optimize database so that the _Store_ requests behave better with _Postgres_.
**[chore: do not advertise MAs with port 0](https://github.com/waku-org/nwaku/issues/1883)** {bug}
- _next_: analyze and fix issue
**[feat: HTTP REST API: Filter support v2](https://github.com/waku-org/nwaku/issues/1872)** {E:REST API service node}
- _achieved_: PR tracking is https://github.com/waku-org/nwaku/pull/1890
Review is done, various fixes upon applied
- _next_: Last, agreed interface change to be done to complete.
**[chore: update resolved enr ip when using `dns4-domain-name` flag](https://github.com/waku-org/nwaku/issues/1576)** {enhancement}
- _next_: analyze and fix issue
**[bug: `0.0.0.0` included in `listenAddrs` of identify message](https://github.com/waku-org/nwaku/issues/1427)** {bug}
- _achieved_: fixed bug, updated tests according to new fixes and raised PR
**[nwaku c-bindings (NodeJS + Python)](https://github.com/waku-org/nwaku/issues/1332)** {E:NodeJS Library}
- _achieved_: improved the thread safeness communication.
https://github.com/waku-org/nwaku/pull/1978
- _next_: Once the above PR is merged, avoid the use of global variables, to enhance the thread-safeness ( see https://github.com/waku-org/nwaku/pull/1865#discussion_r1282722954 )
**[HTTP REST API: Store, Filter, Lightpush, Admin and Private APIs](https://github.com/waku-org/nwaku/issues/1076)** {E:REST API service node}
- _achieved_: Legacy Filter - v1 - interface Rest Api support added. V2 implementation done wait for PR review, /health rest api added to check (currently) RLN readiness
- _next_: Last round of Filter v2 PR review with finalized re-worked push handler part.
- _blocking_: /health endpoint come in and Filter v2 work was down prio till.
---
### js-waku
**[Maintenance](https://github.com/waku-org/js-waku/issues/1455)** {E:2023-qa}
- _achieved_: updated typescript + plugins to major versions, waiting to merge for release
**[Developer Experience (2023)](https://github.com/waku-org/js-waku/issues/1453)** {E:2023-eco-growth}
- _achieved_:
- investigation of `go-waku` interop test that is failing - ongoing, fixing next release
- protocols now use lowest latency peer instead of a random peer
- _next_: root cause `go-waku` interop test failure, release `next` tag on master merge
**[Peer Exchange is supported and used by default](https://github.com/waku-org/js-waku/issues/1429)** {E:2023-light-protocols}
- _achieved_: Peer Exchange is now merged included in `defaultBootstrap`
- _next_: followup on browser investigation and confirm if the EPIC can be safely closed
**[Cover Several Environments As Part of Testing](https://github.com/waku-org/js-waku/issues/52)** {test}, {E:2023-qa}
- _achieved_: browser testing is redone and opening for review
- _next_: integrate with release process - rather quick follow up, revisit current epic
---
### go-waku
**[RLN enabled by default](https://github.com/waku-org/go-waku/issues/655)** {E:3.2: Basic DoS protection in production}
- _achieved_:
- ordered validator execution, upgrade zerokit, append rln proofs when posting msgs in rest/rpc, clean up nullifier table, automatically use key from keystore if only a single credential is available, validate credential using onchain query
- rln membership registration logic refactoring and fixing bugs. Added test for membershipFetcher. Added code for mock_blockchain and mock_client to test membershipFetcher.
- _next_: bandwidth validation, rln isReady verif in /health endpoint, subcommand to list credentials
**[Maintenance](https://github.com/waku-org/go-waku/issues/634)** {E:2023-qa}
- _achieved_:
- fix panic observed in peer-manager, update filter protocol as per rfc.
- add tls/ws to address factory and log ENRs only after they have been setup
- refactoring and some bug fixes in peermanager and read rfcs and docs
- _next_: increase test coverage and read more code.
**[Improve Test Coverage](https://github.com/waku-org/go-waku/issues/620)** {test}
- _achieved_: build examples as part of CI to capture compile errors
---