mirror of
https://github.com/vacp2p/roadmap.git
synced 2026-01-08 21:27:58 -05:00
DST Commitments proposal Q1 2026 (#344)
Draft version of the 2026Q1 commitments. I maintained old names, but I guess this can be changed to logos-* if necessary.
This commit is contained in:
Alberto Soutullo
56
content/dst/anoncomms/2026q1-anoncomms-evaluation.md
Normal file
56
content/dst/anoncomms/2026q1-anoncomms-evaluation.md
Normal file
@@ -0,0 +1,56 @@
|
||||
---
|
||||
title: Anoncomms Evaluation
|
||||
tags:
|
||||
- "2026q1"
|
||||
- "dst"
|
||||
- "anoncomms"
|
||||
draft: false
|
||||
description: "Test new anoncomms binaries on each new version
|
||||
or requested feature
|
||||
and look for regressions,
|
||||
learn scaling properties and run scaling studies."
|
||||
---
|
||||
|
||||
`vac:dst:anoncomms:2026q1-anoncomms-evaluation`
|
||||
|
||||
## Description
|
||||
Test Anoncomms protocols on each new version or requested feature
|
||||
and look for regressions,
|
||||
learn scaling properties and run scaling studies,
|
||||
understand the limits of anoncomms projects and its behaviour.
|
||||
Deliver reports and actionable insights.
|
||||
Do this monthly, reliably, with documentation of findings.
|
||||
|
||||
## Task list
|
||||
|
||||
### Mix
|
||||
> *Note*: This needs more input from project
|
||||
|
||||
* fully qualified name: `vac:dst:anoncomms:2026q1-anoncomms-evaluation:mix`
|
||||
* owner: TBD
|
||||
* status: not started
|
||||
* start-date: 2026/01/01
|
||||
* end-date: 2026/03/31
|
||||
|
||||
#### Description
|
||||
TBD
|
||||
|
||||
#### Deliverables
|
||||
- Reports:
|
||||
- Related PRs if apply:
|
||||
|
||||
### KAD-DHT
|
||||
> *Note*: This needs more input from project
|
||||
|
||||
* fully qualified name: `vac:dst:anoncomms:2026q1-anoncomms-evaluation:kad-dht`
|
||||
* owner: TBD
|
||||
* status: not started
|
||||
* start-date: 2026/01/01
|
||||
* end-date: 2026/03/31
|
||||
|
||||
#### Description
|
||||
TBD
|
||||
|
||||
#### Deliverables
|
||||
- Reports:
|
||||
- Related PRs if apply:
|
||||
66
content/dst/codex/2026q1-codex-evaluation.md
Normal file
66
content/dst/codex/2026q1-codex-evaluation.md
Normal file
@@ -0,0 +1,66 @@
|
||||
---
|
||||
title: Codex Evaluation
|
||||
tags:
|
||||
- "2026q1"
|
||||
- "dst"
|
||||
- "codex"
|
||||
draft: false
|
||||
description: "Test Codex on each new version or requested feature
|
||||
and look for regressions,
|
||||
learn scaling properties and run scaling studies."
|
||||
---
|
||||
|
||||
`vac:dst:codex:2026q1-codex-evaluation`
|
||||
|
||||
|
||||
## Description
|
||||
Test Codex on each new version or requested feature
|
||||
and look for regressions if this is required.
|
||||
Help Codex with testing and benchmarking new features.
|
||||
|
||||
### Background
|
||||
|
||||
We want to learn specific, actionable information
|
||||
about Codex's behaviour
|
||||
and how it is evolving over time
|
||||
with each new release
|
||||
and with each thing we are specifically asked to check and test.
|
||||
|
||||
We will use a combination of real world testing,
|
||||
theoretical analysis and experiments.
|
||||
|
||||
## Task List
|
||||
|
||||
### Filehsharing client
|
||||
|
||||
* fully qualified name: `vac:dst:codex:2026q1-codex-evaluation:filesharing-client`
|
||||
* owner: TBD
|
||||
* status: not started
|
||||
* start-date: 2026/01/01
|
||||
* end-date: 2026/03/31
|
||||
|
||||
#### Description
|
||||
|
||||
Assist the Codex team to check the functionality of the
|
||||
filesharing client implementation under heavy/big workloads.
|
||||
|
||||
#### Deliverables
|
||||
- Reports:
|
||||
- Related PRs if apply:
|
||||
|
||||
### Filehsharing client + mix
|
||||
|
||||
* fully qualified name: `vac:dst:codex:2026q1-codex-evaluation:filesharing-client-mix`
|
||||
* owner: TBD
|
||||
* status: not started
|
||||
* start-date: 2026/01/01
|
||||
* end-date: 2026/03/31
|
||||
|
||||
#### Description
|
||||
|
||||
Assist the Codex team to check the functionality of the
|
||||
filesharing client implementation under heavy/big workloads using mix protocol.
|
||||
|
||||
#### Deliverables
|
||||
- Reports:
|
||||
- Related PRs if apply:
|
||||
82
content/dst/ift/2026q1-dst-lab.md
Normal file
82
content/dst/ift/2026q1-dst-lab.md
Normal file
@@ -0,0 +1,82 @@
|
||||
---
|
||||
title: DST Lab
|
||||
tags:
|
||||
- "2026q1"
|
||||
- "dst"
|
||||
- "ift"
|
||||
draft: false
|
||||
description: "Scale and apply the VacLab to IFT's needs.
|
||||
Anticipate untapped use cases and needs from other teams.
|
||||
Improve the usage of the lab by optimizing resources and time allocation."
|
||||
---
|
||||
|
||||
`vac:dst:ift:2026q1-dst-lab`
|
||||
|
||||
## Description
|
||||
|
||||
DST lab is a set of machines that are mainly used in a composed Kubernetes cluster.
|
||||
In this environment, we can do a set of experiments to test regressions,
|
||||
new functionalities and features, or experimental changes on any decentralized system.
|
||||
In these experiments, we look for abnormal behaviors, we do measurements to study
|
||||
the performance and robustness of the system. These results can be also used to compare
|
||||
with theoretical results and analyze the scaling behaviors of the systems.
|
||||
At the same time, we will work on improving the lab's resources and time allocation,
|
||||
while allow provisioning to other teams dedicated machines if they are needed.
|
||||
|
||||
|
||||
## Task list
|
||||
|
||||
### Analyze current stack
|
||||
|
||||
* fully qualified name: `vac:dst:ift:2026q1-dst-lab:analyze-current-stack`
|
||||
* owner: Mamoutou
|
||||
* status: not started
|
||||
* start-date: 2026/01/01
|
||||
* end-date: 2026/03/31
|
||||
|
||||
#### Description
|
||||
Compare the current stack with new stack proposals.
|
||||
Study if changes are helpful and improve overall performance of the lab.
|
||||
Report findings with analysis and benchmarks of the results.
|
||||
|
||||
#### Deliverables
|
||||
- Code:
|
||||
- Reports:
|
||||
|
||||
|
||||
### Optimize data scrapping
|
||||
|
||||
* fully qualified name: `vac:dst:ift:2026q1-dst-lab:optimize-data-scrapping`
|
||||
* owner: Mamoutou
|
||||
* status: not started
|
||||
* start-date: 2026/01/01
|
||||
* end-date: 2026/03/31
|
||||
|
||||
#### Description
|
||||
Improve the monitoring system of the lab. Adjust scraping frequency and selected metrics.
|
||||
Design a storage solution to store the data so it can be retrieved if necessary.
|
||||
Optimize the storage to reduce used space if data is older than a certain period.
|
||||
|
||||
#### Deliverables
|
||||
- Code:
|
||||
- Reports:
|
||||
|
||||
|
||||
### Lab health monitoring
|
||||
|
||||
* fully qualified name: `vac:dst:ift:2026q1-dst-lab:lab-health-monitoring`
|
||||
* owner: Mamoutou
|
||||
* status: not started
|
||||
* start-date: 2026/01/01
|
||||
* end-date: 2026/03/31
|
||||
|
||||
#### Description
|
||||
Design a set of metrics/dashboards that can be used to monitor the health of the lab.
|
||||
The metrics should be useful to detect abnormal behaviors and to detect potential issues.
|
||||
What we want to achieve with this is to be sure that we can compare experiments from one
|
||||
week to a different week being confident that the results can be trusted, without the need
|
||||
of repeat the same experiment again.
|
||||
|
||||
#### Deliverables
|
||||
- Code:
|
||||
- Reports:
|
||||
126
content/dst/ift/2026q1-dst-tooling.md
Normal file
126
content/dst/ift/2026q1-dst-tooling.md
Normal file
@@ -0,0 +1,126 @@
|
||||
---
|
||||
title: DST Tooling
|
||||
tags:
|
||||
- "2026q1"
|
||||
- "dst"
|
||||
- "ift"
|
||||
draft: false
|
||||
description: "Creating tools that allow
|
||||
DST to easily work with other IFT projects.
|
||||
This includes functionalities such as deployments,
|
||||
monitoring, analysis, and control of aforementioned software's."
|
||||
---
|
||||
|
||||
`vac:dst:ift:2026q1-dst-tooling`
|
||||
|
||||
## Description
|
||||
|
||||
We will create tools to help DST efficiency.
|
||||
These tools can be composed of utilities for Kubernetes,
|
||||
or any other kind that fits the necessities of DST and other projects.
|
||||
As projects might share common necessities, this tasks will be considered
|
||||
as a scaffold for DST tools, adapting the tools for each project if it needs.
|
||||
The primary focus will be on adapting the necessities of the Waku team for
|
||||
the log parser tool. This will comprise retrieving information from a given
|
||||
message id, history of discovered peers, subscriptions, while having good
|
||||
performance and supportability.
|
||||
Additionally, the project will define workflows that facilitate the creation
|
||||
and execution of specialized scenarios. These scenarios will assist in
|
||||
the analysis of libp2p and Gossipsub, supporting studies focused on
|
||||
adversarial conditions and control message behavior.
|
||||
|
||||
|
||||
## Task list
|
||||
|
||||
### General tooling (recurring)
|
||||
|
||||
* fully qualified name: `vac:dst:ift:2026q1-dst-tooling:general-tooling`
|
||||
* owner: TBD
|
||||
* status: not started
|
||||
* start-date: 2026/01/01
|
||||
* end-date: 2026/03/31
|
||||
|
||||
#### Description
|
||||
Group of utilities that are added to the main repository.
|
||||
Should be made general when possible.
|
||||
|
||||
#### Deliverables
|
||||
- PRs:
|
||||
- Documents:
|
||||
|
||||
### Expand deployment - Waku
|
||||
|
||||
* fully qualified name: `vac:dst:ift:2026q1-dst-tooling:expand-deployment-waku`
|
||||
* owner: TBD
|
||||
* status: not started
|
||||
* start-date: 2026/01/01
|
||||
* end-date: 2026/03/31
|
||||
|
||||
#### Description
|
||||
Waku is planning to deliver specific binaries with encapsulated configurations to DST
|
||||
Adjust deployment builders to support these new binaries and be able to run
|
||||
specific experiments with them.
|
||||
|
||||
#### Deliverables
|
||||
- PRs:
|
||||
- Related Documents:
|
||||
|
||||
### Expand deployment - nim-libp2p
|
||||
|
||||
* fully qualified name: `vac:dst:ift:2026q1-dst-tooling:expand-deployment-nim-libp2p`
|
||||
* owner: TBD
|
||||
* status: not started
|
||||
* start-date: 2026/01/01
|
||||
* end-date: 2026/03/31
|
||||
|
||||
#### Description
|
||||
Adjust deployment builders to support nim-libp2p.
|
||||
|
||||
#### Deliverables
|
||||
- PRs:
|
||||
- Related Documents:
|
||||
|
||||
### Expand deployment - codex
|
||||
|
||||
* fully qualified name: `vac:dst:ift:2026q1-dst-tooling:expand-deployment-codex`
|
||||
* owner: TBD
|
||||
* status: not started
|
||||
* start-date: 2026/01/01
|
||||
* end-date: 2026/03/31
|
||||
|
||||
#### Description
|
||||
Adjust deployment builders to support codex.
|
||||
|
||||
#### Deliverables
|
||||
- PRs:
|
||||
- Related Documents:
|
||||
|
||||
### Expand deployment - nomos
|
||||
|
||||
* fully qualified name: `vac:dst:ift:2026q1-dst-tooling:expand-deployment-nomos`
|
||||
* owner: TBD
|
||||
* status: not started
|
||||
* start-date: 2026/01/01
|
||||
* end-date: 2026/03/31
|
||||
|
||||
#### Description
|
||||
Adjust deployment builders to support nomos.
|
||||
|
||||
#### Deliverables
|
||||
- PRs:
|
||||
- Related Documents:
|
||||
|
||||
### Expand deployment - anoncomms
|
||||
|
||||
* fully qualified name: `vac:dst:ift:2026q1-dst-tooling:expand-deployment-anoncomms`
|
||||
* owner: TBD
|
||||
* status: not started
|
||||
* start-date: 2026/01/01
|
||||
* end-date: 2026/03/31
|
||||
|
||||
#### Description
|
||||
Adjust deployment builders to support provided anoncomms binaries.
|
||||
|
||||
#### Deliverables
|
||||
- PRs:
|
||||
- Related Documents:
|
||||
@@ -20,6 +20,32 @@ are not only effective but also maintain or improve system performance and scala
|
||||
|
||||
[[dst/preview|Roadmap Preview]]
|
||||
|
||||
## 2026q1 `vac:dst:`
|
||||
---
|
||||
### `anoncomms`
|
||||
* [[dst/anoncomms/2026q1-anoncomms-evaluation|anoncomms-evaluation]]
|
||||
|
||||
### `codex`
|
||||
* [[dst/codex/2026q1-codex-evaluation|codex-evaluation]]
|
||||
|
||||
### `ift`
|
||||
* [[dst/ift/2026q1-dst-lab|dst-lab]]
|
||||
* [[dst/ift/2026q1-dst-tooling|dst-tooling]]
|
||||
|
||||
### `logos-core`
|
||||
* [[dst/logos-core/2026q1-logos-core-evaluation|logos-core-evaluation]]
|
||||
|
||||
### `nomos`
|
||||
* [[dst/nomos/2026q1-nomos-evaluation|nomos-evaluation]]
|
||||
|
||||
### `vac`
|
||||
* [[dst/vac/2026q1-libp2p-evaluation|libp2p-evaluation]]
|
||||
|
||||
### `waku`
|
||||
* [[dst/waku/2026q1-waku-evaluation|waku-evaluation]]
|
||||
* [[dst/waku/2026q1-waku-scaling|waku-scaling]]
|
||||
|
||||
---
|
||||
## 2025q4 `vac:dst:`
|
||||
---
|
||||
|
||||
|
||||
111
content/dst/logos-core/2026q1-logos-core-evaluation.md
Normal file
111
content/dst/logos-core/2026q1-logos-core-evaluation.md
Normal file
@@ -0,0 +1,111 @@
|
||||
---
|
||||
title: Logos-core Evaluation
|
||||
tags:
|
||||
- "2026q1"
|
||||
- "dst"
|
||||
- "logos-core"
|
||||
draft: false
|
||||
description: "Perform integration scenarios in logos core
|
||||
with different components and evaluate their behaviour."
|
||||
---
|
||||
|
||||
`vac:dst:logos-core:2026q1-logos-core-evaluation`
|
||||
|
||||
|
||||
## Description
|
||||
|
||||
Realize integration scenarios in logos core with
|
||||
different components and evaluate their behavior.
|
||||
Scenarios should work independently with each component,
|
||||
while also work in a full stack manner.
|
||||
These componentes are logos-messaging, logos-storage and logos-blockchain.
|
||||
|
||||
## Task list
|
||||
> Schedule note: Dates reflect quarter bounds; update when actual timing is known.
|
||||
> Note: This needs more input from the project.
|
||||
|
||||
### logos-core evaluation
|
||||
|
||||
* fully qualified name: `vac:dst:logos-core:2026q1-logos-core-evaluation:evaluation`
|
||||
* owner: TBD
|
||||
* status: not started
|
||||
* start-date: 2026/01/01
|
||||
* end-date: 2026/03/31
|
||||
|
||||
#### Description
|
||||
Integrate logos-core in the DST lab, evaluating its behaviour.
|
||||
Prepare new tools if needed, and report performance or
|
||||
issues if they are found.
|
||||
|
||||
#### Deliverables
|
||||
* Analysis:
|
||||
|
||||
|
||||
### logos-messaging
|
||||
* fully qualified name: `vac:dst:logos-core:2026q1-logos-core-evaluation:logos-messaging`
|
||||
* owner: TBD
|
||||
* status: not started
|
||||
* start-date: 2026/01/01
|
||||
* end-date: 2026/03/31
|
||||
|
||||
#### Description
|
||||
|
||||
Add logos-messaging component into the evaluation.
|
||||
Realize the same scenarios and reports as in `evaluation` task.
|
||||
|
||||
#### Deliverables
|
||||
- Reports:
|
||||
- Related PRs if apply:
|
||||
|
||||
### logos-storage
|
||||
* fully qualified name: `vac:dst:logos-core:2026q1-logos-core-evaluation:logos-storage`
|
||||
* owner: TBD
|
||||
* status: not started
|
||||
* start-date: 2026/01/01
|
||||
* end-date: 2026/03/31
|
||||
|
||||
#### Description
|
||||
|
||||
Add logos-storage component into the evaluation.
|
||||
Realize the same scenarios and reports as in `evaluation` task.
|
||||
|
||||
|
||||
#### Deliverables
|
||||
- Reports:
|
||||
- Related PRs if apply:
|
||||
|
||||
|
||||
### logos-blockchain
|
||||
* fully qualified name: `vac:dst:logos-core:2026q1-logos-core-evaluation:logos-blockchain`
|
||||
* owner: TBD
|
||||
* status: not started
|
||||
* start-date: 2026/01/01
|
||||
* end-date: 2026/03/31
|
||||
|
||||
#### Description
|
||||
|
||||
Add logos-blockchain component into the evaluation.
|
||||
Realize the same scenarios and reports as in `evaluation` task.
|
||||
|
||||
|
||||
#### Deliverables
|
||||
- Reports:
|
||||
- Related PRs if apply:
|
||||
|
||||
|
||||
### full stack
|
||||
* fully qualified name: `vac:dst:logos-core:2026q1-logos-core-evaluation:full-stack`
|
||||
* owner: TBD
|
||||
* status: not started
|
||||
* start-date: 2026/01/01
|
||||
* end-date: 2026/03/31
|
||||
|
||||
#### Description
|
||||
|
||||
Add all components into the evaluation.
|
||||
Realize the same scenarios and reports as in `evaluation` task.
|
||||
|
||||
|
||||
#### Deliverables
|
||||
- Reports:
|
||||
- Related PRs if apply:
|
||||
88
content/dst/nomos/2026q1-nomos-evaluation.md
Normal file
88
content/dst/nomos/2026q1-nomos-evaluation.md
Normal file
@@ -0,0 +1,88 @@
|
||||
---
|
||||
title: Nomos Evaluation
|
||||
tags:
|
||||
- "2026q1"
|
||||
- "dst"
|
||||
- "nomos"
|
||||
draft: false
|
||||
description: "Test Nomos on each new version or requested feature
|
||||
and look for regressions,
|
||||
learn scaling properties and run scaling studies."
|
||||
---
|
||||
|
||||
`vac:dst:nomos:2026q1-nomos-evaluation`
|
||||
|
||||
|
||||
## Description
|
||||
> *Note*: This needs more input from project
|
||||
|
||||
Use real world testing,
|
||||
theoretical analysis
|
||||
and simulation
|
||||
to determine and improve Nomos's scaling properties.
|
||||
Find the limits of Nomos's capabilities
|
||||
and measure them in different scenarios.
|
||||
|
||||
We will measure the real world speeds and latency of Nomos' mixnet,
|
||||
and what use cases it is therefore able to support.
|
||||
|
||||
The scope of this commitment depends on the Nomos team
|
||||
work and improvements, and it is subjected to change.
|
||||
|
||||
## Task List
|
||||
|
||||
### Blend benchmarking
|
||||
> *Note*: This was moved from previous quarter
|
||||
|
||||
* fully qualified name: `vac:dst:nomos:2026q1-nomos-evaluation:blendnet-benchmarking`
|
||||
* owner: Alberto
|
||||
* status: not started
|
||||
* start-date: 2026/01/01
|
||||
* end-date: 2026/03/31
|
||||
|
||||
#### Description
|
||||
|
||||
Measure the speed and reliability of Nomos's blendnet.
|
||||
|
||||
Schedule note: Dates reflect quarter bounds; update when actual timing is known.
|
||||
#### Deliverables
|
||||
* Benchmarks done
|
||||
* Report published with all relevant details
|
||||
|
||||
|
||||
### DA benchmarking
|
||||
> *Note*: This was moved from previous quarter
|
||||
|
||||
* fully qualified name: `vac:dst:nomos:2026q1-nomos-evaluation:da-benchmarking`
|
||||
* owner: TBD
|
||||
* status: not started
|
||||
* start-date: 2026/01/01
|
||||
* end-date: 2026/03/31
|
||||
|
||||
#### Description
|
||||
|
||||
Measure Nomos bandwidth usage in DA per node and entire network.
|
||||
|
||||
Schedule note: Dates reflect quarter bounds; update when actual timing is known.
|
||||
#### Deliverables
|
||||
* PRS:
|
||||
* Documents:
|
||||
|
||||
|
||||
### Nomos consumption
|
||||
> *Note*: This was moved from previous quarter
|
||||
|
||||
* fully qualified name: `vac:dst:nomos:2026q1-nomos-evaluation:consumption`
|
||||
* owner: TBD
|
||||
* status: not started
|
||||
* start-date: 2026/01/01
|
||||
* end-date: 2026/03/31
|
||||
|
||||
#### Description
|
||||
|
||||
Measure Nomos resource consumption (CPU/RAM) usage in different scenarios.
|
||||
|
||||
Schedule note: Dates reflect quarter bounds; update when actual timing is known.
|
||||
#### Deliverables
|
||||
* PRS:
|
||||
* Documents:
|
||||
@@ -7,24 +7,7 @@ tags:
|
||||
|
||||
## Roadmap Preview
|
||||
|
||||
### Q4 other potential commitments
|
||||
|
||||
- Nomos
|
||||
- Analyze scaling behavior
|
||||
- Network dynamis (message propagation, network topology, etc.)
|
||||
- Consensus scaling (throughput vs numbers of validators, etc) (probably done)
|
||||
- State/transaction layer bottlenecks (liveness/safety, etc) (probably done)
|
||||
- Adversarial robustness (prob done?)
|
||||
- Decentralization metrics (hardware requirements)
|
||||
|
||||
- VAC
|
||||
- Improve lab infrastructure.
|
||||
- Analyze current stack, find improvements
|
||||
- Automatize flow of delivering machines
|
||||
- Plug data from DST experiments in infra cortex
|
||||
- Optimize data scraping from DST experiments (datapoints from metrics, logs)
|
||||
|
||||
### 2026Q1
|
||||
### 2026Q1 other potential commitments
|
||||
- Waku
|
||||
- Keep assisting waku team with regression analysis on each new version
|
||||
- Perform theoretical and statistical models
|
||||
@@ -38,15 +21,19 @@ tags:
|
||||
- Codex
|
||||
- Start assisting Codex in regression analysis on each new version
|
||||
- Perform theoretical and statistical models
|
||||
- Analyze scaling behavior
|
||||
|
||||
- nim-libp2p
|
||||
- Keep assisting p2p team with regression analysis on each new version
|
||||
- Benchmark new functionalities (Webtransport, KAD-DHT, ...)
|
||||
- Perform theoretical and statistical models
|
||||
- Analyze scaling behavior
|
||||
|
||||
- logos-core
|
||||
- Discuss how the scenarios can be realized and what specific features are needed.
|
||||
|
||||
- VAC
|
||||
- Improve lab infrastructure.
|
||||
- Automatize flow of delivering machines
|
||||
- Plug data from DST experiments in infra cortex
|
||||
- Introduce live dashboards capable of providing real-time insights into running experiments (e.g., message delivery times, participant node status, etc.)
|
||||
- Expand dashboard utilities to interact with real-time experiments.
|
||||
- Keep supporting FURPS by doing necessary experiments to projects.
|
||||
@@ -71,7 +58,7 @@ tags:
|
||||
|
||||
- nim-libp2p
|
||||
- Keep assisting p2p team with regression analysis on each new version
|
||||
- Benchmark new functionalities (Webtransport, KAD-DHT, ...)
|
||||
- Benchmark new functionalities (Webtransport, ...)
|
||||
- Perform theoretical and statistical models
|
||||
- Analyze scaling behavior
|
||||
|
||||
|
||||
102
content/dst/vac/2026q1-libp2p-evaluation.md
Normal file
102
content/dst/vac/2026q1-libp2p-evaluation.md
Normal file
@@ -0,0 +1,102 @@
|
||||
---
|
||||
title: Libp2p Evaluation
|
||||
tags:
|
||||
- "2026q1"
|
||||
- "dst"
|
||||
- "vac"
|
||||
draft: false
|
||||
description: "Test libp2p on each new version or feature
|
||||
and look for regressions,
|
||||
learn scaling properties and run scaling studies."
|
||||
---
|
||||
|
||||
`vac:dst:vac:2026q1-libp2p-evaluation`
|
||||
|
||||
|
||||
## Description
|
||||
|
||||
Test libp2p on each new version or requested feature
|
||||
and look for regressions,
|
||||
learn scaling properties and run scaling studies,
|
||||
understand the limits of Waku and its behaviour.
|
||||
Deliver reports and actionable insights.
|
||||
Do this monthly, reliably, with documentation of findings.
|
||||
|
||||
The scope of this commitment depends on the P2P team
|
||||
work and improvements, and it is subjected to change.
|
||||
|
||||
## Task list
|
||||
> Schedule note: Dates reflect quarter bounds; update when actual timing is known.
|
||||
|
||||
### Regression testing (recurring)
|
||||
|
||||
* fully qualified name: `vac:dst:vac:2026q1-libp2p-evaluation:regression-testing`
|
||||
* owner: TBD
|
||||
* status: not started
|
||||
* start-date: 2026/01/01
|
||||
* end-date: 2026/03/31
|
||||
|
||||
#### Description
|
||||
Run different scenarios
|
||||
and collect evidence and data
|
||||
of libp2p's behaviour.
|
||||
|
||||
Test for known regressions
|
||||
that have occurred in the past
|
||||
and ensure they don't happen again.
|
||||
|
||||
#### Deliverables
|
||||
* Analysis:
|
||||
|
||||
|
||||
### ls-quic
|
||||
* fully qualified name: `vac:dst:vac:2026q1-libp2p-evaluation:ls-quic`
|
||||
* owner: TBD
|
||||
* status: not started
|
||||
* start-date: 2026/01/01
|
||||
* end-date: 2026/03/31
|
||||
|
||||
#### Description
|
||||
|
||||
Help P2P with the development of ls-quic by providing benchmarks and feedback
|
||||
between different commits.
|
||||
|
||||
|
||||
#### Deliverables
|
||||
- Reports:
|
||||
- Related PRs if apply:
|
||||
|
||||
|
||||
### Quic-vs-tcp
|
||||
> *Note*: This was moved from previous quarter
|
||||
|
||||
* fully qualified name: `vac:dst:vac:2026q1-libp2p-evaluation:quic-vs-tcp`
|
||||
* owner: TBD
|
||||
* status: not started
|
||||
* start-date: 2026/01/01
|
||||
* end-date: 2026/03/31
|
||||
|
||||
#### Description
|
||||
|
||||
Perform a comparison between nim-libp2p using quic and waku using mplex and yamux.
|
||||
|
||||
#### Deliverables
|
||||
- Reports:
|
||||
- Related PRs if apply:
|
||||
|
||||
|
||||
### ls-quic
|
||||
* fully qualified name: `vac:dst:vac:2026q1-libp2p-evaluation:ls-quic`
|
||||
* owner: TBD
|
||||
* status: not started
|
||||
* start-date: 2026/01/01
|
||||
* end-date: 2026/03/31
|
||||
|
||||
#### Description
|
||||
|
||||
Help P2P with the development of ls-quic by providing benchmarks and feedback
|
||||
between different commits.
|
||||
|
||||
#### Deliverables
|
||||
- Reports:
|
||||
- Related PRs if apply:
|
||||
45
content/dst/waku/2026q1-waku-evaluation.md
Normal file
45
content/dst/waku/2026q1-waku-evaluation.md
Normal file
@@ -0,0 +1,45 @@
|
||||
---
|
||||
title: Waku Evaluation
|
||||
tags:
|
||||
- "2026q1"
|
||||
- "dst"
|
||||
- "waku"
|
||||
draft: false
|
||||
description: "Test Waku on each new version or requested feature
|
||||
and look for regressions,
|
||||
learn scaling properties and run scaling studies."
|
||||
---
|
||||
|
||||
`vac:dst:waku:2026q1-waku-evaluation`
|
||||
|
||||
## Description
|
||||
Test Waku on each new version or requested feature
|
||||
and look for regressions,
|
||||
learn scaling properties and run scaling studies,
|
||||
understand the limits of Waku and its behaviour.
|
||||
Deliver reports and actionable insights.
|
||||
Do this monthly, reliably, with documentation of findings.
|
||||
|
||||
## Task list
|
||||
|
||||
### Regression testing (recurring)
|
||||
|
||||
* fully qualified name: `vac:dst:waku:2026q1-waku-evaluation:regression-testing`
|
||||
* owner: TBD
|
||||
* status: not started
|
||||
* start-date: 2026/01/01
|
||||
* end-date: 2026/01/01
|
||||
|
||||
#### Description
|
||||
Run different scenarios
|
||||
and collect evidence and data
|
||||
of Waku's behaviour.
|
||||
|
||||
Test for known regressions
|
||||
that have occurred in the past
|
||||
and ensure they don't happen again.
|
||||
|
||||
Schedule note: Dates reflect quarter bounds; update when actual timing is known.
|
||||
#### Deliverables
|
||||
- Reports:
|
||||
- Related PRs if apply:
|
||||
178
content/dst/waku/2026q1-waku-scaling.md
Normal file
178
content/dst/waku/2026q1-waku-scaling.md
Normal file
@@ -0,0 +1,178 @@
|
||||
---
|
||||
title: Waku Scaling
|
||||
tags:
|
||||
- "2026q1"
|
||||
- "dst"
|
||||
- "waku"
|
||||
draft: false
|
||||
description: "Use experiments determine and
|
||||
improve Waku's scaling properties.
|
||||
Find the limits of Waku's capabilities
|
||||
and measure them in different scenarios.
|
||||
Deliver hard numbers and actionable insights.
|
||||
Confirm or reject our ideas or presented ones."
|
||||
---
|
||||
|
||||
`vac:dst:waku:2026q1-waku-scaling`
|
||||
|
||||
## Description
|
||||
|
||||
We will use realistic Waku node experiments to evaluate
|
||||
and improve Waku's scalability by conducting
|
||||
performance measurements across its key components and tasks.
|
||||
These efforts contains supporting on-chain RLN memberships,
|
||||
strengthening the foundations for private chats, optimize
|
||||
browser bootstrapping for improved responsiveness,
|
||||
integrate nwaku in Status Desktop for seamless relay functionality,
|
||||
and implement the SDS protocol for group messaging reliability and recovery.
|
||||
|
||||
## Task list
|
||||
|
||||
### scalable data sync
|
||||
|
||||
* fully qualified name: `vac:dst:waku:2026q1-waku-scaling:scalable-data-sync`
|
||||
* owner: TBD
|
||||
* status: not started
|
||||
* start-date: 2026/01/01
|
||||
* end-date: 2026/03/31
|
||||
|
||||
#### Description
|
||||
|
||||
1. When sending a message in a group, the publisher can ensure the message
|
||||
was received by at least one recipient within `S` seconds **(Vac-DST)**.
|
||||
3. When receiving messages in group, the receiver can reach eventual
|
||||
consistency within `6*S` seconds **(Vac-DST)**.
|
||||
|
||||
#### Deliverables
|
||||
- PRs:
|
||||
- Related Documents:
|
||||
|
||||
|
||||
### Status communities
|
||||
|
||||
* fully qualified name: `vac:dst:waku:2026q1-waku-scaling:status-communities`
|
||||
* owner: TBD
|
||||
* status: not started
|
||||
* start-date: 2026/01/01
|
||||
* end-date: 2026/03/31
|
||||
|
||||
#### Description
|
||||
Logos-messaging specific FURPS, before Chat SDK integration.
|
||||
|
||||
1. Time to setup filter subscriptions for Communities has improved by >20% (**Vac-DST**).
|
||||
2. Time to retrieve 24 hours of Communities messages has improved by >20% (**Vac-DST**).
|
||||
3. Increased community traffic does not increase bandwidth usage of 1:1 chat (**Vac-DST**).
|
||||
|
||||
#### Deliverables
|
||||
- PRs:
|
||||
- Related Documents:
|
||||
|
||||
### Status private chats
|
||||
|
||||
* fully qualified name: `vac:dst:waku:2026q1-waku-scaling:status-private-chats`
|
||||
* owner: TBD
|
||||
* status: not started
|
||||
* start-date: 2026/01/01
|
||||
* end-date: 2026/03/31
|
||||
|
||||
#### Description
|
||||
1. 99% of one-to-one user messages are eventually received by their recipient, within 5 minutes of being online (**Vac-DST**).
|
||||
2. One-to-one chat’s non-user messages do not consume over 20% of the allocated quota (**Vac-DST**).
|
||||
|
||||
#### Deliverables
|
||||
- PRs:
|
||||
- Related Documents:
|
||||
|
||||
### Incentivisation
|
||||
|
||||
* fully qualified name: `vac:dst:waku:2026q1-waku-scaling:incentivisation`
|
||||
* owner: TBD
|
||||
* status: not started
|
||||
* start-date: 2026/01/01
|
||||
* end-date: 2026/03/31
|
||||
|
||||
#### Description
|
||||
Reliability
|
||||
3. In a stable network, a client can find, pay and send a message via a RLNaaS provider (**Vac-QA**)
|
||||
in 90% of cases **(Vac-DST)**
|
||||
3. A client can assess whether an RLNaaS provider has relayed their message (**Vac-QA**)
|
||||
in 90% of cases **(Vac-DST)**.
|
||||
|
||||
Performance:
|
||||
1. Assuming a block time of 5 seconds,
|
||||
a user can execute an RLNaaS payment and send a message within 30 seconds (Vac-DST)
|
||||
|
||||
#### Deliverables
|
||||
- PRs:
|
||||
- Related Documents:
|
||||
|
||||
### Rendezvous
|
||||
|
||||
* fully qualified name: `vac:dst:waku:2026q1-waku-scaling:rendezvous`
|
||||
* owner: TBD
|
||||
* status: not started
|
||||
* start-date: 2026/01/01
|
||||
* end-date: 2026/03/31
|
||||
|
||||
#### Description
|
||||
1. In an established network of 1k relay nodes on 10 shards with 1 bootstrap node,
|
||||
100 new relay nodes (relay + discv5 + Waku PX + rendezvous)
|
||||
can connect to 20 relay peers in the right shard within 1 minute (**Vac-DST**)
|
||||
; run simulation without rendezvous to see the difference
|
||||
|
||||
#### Deliverables
|
||||
- PRs:
|
||||
- Related Documents:
|
||||
|
||||
### RLN Relay
|
||||
|
||||
* fully qualified name: `vac:dst:waku:2026q1-waku-scaling:rln-relay`
|
||||
* owner: TBD
|
||||
* status: not started
|
||||
* start-date: 2026/01/01
|
||||
* end-date: 2026/03/31
|
||||
|
||||
#### Description
|
||||
1. In a network of 10k RLN Relay nodes with each node sending one 1-100KB message every 10-30s,
|
||||
messages are propagated within 500ms, with 99.9% success **(Vac-DST)**.
|
||||
2. In a network of 10k RLN Relay nodes,
|
||||
a spamming node will be disconnected from its peers in under 1 min. **(Vac-DST)**
|
||||
|
||||
#### Deliverables
|
||||
- PRs:
|
||||
- Related Documents:
|
||||
|
||||
### Store
|
||||
|
||||
* fully qualified name: `vac:dst:waku:2026q1-waku-scaling:store`
|
||||
* owner: TBD
|
||||
* status: not started
|
||||
* start-date: 2026/01/01
|
||||
* end-date: 2026/03/31
|
||||
|
||||
#### Description
|
||||
5. 95th percentile of hash queries are served in less than 10ms of less than 10 hashes;
|
||||
for a database less than 250 GB size and average message size under 500KiB **(Vac-DST)**.
|
||||
6. 90th percentile of time range queries are served in less than 10ms; if the query is
|
||||
less than 1 hour, using up to 10 content topics, for a database less than 250 GB size
|
||||
and average message size under 500KiB **(Vac-DST)**.
|
||||
|
||||
#### Deliverables
|
||||
- PRs:
|
||||
- Related Documents:
|
||||
|
||||
### Store sync
|
||||
|
||||
* fully qualified name: `vac:dst:waku:2026q1-waku-scaling:store-sync`
|
||||
* owner: TBD
|
||||
* status: not started
|
||||
* start-date: 2026/01/01
|
||||
* end-date: 2026/03/31
|
||||
|
||||
#### Description
|
||||
1. A sync of a 60 minutes time window happens under 60 seconds, assuming 15 msgs/second (total),
|
||||
150KB message size and a maximum of 10% pre-existing message discrepancy (**Vac-DST**).
|
||||
|
||||
#### Deliverables
|
||||
- PRs:
|
||||
- Related Documents:
|
||||
Reference in New Issue
Block a user