mirror of https://github.com/logos-co/roadmap.git
added weeklies
This commit is contained in:
parent
9e92c83886
commit
71e7cd9dea
|
|
@ -0,0 +1,54 @@
|
|||
---
|
||||
title: 2023-08-29 Comms weekly
|
||||
tags:
|
||||
- acid-updates
|
||||
date: 2023-08-29
|
||||
lastmod: 2023-09-04
|
||||
draft: false
|
||||
---
|
||||
## Leads roundup - acid
|
||||
|
||||
### **Al - Comms**
|
||||
|
||||
- LPE & Podcast are almost there. Content needs to be polished and reviewed by Carl and Jarrad. Might have an impact on the deadline but we start testing phase tomorrow.
|
||||
- Plan for marketing and promotion of the podcast needs a bit more work. Teasers for Snowden will be released. Next episode drops next week.
|
||||
- Status app comms campaign. We are aligned with John and Status team. Needs pre-launch work for content and pending some items and confirmations from John.
|
||||
- Digital designer will be joining us soon for Content team. We are still looking for a Motion designer.
|
||||
- Townhall: Dmitry and Santiago will be talking re: Codex + Logos culture.
|
||||
|
||||
### **Amir - Tech and Design**
|
||||
|
||||
- LPE is ready. Content is being populated. Soft launch is 30/08. Then stress test, debug, etc.
|
||||
- Notion page is up and running for listing errors, bugs and feedback. Amir will move to GitHub https://www.notion.so/f9fef49cc74c46b19ceb9c14a2003062?v=3eb563f28fc448bd836d16da1272d620&pvs=4
|
||||
- Wiki: codebase will be ready in a day or two, then once infra team deploys we have kick off meeting for structure, content etc. Then design team can redesign based on what we need. Timeframe: end of September
|
||||
|
||||
### **Matt - Copy**
|
||||
|
||||
- Content from the LPE is getting there, pending review as mentioned above.
|
||||
- Cleaning up the documentation sites etc.
|
||||
- Status comms campaign is coming so articles in planning will be drafted and
|
||||
|
||||
### **Christian - Podcast**
|
||||
|
||||
- Podcast release plan is being solidified and reviewed https://docs.google.com/document/d/1ppSb_Fkdw3iirwzlEgTvYpkq3n00ds4Xz5KE3mgqA-E/edit?usp=sharing
|
||||
- Review process is set up and open for feedback.
|
||||
|
||||
### **Nick - Content**
|
||||
|
||||
- Decks for townhall are coming and will be ready for next week.
|
||||
- Images for LPE content is being vetted. We are looking to establish a style for the first article to set the tone for the following. This is holding it back a bit but once it is set we can move it from there.
|
||||
|
||||
### **Louisa - Events**
|
||||
|
||||
- By the end of next week we will launch global event strategy post-review. Includes templates and structures for the future.
|
||||
- Network State Event needs to lock down the potential event speakers, how to communicate with them and basically get a review. Nimbus and Waku and Codex will be there. We need to fix the program and agree on it. Venues shortlisted by the end of the week.
|
||||
- 8 agencies have been briefed as event organisers. Needs to be locked and set by end of week.
|
||||
- ETH Rome, Logos and Waku are sponsoring and Jarrad is talking. Paralelni Polis is happening late September. Working on the details to hit production deadlines.
|
||||
- Beginning work on hacakthon in Seoul end of February 2024.
|
||||
|
||||
### **Movement Building - Santiago**
|
||||
|
||||
- Comms plans LPE, Status and Logos Community plans are on good track. Carl reviewed and asked for 90 day plans plus timelines.
|
||||
- Logos community structure is being developed to guide people through an engagement/leadership ladder that serves our purpose. First community coming in will be our testing phase pre-growth.
|
||||
- LPE launch plan is being reviewed and has a budget verbally approved to push via paid ads. Focus mostly on Snowden on episode as a roundabout way to support awareness for Logos.
|
||||
- BU Plans, pretty much done, will send them to Al asap for review.
|
||||
|
|
@ -0,0 +1,41 @@
|
|||
---
|
||||
title: 2023-08-21 Nomos weekly
|
||||
tags:
|
||||
- nomos-updates
|
||||
date: 2023-08-21
|
||||
lastmod: 2023-09-04
|
||||
draft: false
|
||||
---
|
||||
## Nomos weekly report 21st Oct
|
||||
|
||||
(delayed as I was on holidays and then took me some time to clarify some things with the team)
|
||||
|
||||
### Network Privacy and Mixnet
|
||||
|
||||
- Improved the mixnet implementation based on latest discussion. https://github.com/logos-co/nomos-node/pull/307
|
||||
- Base implementation of Mixnet PoC: https://github.com/logos-co/nomos-node/pull/302
|
||||
- Refactor to encapsulate message body creation&write&read: https://github.com/logos-co/nomos-node/pull/308
|
||||
- New issues related to mixnet: https://github.com/logos-co/nomos-node/issues?q=is%3Aopen+is%3Aissue+label%3Amixnet
|
||||
|
||||
### Private PoS
|
||||
|
||||
- Updated draft addressing comments related to shielded and transparent transaction types.
|
||||
- Defined an opportunistic voting problem.
|
||||
- Continuing analysis on zCash transaction's construction.
|
||||
- This is currently the project that is going slowest and needs more attention going forward. It's also the most complex and with the most unknowns.
|
||||
|
||||
### Simulations app
|
||||
|
||||
- Graceful shutdown of simulations.
|
||||
- Created a new repository for simulations configurations and test results: https://github.com/logos-co/nomos-simulations
|
||||
- Updates and discussed test runs: https://github.com/logos-co/nomos-simulations/pull/3
|
||||
- Changes to support CSV format output of simulation data: https://github.com/logos-co/nomos-node/pull/304 and https://github.com/logos-co/nomos-node/pull/306
|
||||
- Minor issue on integration tests fixed: https://github.com/logos-co/nomos-node/pull/315
|
||||
|
||||
### Data Availability Sampling
|
||||
|
||||
- Studied RS+KZG in context of our DA architecture.
|
||||
- RS: basic encoding/decoding lib. Created a basic wrapper around reed-solomon-encoding library to work with arbitrary bytearrays with the simples API possible. Created basic tests and docs as well.
|
||||
- KZG: basic commitment + proof creation, also proof verification lib. Same here, created a simplistic API that abstract from the confusing types in the underlaying used library.
|
||||
- Created a simplistic API for RS: https://github.com/logos-co/nomos-node/pull/303
|
||||
- Created a simplistic API for KZG: https://github.com/logos-co/nomos-node/pull/309
|
||||
|
|
@ -0,0 +1,45 @@
|
|||
---
|
||||
title: 2023-08-29 Nomos weekly
|
||||
tags:
|
||||
- nomos-updates
|
||||
date: 2023-09-04
|
||||
lastmod: 2023-09-04
|
||||
draft: false
|
||||
---
|
||||
## **Nomos weekly report**
|
||||
|
||||
### Milestone 1: Network Privacy and Mixnet
|
||||
|
||||
#### **Research**
|
||||
- A Mixnet PoC was conducted to gauge end-to-end latency, revealing a slight latency increase when utilizing mixnet. Several potential optimization areas have been identified.
|
||||
|
||||
#### **Development**
|
||||
- Various enhancements for the Mixnet have been developed, including the addition of delays for Sphinx packets, auto port for integration tests, and introducing a graceful shutdown for mixnode elements.
|
||||
- There's an ongoing shift from channels to streams in mixnet message handling.
|
||||
- Refactoring of Mixnet Node & Client: https://github.com/logos-co/nomos-node/pull/320
|
||||
- Mixnet PoC Architecture Documents: https://www.notion.so/Mixnet-and-Network-Privacy-Architecture-613f53cf11a245098c50af6b191d31d2
|
||||
- Mixnet Measurements Documentation: https://www.notion.so/Mixnet-Measurements-551ade11ae4d44ca9f3d947ea6950c67
|
||||
- Sphinx Packet Delay Support: https://github.com/logos-co/nomos-node/pull/321
|
||||
- Auto Port for Tests: https://github.com/logos-co/nomos-node/pull/327
|
||||
- Mixnet Criterion Measurement: https://github.com/logos-co/nomos-node/pull/328
|
||||
- Graceful Shutdown for Mixnet: https://github.com/logos-co/nomos-node/pull/330
|
||||
|
||||
---
|
||||
|
||||
### Milestone 2: Private PoS
|
||||
|
||||
#### **Research**
|
||||
- Discussions were held about token-engineering and staking in private settings, resulting in documentation that delves into the validation and delegation aspects of PPoS. Current considerations involve the integration of the ZeroCash/zCash construction into the staking model.
|
||||
|
||||
---
|
||||
### Milestone 3: Data Availability Sampling (RS, KZG)
|
||||
|
||||
#### **Research**
|
||||
- Limitations discovered during RS and KZG implementation, notably with RS library scalability issues and bls12_381 curve finite field challenges. Found KZG libraries are primarily designed for Ethereum, which constrains the blob size.
|
||||
- Benchmarks for KZG implementation were carried out, and simulation runs were conducted for different configurations.
|
||||
- Node decay in relation to data availability was analyzed, leading to the derivation of an equation for understanding node averages in the network.
|
||||
#### **Development**
|
||||
- KZG Library: https://github.com/logos-co/nomos-node/pull/325
|
||||
- KZG Base Layer initial approach: https://github.com/logos-co/nomos-node/pull/309
|
||||
- Detailed KZG Operation Benchmarks: https://github.com/logos-co/nomos-node/tree/da-kzg-benches
|
||||
- Node Decay Analysis & Results: https://www.overleaf.com/read/gzqvbbmfnxyp
|
||||
|
|
@ -0,0 +1,92 @@
|
|||
---
|
||||
title: 2023-08-28 Waku weekly
|
||||
tags:
|
||||
- waku-updates
|
||||
date: 2023-08-28
|
||||
lastmod: 2023-08-28
|
||||
draft: false
|
||||
---
|
||||
|
||||
## 2023-08-28 Waku weekly
|
||||
---
|
||||
### Epics
|
||||
|
||||
**[Status MVP: Status Core Contributors use Status Mobile](https://github.com/waku-org/pm/issues/8)** {E:2023-light-protocols}
|
||||
|
||||
Light push and filter protocols are available in Status Mobile and Desktop. Some light dogfooding has started.
|
||||
|
||||
---
|
||||
### Research
|
||||
|
||||
**[1.1 Network requirements and task breakdown](https://github.com/waku-org/research/issues/6)** {E:2023-1mil-users}
|
||||
|
||||
- _achieved_: Further task refinement and assigning ownership. Visibility and traceability via GH issues.
|
||||
- _next_: Start working on Waku Network RFC.
|
||||
|
||||
---
|
||||
### nwaku
|
||||
|
||||
**[setting up static sharding fleet for Status](https://github.com/waku-org/nwaku/issues/1914)** {E:2023-10k-users}
|
||||
|
||||
- _achieved_: final infra definition, including generated keys and shards, specified in infra-status issue
|
||||
- _next_: ensure fleet gets deployed as specified
|
||||
|
||||
**[Release Process Improvements](https://github.com/waku-org/nwaku/issues/1889)** {E:2023-qa}
|
||||
|
||||
- _achieved_: added a CI job to notify on unexpected config option or DB schema changes
|
||||
- _next_: document how to run PR built images in waku-simulator, adding Linux arm64 binaries and images
|
||||
|
||||
**[PostgreSQL](https://github.com/waku-org/nwaku/issues/1888)** {E:2023-10k-users}
|
||||
|
||||
- _achieved_: new _docker compose_ in `test-waku-query` that allows to quickly compare `insert` and `query` performance between _SQLite_ and _Postgres_.
|
||||
- _next_: Carry on with stress testing & follow-up of the _Postgres_ addition to [wakuv2.shards](https://github.com/status-im/infra-nim-waku/blob/master/ansible/group_vars/wakuv2-shards.yml) by the _infra_ team.
|
||||
|
||||
**[nwaku c-bindings](https://github.com/waku-org/nwaku/issues/1332)** {E:2023-many-platforms}
|
||||
|
||||
- _achieved_: Started applying _thread-safe_ recommendations, making the _Waku Node_ instance to be created within the _Waku Thread_ itself.
|
||||
- _next_: Carry on with the _thread-safety_ recommendations: avoid using [Channel](https://nim-lang.org/0.20.0/channels.html) to communicate main thread and the _Waku Thread_.
|
||||
|
||||
**[HTTP REST API: Store, Filter, Lightpush, Admin and Private APIs](https://github.com/waku-org/nwaku/issues/1076)** {E:2023-many-platforms}
|
||||
|
||||
- _achieved_: Legacy Filter - v1 - interface Rest Api support added. V2 implementation done wait for PR review
|
||||
- _next_: Finish rebase to master, manual adapt of autoshard feature into Filter v2.
|
||||
|
||||
---
|
||||
### js-waku
|
||||
|
||||
**[Maintenance](https://github.com/waku-org/js-waku/issues/1455)** {E:2023-qa}
|
||||
|
||||
- _achieved_: store protocol refactor for readability
|
||||
|
||||
**[Peer Exchange is supported and used by default](https://github.com/waku-org/js-waku/issues/1429)** {E:2023-light-protocols}
|
||||
|
||||
- _achieved_: break down dogfooding into tasks for peer-exchange
|
||||
|
||||
**[Cover Several Environments As Part of Testing](https://github.com/waku-org/js-waku/issues/52)** {E:2023-qa}
|
||||
|
||||
- _achieved_: created front-end app to be run in a pipeline
|
||||
- _next_: complete app and run in the pipeline, figure out next steps to run Firefox
|
||||
|
||||
---
|
||||
### go-waku
|
||||
|
||||
**[RLN enabled by default](https://github.com/waku-org/go-waku/issues/655)** {E:2023-rln}
|
||||
|
||||
- _achieved_: run rln-relay on all configured pubsub topics and content topics, added metrics, made RLN database aware of chainID and contract address, refactored keystore.
|
||||
- _next_: test keystore interop with nwaku, integrate waku rln registry, and restore valid roots from DB
|
||||
|
||||
**[Auto-sharding v1](https://github.com/waku-org/go-waku/issues/623)** {E:2023-1mil-users}
|
||||
|
||||
- _achieved_: Implemented core logic for autosharding
|
||||
- _next_: API changes for autosharding
|
||||
|
||||
**[Improve Test Coverage](https://github.com/waku-org/go-waku/issues/620)** {E:2023-qa}
|
||||
|
||||
- _achieved_: Improved test coverage in utils.
|
||||
|
||||
**[Introduce Peer Management](https://github.com/waku-org/go-waku/issues/594)** {E:2023-peer-mgmt}
|
||||
|
||||
- _achieved_: Raised PR in status-go to use this version in order to dogfood. Local testing with status desktop
|
||||
- _next_: Dogfood changes with Status desktop and mobile using Waku CC's
|
||||
|
||||
---
|
||||
|
|
@ -0,0 +1,87 @@
|
|||
---
|
||||
title: 2023-09-04 Waku weekly
|
||||
tags:
|
||||
- waku-updates
|
||||
date: 2023-09-04
|
||||
lastmod: 2023-09-04
|
||||
draft: false
|
||||
---
|
||||
|
||||
## 2023-09-04 Waku weekly
|
||||
---
|
||||
### Epics
|
||||
|
||||
**[1.1 Network requirements and task breakdown](https://github.com/waku-org/pm/issues/62)** {E:2023-1mil-users}
|
||||
|
||||
- _achieved_: Started working on Waku Network RFC. Visibility and traceability in GH improvements.
|
||||
- _next_: Continue working on Waku Network RFC.
|
||||
|
||||
---
|
||||
### nwaku
|
||||
|
||||
**[setting up static sharding fleet for Status](https://github.com/waku-org/nwaku/issues/1914)** {E:2023-10k-users}
|
||||
|
||||
- _achieved_: negotiation with infra to improve fleet definition, clarify postgresql deployment
|
||||
- _next_: ensure fleet gets deployed as specified
|
||||
|
||||
**[Release Process Improvements](https://github.com/waku-org/nwaku/issues/1889)** {E:2023-qa}
|
||||
|
||||
- _achieved_: minor fixes in GH action workflows, building `experimental` (i.e. RLN enabled) image per-PR to simlify RLN testing/simulations
|
||||
- _next_: document how to run PR built images in waku-simulator, adding Linux arm64 binaries and images
|
||||
|
||||
**[PostgreSQL](https://github.com/waku-org/nwaku/issues/1888)** {E:2023-10k-users}
|
||||
|
||||
- _achieved_: Download and start configuring `jmeter` to have a variable number of clients sending concurrent _Store_ requests.
|
||||
- _next_: Carry on with stress testing & follow-up of the _Postgres_ addition to [wakuv2.shards](https://github.com/status-im/infra-nim-waku/blob/master/ansible/group_vars/wakuv2-shards.yml) by the _infra_ team.
|
||||
|
||||
**[nwaku c-bindings](https://github.com/waku-org/nwaku/issues/1332)** {E:2023-many-platforms}
|
||||
|
||||
- _achieved_: Merged PR that made the _Waku Node_ to be created within the _Waku Thread_. Submitted a PR that aims to make a safer the communication between the main thread and the _Waku Thread_.
|
||||
- _next_: Merge the PR to enhance communication between threads and start extracting the thread context outside the library (comment: 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:2023-many-platforms}
|
||||
|
||||
- _achieved_: Legacy Filter - v1 - interface Rest Api support added. V2 implementation done wait for PR review
|
||||
- _next_: Complete Filter v2 PR foundings fixes.
|
||||
- _blocking_: PR review found a design flow, need a little redesign.
|
||||
|
||||
---
|
||||
### js-waku
|
||||
|
||||
**[Maintenance](https://github.com/waku-org/js-waku/issues/1455)** {E:2023-qa}
|
||||
|
||||
- _achieved_: @chainsafe/libp2p-gossipsub is updated
|
||||
|
||||
**[Developer Experience (2023)](https://github.com/waku-org/js-waku/issues/1453)** {E:2023-eco-growth}
|
||||
|
||||
- _achieved_: pre-emptive stream creations for light protocols, using lowest latency peers for light protocols (WIP)
|
||||
- _next_: merging lowest latency peer PR
|
||||
|
||||
**[Waku Relay scalability in the Browser](https://github.com/waku-org/js-waku/issues/905)**
|
||||
|
||||
- _achieved_: complete PoC of Waku Relay over WebRTC using circuit relay
|
||||
- _next_: pause this to prioritize Waku Network milestone
|
||||
|
||||
**[Cover Several Environments As Part of Testing](https://github.com/waku-org/js-waku/issues/52)** {E:2023-qa}
|
||||
|
||||
- _achieved_: finishing testing against chrome and react;
|
||||
- _next_: investigate other adding browsers;
|
||||
|
||||
---
|
||||
### go-waku
|
||||
|
||||
**[RLN enabled by default](https://github.com/waku-org/go-waku/issues/655)** {E:2023-rln}
|
||||
|
||||
- _achieved_: test keystore interop with nwaku, integrate waku rln registry, and restore valid roots from DB
|
||||
- _next_: ordered validator execution, bandwidth validation, upgrade zerokit
|
||||
|
||||
**[Maintenance](https://github.com/waku-org/go-waku/issues/634)** {E:2023-qa}
|
||||
|
||||
- _achieved_: allow mixing named and static shards, logs succesful message pushes, concurrency fixes for filterv2
|
||||
|
||||
**[Auto-sharding v1](https://github.com/waku-org/go-waku/issues/623)** {E:2023-1mil-users}
|
||||
|
||||
- _achieved_: Implemented new config for autosharding and ENR updates with shard info
|
||||
- _next_: update various protocols to autoshard
|
||||
|
||||
---
|
||||
Loading…
Reference in New Issue