logos-co/roadmap
1
0
Fork 0
mirror of https://github.com/logos-co/roadmap.git synced 2025-01-11 17:04:11 +00:00
Code Issues Packages Projects Releases Wiki Activity

waku update

Browse Source
This commit is contained in:
fryorcraken.eth 2023-10-18 10:45:47 +11:00
parent 13e0ac9ae0
commit 263d73ac7a
No known key found for this signature in database
GPG Key ID: A82ED75A8DFC50A4
1 changed files with 16 additions and 67 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

83
content/waku/updates/2023-10-16.md
View File

@ -6,116 +6,65 @@ date: 2023-10-16
lastmod: 2023-10-16 lastmod: 2023-10-16
draft: draft:
--- ---
### nwaku
### nwaku
**[chore: Reorganize RestApi specs for live documentation](https://github.com/waku-org/nwaku/issues/2120)** {E:REST API service node} **[chore: Reorganize RestApi specs for live documentation](https://github.com/waku-org/nwaku/issues/2120)** {E:REST API service node}
- _achieved_: Http RestAPI interface is in parity with json-rpc with even more features supported on it. - _achieved_: Http RestAPI interface is in parity with json-rpc with even more features supported on it.
- _next_: Openapi specification is reorganized and online doc generated out of it. Currently under PR review.
- _next_: Openapi specification is reorganized and online doc generated out of it. Currently under PR review. Follow up spec reorganization with rest api type reorganization. RFC changes to enhance lighpust failure response. Follow up spec reorganization with rest api type reorganization. RFC changes to enhance lighpust failure response.
**[feat: allowing users to choose port 0 for dynamically allocated ports](https://github.com/waku-org/nwaku/issues/2042)** {enhancement} **[feat: allowing users to choose port 0 for dynamically allocated ports](https://github.com/waku-org/nwaku/issues/2042)** {enhancement}
- _achieved_: had over code review sessions and got feedback. Implemented improvements, attempted new approaches, fixed bugs. Most of the solution is already implemented and working. - _achieved_: had over code review sessions and got feedback. Implemented improvements, attempted new approaches, fixed bugs. Most of the solution is already implemented and working.
- _next_: fix failed tests, add test cases and raise PR - _next_: fix failed tests, add test cases and raise PR
**[feat: experimental incentivize store protocol](https://github.com/waku-org/nwaku/issues/1961)** {E:Basic service incentivization}
**[feat: experimental incentivize store protocol](https://github.com/waku-org/nwaku/issues/1961)** {track:protocol-incentivization} - _achieved_: wrote the [first draft of incentivization outline](https://github.com/waku-org/research/pull/33)
- _next_: discuss open question, continue structuring the document
**[setting up static sharding fleet for Status](https://github.com/waku-org/nwaku/issues/1914)** {E:Static sharding}
_achieved_: wrote the [first draft of incentivization outline](https://github.com/waku-org/research/commit/08233a7ce2ce1d922c82ec178e82610c72f9feed) - _achieved_: setup a separate shard for community points of contact, and another one for 1:1/group messages
- _next_: investigate/fix discv5 not working when static sharding is being used.
_next_: discuss open question, continue structuring the document
**[PostgreSQL](https://github.com/waku-org/nwaku/issues/1888)** {E:2.1: Production testing of existing protocols}, {E:PostgreSQL} **[PostgreSQL](https://github.com/waku-org/nwaku/issues/1888)** {E:2.1: Production testing of existing protocols}, {E:PostgreSQL}
- _achieved_: - _achieved_:
- Testing environment prepared in `metal-01.he-eu-hel1.wakudev.misc.statusim.net`. There are two databases (Postgres and SQLite) with 5 million of random messages. - Testing environment prepared in `metal-01.he-eu-hel1.wakudev.misc.statusim.net`. There are two databases (Postgres and SQLite) with 5 million of random messages.
- Enhanced Grafana dashboard so that we can compare timings performance throughout an histogram.
- Enhanced Grafana dashboard so that we can compare timings performance throughout an histogram ( @alrevuelta's idea .)
- _next_: Carry on with the investigation to enhance the _Postgres_ performance. - _next_: Carry on with the investigation to enhance the _Postgres_ performance.
**[feat: provide a way to define advertised addresses](https://github.com/waku-org/nwaku/issues/1797)** {enhancement} **[feat: provide a way to define advertised addresses](https://github.com/waku-org/nwaku/issues/1797)** {enhancement}
- _achieved_: implemented solution and raised PR - _achieved_: implemented solution and raised PR
- _next_: get feedback, implement suggested improvements and close - _next_: get feedback, implement suggested improvements and close
**[nwaku c-bindings (NodeJS + Python)](https://github.com/waku-org/nwaku/issues/1332)** {E:NodeJS Library} **[nwaku c-bindings (NodeJS + Python)](https://github.com/waku-org/nwaku/issues/1332)** {E:NodeJS Library}
- _achieved_: - _achieved_:
- Separate PR to avoid global variables: https://github.com/waku-org/nwaku/pull/2118 - Separate PR to avoid global variables: https://github.com/waku-org/nwaku/pull/2118
- Started to document the tasks tackled so far: https://www.notion.so/NWaku-cbindings-FFI-7a9ae6240cfc4caba7c7ff0bf3429a70
- Started to document the tasks tackled so far: https://www.notion.so/NWaku-cbindings-FFI-7a9ae6240cfc4caba7c7ff0bf3429a70.
- _next_: Start creating a separate _NodeJs_ and _Python_ repositories, where we will create nodejs-waku and py-waku, respectively. - _next_: Start creating a separate _NodeJs_ and _Python_ repositories, where we will create nodejs-waku and py-waku, respectively.
--- ---
### js-waku ### js-waku
**[Peer Management: Connection and Disconnection](https://github.com/waku-org/js-waku/issues/914)** {E:2.1: Production testing of existing protocols}
**[Peer Management: Connection and Disconnection](https://github.com/waku-org/js-waku/issues/914)** {track:restricted-run}, {E:2.1: Production testing of existing protocols} - _achieved_: reached a conclusion tackling deliberate vs accidental disconnections, PRs opened to handle Filter subscriptions on disconnection/reconnections, iterative fixes on addressing multiple dial attempts for same peer, fixes around keep alive pings
- _next_: getting reviews & merging these PRs which should enable us to close this epic 🥳
- _achieved_: reached a conclusion tackling deliberate vs accidental disconnections, PRs opened to handle Filter subscriptions on disconnection/reconnections, iterative fixes on addressing multiple dial attempts for same peer, fixes around keep alive pings.
- _next_: getting reviews & merging these PRs which should enable us to close this milestone 🥳.
--- ---
### go-waku ### go-waku
**[feat: Service peer selection on specific shards](https://github.com/waku-org/go-waku/issues/680)** {E:1.4: Sharded peer management and discovery} **[feat: Service peer selection on specific shards](https://github.com/waku-org/go-waku/issues/680)** {E:1.4: Sharded peer management and discovery}
- _achieved_: refactor and migrate peer selection to peer manager and update lightclient API to use new options
- _next_: on-demand discovery if peers are not available for the shard
- _achieved_: refactor and migrate peer selection to peer manager and update lightclient API to use new options.
- _next_: on-demand discovery if peers are not available for the shard.
**[Add postgresql to the unit tests](https://github.com/waku-org/go-waku/issues/607)** {test} **[Add postgresql to the unit tests](https://github.com/waku-org/go-waku/issues/607)** {test}
- _achieved_: Completed. Fixed only sqlite being used for creating queries. - _achieved_: Completed. Fixed only sqlite being used for creating queries.
---