mirror of
https://github.com/vacp2p/roadmap.git
synced 2026-01-07 23:04:01 -05:00
Merge branch 'master' into acz-2025q3
This commit is contained in:
seugu
@@ -12,40 +12,46 @@ with the multi-admin support and implementing the last version RFC"
|
||||
|
||||
`vac:acz:ift:2025q2-de-mls-tesnet`
|
||||
|
||||
finalizing the de-MLS RFC with consensus integration
|
||||
finalizing the de-MLS RFC with consensus integration
|
||||
with the multi-admin support and implementing the last version RFC
|
||||
|
||||
## Description
|
||||
This commitment involves completing the de-MLS RFC by incorporating
|
||||
multi-administrator configurations with decentralized consensus and implementing it
|
||||
with a multi-admin setup over the Waku network.
|
||||
The process includes presenting the findings such as MLS over Waku and benchmarking,
|
||||
|
||||
This commitment involves completing the de-MLS RFC by incorporating
|
||||
multi-administrator configurations with decentralized consensus and implementing it
|
||||
with a multi-admin setup over the Waku network.
|
||||
The process includes presenting the findings such as MLS over Waku and benchmarking,
|
||||
then applying for the EF grant.
|
||||
|
||||
### Background
|
||||
de-MLS is a decentralized, scalable, end-to-end encrypted (E2EE) group messaging application
|
||||
with Ethereum-based authentication.
|
||||
The primary goal of this project is to develop a comprehensive and mature RFC that outlines
|
||||
decentralized, secure, and scalable group key generation,
|
||||
|
||||
de-MLS is a decentralized, scalable, end-to-end encrypted (E2EE) group messaging application
|
||||
with Ethereum-based authentication.
|
||||
The primary goal of this project is to develop a comprehensive and mature RFC that outlines
|
||||
decentralized, secure, and scalable group key generation,
|
||||
designed to accommodate large numbers of users within a single group.
|
||||
|
||||
During 2025q1, we removed centralized aspects of the RFC by integrating the
|
||||
consensus mechanism among the users for achieving true decentralization.
|
||||
During 2025q1, we removed centralized aspects of the RFC by integrating the
|
||||
consensus mechanism among the users for achieving true decentralization.
|
||||
Also, we relese the extended implementation that multi-waku node can cooperate.
|
||||
The implementation plan for this quarter is to extend the initial single admin approach
|
||||
to a multi-admin configuration with consensus operating across the Waku network.
|
||||
The implementation plan for this quarter is to extend the initial single admin approach
|
||||
to a multi-admin configuration with consensus operating across the Waku network.
|
||||
|
||||
### Narratives
|
||||
|
||||
we will reinforce the Conduit of Expertise narrative by:
|
||||
* Develop the foundational framework for a decentralized, scalable messaging application
|
||||
|
||||
* Develop the foundational framework for a decentralized, scalable messaging application
|
||||
* Research and implement the scalable and decentralized consensus mechanism.
|
||||
|
||||
We will also strengthen the Premier Research Destination narrative by:
|
||||
|
||||
* Develop a standardized decentralized messaging application over the Waku network,
|
||||
by providing a well-structured RFC and a proof of concept (PoC) that demonstrates
|
||||
by providing a well-structured RFC and a proof of concept (PoC) that demonstrates
|
||||
its base functionality within the ecosystem.
|
||||
This will allow teams and organizations to build their own messaging applications while
|
||||
This will allow teams and organizations to build their own messaging applications while
|
||||
benefiting from these features.
|
||||
* Create a proposal for the Ethereum Foundation (EF) to apply for EF grants to promote the project and
|
||||
* Create a proposal for the Ethereum Foundation (EF) to apply for EF grants to promote the project and
|
||||
gain support from the Ethereum ecosystem.
|
||||
|
||||
## Task List
|
||||
@@ -54,16 +60,22 @@ gain support from the Ethereum ecosystem.
|
||||
|
||||
* fully qualified name: `vac:acz:ift:2025q2-de-mls-tesnet:test-deployment`
|
||||
* owner: Ekaterina
|
||||
* status: started (10%)
|
||||
* status: on-hold
|
||||
* start-date: 2025/05/01
|
||||
* end-date: 2025/06/30
|
||||
|
||||
#### Description
|
||||
|
||||
This task is on hold until the next quarter q4-2025.
|
||||
It'll be done after consensus integration,
|
||||
as well as cutting off unnecessary web functionality that complicates testing.
|
||||
|
||||
Set up test deployment for the [de-MLS](https://github.com/vacp2p/de-mls) repository.
|
||||
|
||||
#### Deliverables
|
||||
A PR to the [de-MLS](https://github.com/vacp2p/de-mls) repository with
|
||||
|
||||
A PR to the [de-MLS](https://github.com/vacp2p/de-mls) repository with
|
||||
|
||||
* Docker configurations for deployment and testing.
|
||||
* Documentation for test deployment setup.
|
||||
|
||||
@@ -77,8 +89,8 @@ A PR to the [de-MLS](https://github.com/vacp2p/de-mls) repository with
|
||||
|
||||
#### Description
|
||||
|
||||
Writing a blog post about implementation details of single admin de-MLS with Waku node
|
||||
as delivery service based on [this PR](https://github.com/vacp2p/de-mls/pull/29)
|
||||
Writing a blog post about implementation details of single admin de-MLS with Waku node
|
||||
as delivery service based on [this PR](https://github.com/vacp2p/de-mls/pull/29)
|
||||
|
||||
#### Deliverables
|
||||
|
||||
@@ -94,138 +106,146 @@ A blogpost to [vac.dev/rlog/](https://vac.dev/rlog/)
|
||||
|
||||
#### Description
|
||||
|
||||
This task entails delivering the decentralized consensus
|
||||
This task entails delivering the decentralized consensus
|
||||
RFC which is fast and efficient for p2p networks.
|
||||
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- [A PR](https://github.com/vacp2p/rfc-index/pull/142) to [vacp2p/rfc-index](https://github.com/vacp2p/rfc-index) repo.
|
||||
[A PR](https://github.com/vacp2p/rfc-index/pull/142) to [vacp2p/rfc-index](https://github.com/vacp2p/rfc-index) repo.
|
||||
|
||||
### Update de-MLS RFC with multi admins
|
||||
### Update de-MLS RFC with multi admins
|
||||
|
||||
* fully qualified name: `vac:acz:ift:2025q2-de-mls-tesnet:multi-admin-rfc`
|
||||
* owner: Ugur
|
||||
* status: started (20%)
|
||||
* status: started (80%)
|
||||
* start-date: 2025/05/04
|
||||
* end-date: 2025/05/26
|
||||
|
||||
#### Description
|
||||
|
||||
Update and reorganize the decetnralized MLS RFC with the single and multi admin options.
|
||||
This task also contains the integrating the consensus RFC.
|
||||
Update and reorganize the decetnralized MLS RFC with the single and multi admin options.
|
||||
This task also contains the integrating the consensus RFC.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
* PR to vacp2p/rfc-index repo with related updates.
|
||||
* PR to vacp2p/rfc-index repo with related updates.
|
||||
|
||||
### CI Setup
|
||||
|
||||
* fully qualified name: `vac:acz:ift:2025q2-de-mls-tesnet:ci-setup`
|
||||
* owner: Ekaterina
|
||||
* status: not started
|
||||
* status: cancelled
|
||||
* start-date: 2025/06/01
|
||||
* end-date: 2025/06/30
|
||||
|
||||
#### Description
|
||||
|
||||
Set up continuous integration for the [de-MLS](https://github.com/vacp2p/de-mls) repository,
|
||||
including automated testing and code validation.
|
||||
At this stage it does not look possible to set up CI,
|
||||
perhaps we will return to this task in a slightly different form later on.
|
||||
|
||||
Set up continuous integration for the [de-MLS](https://github.com/vacp2p/de-mls) repository,
|
||||
including automated testing and code validation.
|
||||
|
||||
#### Deliverables
|
||||
A PR to the [de-MLS](https://github.com/vacp2p/de-mls) repository
|
||||
|
||||
A PR to the [de-MLS](https://github.com/vacp2p/de-mls) repository
|
||||
with a new CI pipeline for the repository that includes the waku node.
|
||||
|
||||
### Implement consesus layer
|
||||
|
||||
* fully qualified name: `vac:acz:ift:2025q2-de-mls-tesnet:consensus-layer`
|
||||
* owner: Ekaterina
|
||||
* status: not started
|
||||
* start-date:
|
||||
* end-date:
|
||||
* status: not started
|
||||
* start-date: 2025/06/16
|
||||
* end-date: 2025/06/30
|
||||
|
||||
#### Description
|
||||
|
||||
Implement a consensus mechanism for one admin based on RFC, i.e.
|
||||
in the end we want to see a separate module
|
||||
that will process all incoming proposals for group state changes
|
||||
Implement a consensus mechanism for one admin based on RFC, i.e.
|
||||
in the end we want to see a separate module
|
||||
that will process all incoming proposals for group state changes
|
||||
and receive a commit message as an output.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
* A PR to the [de-MLS repository](https://github.com/vacp2p/de-mls)
|
||||
* A PR to the [de-MLS repository](https://github.com/vacp2p/de-mls)
|
||||
containing new consensus layer as separate module with tests.
|
||||
|
||||
### Separate commit and proposal messages inside app
|
||||
|
||||
* fully qualified name: `vac:acz:ift:2025q2-de-mls-tesnet:commit-and-proposal`
|
||||
* owner: Ekaterina
|
||||
* status: started (10%)
|
||||
* status: done
|
||||
* start-date: 2025/05/05
|
||||
* end-date: 2025/06/06
|
||||
* end-date: 2025/06/30
|
||||
|
||||
#### Description
|
||||
|
||||
Before integrating the consensus, it is necessary to split the process of applying new commits
|
||||
Before integrating the consensus, it is necessary to split the process of applying new commits
|
||||
into the corresponding proposal and commits for applying the group state update.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
* A PR to the [de-MLS repository](https://github.com/vacp2p/de-mls)
|
||||
* A [PR](https://github.com/vacp2p/de-mls/pull/36) to the [de-MLS repository](https://github.com/vacp2p/de-mls)
|
||||
updating the API for separate commit and proposal messages.
|
||||
|
||||
### Put all proposall message in one queue
|
||||
|
||||
* fully qualified name: `vac:acz:ift:2025q2-de-mls-tesnet:global-message-queue`
|
||||
* owner: Ekaterina
|
||||
* status: not started
|
||||
* status: done
|
||||
* start-date: 2025/05/19
|
||||
* end-date: 2025/05/30
|
||||
|
||||
#### Description
|
||||
|
||||
At the first stage of implementation we separated adding and messages
|
||||
to a group and deleting from a group into different threads,
|
||||
we need one message queue to work with consensus.
|
||||
to a group and deleting from a group into different threads,
|
||||
we need one message queue to work with consensus.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
* A PR to the [de-MLS repository](https://github.com/vacp2p/de-mls)
|
||||
* A [PR](https://github.com/vacp2p/de-mls/pull/36) to the [de-MLS repository](https://github.com/vacp2p/de-mls)
|
||||
containing update of message processing
|
||||
|
||||
|
||||
### Update frontend
|
||||
### Update frontend
|
||||
|
||||
* fully qualified name: `vac:acz:ift:2025q2-de-mls-tesnet:frontend-updating`
|
||||
* owner: Ekaterina
|
||||
* status: started (5%)
|
||||
* status: cancelled
|
||||
* start-date: 2025/05/01
|
||||
* end-date: 2025/06/30
|
||||
|
||||
#### Description
|
||||
|
||||
The current frontend is difficult to maintain and besides adding new functionality
|
||||
This task is cancelled due to the lack of need to update the frontend for the de-MLS poc.
|
||||
|
||||
The current frontend is difficult to maintain and besides adding new functionality
|
||||
for testing now requires a lot of effort.
|
||||
In addition, communication via websockets needs to be reconsidered in terms of efficiency
|
||||
In addition, communication via websockets needs to be reconsidered in terms of efficiency.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
* A PR to the [de-MLS repository](https://github.com/vacp2p/de-mls)
|
||||
* A PR to the [de-MLS repository](https://github.com/vacp2p/de-mls)
|
||||
containing new frontend.
|
||||
|
||||
### Integrate wallet based registration
|
||||
### Integrate wallet based registration
|
||||
|
||||
* fully qualified name: `vac:acz:ift:2025q2-de-mls-tesnet:wallet-based-register`
|
||||
* owner: Ekaterina
|
||||
* status: not started
|
||||
* status: on-hold
|
||||
* start-date: 2025/06/01
|
||||
* end-date: 2025/06/30
|
||||
|
||||
#### Description
|
||||
|
||||
For the first version de-mls used a mock version for online registration,
|
||||
This task is on hold until the next quarter q3-2025 due to changing priorities
|
||||
and the unpredictable complexity of more relevant tasks.
|
||||
|
||||
For the first version de-mls used a mock version for online registration,
|
||||
now it makes sense to add wallet support for user authentication
|
||||
|
||||
#### Deliverables
|
||||
|
||||
* A PR to the [de-MLS repository](https://github.com/vacp2p/de-mls)
|
||||
containing support of wallet as authentication part.
|
||||
* A PR to the [de-MLS repository](https://github.com/vacp2p/de-mls)
|
||||
containing support of wallet as authentication part.
|
||||
|
||||
@@ -72,7 +72,7 @@ A document of a summary of the ZK call 2 meeting to [ZK Notion page](https://www
|
||||
### IFT ZK Call 3
|
||||
* fully qualified name: `vac:acz:ift:2025q2-ift-zk-calls:ift-zk-call-3`
|
||||
* owner: Marvin
|
||||
* status: not started
|
||||
* status: done
|
||||
* start-date: 2025/05/31
|
||||
* end-date: 2025/06/14
|
||||
|
||||
|
||||
@@ -89,7 +89,7 @@ Delivering the implementation a simple gossipsub PoC over Waku the mixnet.
|
||||
### Updating RFC
|
||||
* fully qualified name: `vac:acz:ift:2025q2-libp2p-mix-testnet:update-rfc`
|
||||
* owner: Akshaya
|
||||
* status: started (20%)
|
||||
* status: done
|
||||
* start-date: 2025/04/1
|
||||
* end-date: 2025/04/21
|
||||
|
||||
@@ -102,12 +102,12 @@ Updating the [mixnet RFC](https://rfc.vac.dev/vac/raw/mix) with latest findings
|
||||
|
||||
#### Deliverables
|
||||
|
||||
* A PR to [vacp2p/rfc-index](https://github.com/vacp2p/rfc-index)
|
||||
* A [PR](https://github.com/vacp2p/rfc-index/pull/158) to [vacp2p/rfc-index](https://github.com/vacp2p/rfc-index)
|
||||
|
||||
### Nomos Comparison
|
||||
* fully qualified name: `vac:acz:ift:2025q2-libp2p-mix-testnet:nomos-comparison`
|
||||
* owner: Akshaya
|
||||
* status: not started
|
||||
* status: done
|
||||
* start-date: 2025/05/19
|
||||
* end-date: 2025/06/02
|
||||
|
||||
@@ -124,7 +124,7 @@ aimed at identifying trade-offs in scalability, privacy, and protocol adaptabili
|
||||
### Implementing SURB
|
||||
* fully qualified name: `vac:acz:ift:2025q2-libp2p-mix-testnet:surb-implementation`
|
||||
* owner: Ben
|
||||
* status: started (0%)
|
||||
* status: started (40%)
|
||||
* start-date: 2025/05/19
|
||||
* end-date: 2025/06/10
|
||||
|
||||
@@ -140,8 +140,8 @@ section 3.4 and 3.5.
|
||||
|
||||
### Solving discrepancies
|
||||
* fully qualified name: `vac:acz:ift:2025q2-libp2p-mix-testnet:solve-discrepancy`
|
||||
* owner: Ben
|
||||
* status: started (10%)
|
||||
* owner: Akshaya
|
||||
* status: started (85%)
|
||||
* start-date: 2025/05/28
|
||||
* end-date: 2025/06/10
|
||||
|
||||
@@ -157,7 +157,7 @@ This task entails solving the discrepancy in mix implementation based on [issue#
|
||||
|
||||
* fully qualified name: `vac:acz:ift:2025q2-libp2p-mix-testnet:consulting-waku-mix`
|
||||
* owner: Akshaya
|
||||
* status: started (20%)
|
||||
* status: done
|
||||
* start-date: 2025/05/1
|
||||
* end-date: 2025/06/30
|
||||
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: RLN Status L2
|
||||
tags:
|
||||
- "2025q1"
|
||||
- "2025q2"
|
||||
- "acz"
|
||||
- "ift"
|
||||
draft: false
|
||||
@@ -48,7 +48,7 @@ We will also strengthen the Premier Research Destination narrative by:
|
||||
|
||||
* fully qualified name: `vac:acz:ift:2025q2-rln-status-l2:maintain`
|
||||
* owner: Ugur
|
||||
* status: started (60%)
|
||||
* status: done
|
||||
* start-date: 2025/04/01
|
||||
* end-date: 2025/06/30
|
||||
|
||||
@@ -62,17 +62,17 @@ with the existing infrastructure.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
* A document to ACZ notion page
|
||||
* [A set of documents](https://www.notion.so/Status-L2-RLN-Deployment-Main-Page-1d08f96fb65c80d58d88e87d88a158b3) to ACZ notion page
|
||||
|
||||
### Prover Service Development
|
||||
|
||||
* fully qualified name: `vac:acz:ift:2025q2-rln-status-l2:prover-service`
|
||||
* owner: Sylvain
|
||||
* status: started (30%)
|
||||
* status: done
|
||||
* start-date: 2025/04/16
|
||||
* end-date: 2025/06/30
|
||||
|
||||
### Description
|
||||
#### Description
|
||||
|
||||
This task involves integrating RLN (Rate-Limiting Nullifier) into the Status L2 architecture,
|
||||
with a focus on the prover component within the Linea network.
|
||||
@@ -87,12 +87,16 @@ Key responsibilities include:
|
||||
|
||||
* A PR to the appropriate repository, including the RLN integration and all related components.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
* A repo that is [vacp2p/status-rln-prover](https://github.com/vacp2p/status-rln-prover)
|
||||
|
||||
### RPC Node Modification
|
||||
|
||||
* fully qualified name: `vac:acz:ift:2025q2-rln-status-l2:rpc-node-modification`
|
||||
|
||||
* owner: Vinh
|
||||
* status: started (20%)
|
||||
* status: done
|
||||
* start-date: 2025/04/16
|
||||
* end-date: 2025/06/30
|
||||
|
||||
@@ -128,7 +132,7 @@ This task focuses on enhancing the interaction between RPC nodes and the Prover
|
||||
|
||||
* fully qualified name: `vac:acz:ift:2025q2-rln-status-l2:rln-spec`
|
||||
* owner: Ugur
|
||||
* status: started (10%)
|
||||
* status: started (70%)
|
||||
* start-date: 2025/05/20
|
||||
* end-date: 2025/06/10
|
||||
|
||||
|
||||
@@ -62,12 +62,14 @@ This task is important to diffuse the cryptographic components' how-know across
|
||||
|
||||
* fully qualified name: `vac:acz:ift:2025q2-think-tank:maintain-2`
|
||||
* owner: Marvin
|
||||
* status: not started
|
||||
* status: cancelled
|
||||
* start-date: 2025/04/14
|
||||
* end-date: 2025/04/26
|
||||
|
||||
#### Description
|
||||
|
||||
This task is cancelled since we update the think tank weekly basis.
|
||||
|
||||
Updating the think-tank Notion page with up-to-date improvements such as cryptographic techniques
|
||||
developed and researched by IFT teams, in particular ACZ, Nescience, Nomos and Codex.
|
||||
This task is important to diffuse the cryptographic components' how-know across the IFT.
|
||||
@@ -80,12 +82,14 @@ This task is important to diffuse the cryptographic components' how-know across
|
||||
|
||||
* fully qualified name: `vac:acz:ift:2025q2-think-tank:wrapping-up`
|
||||
* owner: Marvin
|
||||
* status: not started
|
||||
* status: cancelled
|
||||
* start-date:
|
||||
* end-date:
|
||||
|
||||
#### Description
|
||||
|
||||
This task is cancelled since we update the think tank weekly basis.
|
||||
|
||||
Wrapping up the think-tank Notion page with adjusting structure and identifying the possible missing parts.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
@@ -236,9 +236,9 @@ A [PR](https://github.com/vacp2p/zerokit/pull/311) to `zerokit` and linked to th
|
||||
|
||||
* fully qualified name: `vac:acz:ift:2025q2-zerokit:perfomance-updates-blogpost`
|
||||
* owner: Ben
|
||||
* status: started (0%)
|
||||
* status: started (75%)
|
||||
* start-date: 2025/05/26
|
||||
* end-date: 2025/06/06
|
||||
* end-date: 2025/06/30
|
||||
|
||||
#### Description
|
||||
|
||||
@@ -262,21 +262,21 @@ It should make technical concepts accessible and provide examples or diagrams wh
|
||||
|
||||
* fully qualified name: `vac:acz:ift:2025q2-zerokit:zerokit-maintaining`
|
||||
* owner: Ekaterina
|
||||
* status: started (40%)
|
||||
* status: done
|
||||
* start-date: 2025/04/01
|
||||
* end-date: 2025/05/30
|
||||
* end-date: 2025/06/30
|
||||
|
||||
#### Description
|
||||
This task encompasses all maintenance updates for Zerokit, including CI updates and the creation of future issues.
|
||||
|
||||
#### Deliverables
|
||||
A set of PRs and issues to [vacp2p/zerokit](https://github.com/vacp2p/zerokit/).
|
||||
A set of PRs and issues to [vacp2p/zerokit](https://github.com/vacp2p/zerokit/).
|
||||
|
||||
### Release v0.8.0
|
||||
|
||||
* fully qualified name: `vac:acz:ift:2025q2-zerokit:release`
|
||||
* owner: Ekaterina
|
||||
* status: started (50%)
|
||||
* status: done
|
||||
* start-date: 2025/05/12
|
||||
* end-date: 2025/06/26
|
||||
|
||||
|
||||
@@ -5,6 +5,7 @@ tags:
|
||||
- vac
|
||||
---
|
||||
|
||||
|
||||
## 2025q3 `vac:acz:`
|
||||
---
|
||||
|
||||
@@ -19,7 +20,6 @@ tags:
|
||||
### `nes`
|
||||
* [ ] [[acz/nes/2025q3-nescience-consulting|2025q3-nescience-consulting]]
|
||||
|
||||
|
||||
---
|
||||
## 2025q2 `vac:acz:`
|
||||
* [ ] [[acz/ift/2025q2-zerokit|2025q2-zerokit]]
|
||||
|
||||
@@ -55,7 +55,7 @@ which topics we include or exclude.
|
||||
### SE/DE improvements
|
||||
* fully qualified name: `vac:acz:nes:2025q2-nescience-consulting:SE-DE-improvements`
|
||||
* owner: Marvin
|
||||
* status: started (30%)
|
||||
* status: done
|
||||
* start-date: 2024/05/21
|
||||
* end-date: 2025/06/04
|
||||
|
||||
@@ -67,6 +67,29 @@ In Q1, shielded executions were a primary focus. In this task, we focus on impro
|
||||
|
||||
This directly corresponds to Nescience's [Q2-R2](https://www.notion.so/R2-Updating-public-state-with-private-execution-SE-DE-improvements-1bf8f96fb65c81a98548fff27c4d1dcc) task.
|
||||
|
||||
### Deliverables
|
||||
* RFC style documents for SE/DE
|
||||
|
||||
### Light user support in NSSA
|
||||
* fully qualified name: `vac:acz:nes:2025q2-nescience-consulting:light-users`
|
||||
* owner: Marvin
|
||||
* status: started (70%)
|
||||
* start-date: 2024/06/03
|
||||
* end-date: 2025/06/11
|
||||
|
||||
### Description
|
||||
Light user support is essential for NSSA adoption.
|
||||
This ensures a wide range of users can participate within NSSA.
|
||||
It is necessary to ensure that light users can enjoy the same level of NSSA privacy guarantees as any other users.
|
||||
To this end, we will examine privacy transactions (private, SE, DE) for light users. Specific analysis should include:
|
||||
|
||||
- Investigate how other projects handle light user proof generation.
|
||||
- Potential privacy risks relying on a third party to run zkVM.
|
||||
- Investigate whether light users can practically compute portions of the proof locally to strengthen privacy.
|
||||
- Design protocol or mitigations (of current circuits) for outsourcing zkVM execution.
|
||||
|
||||
Ties directly with NSSA’s task [Q2/R4](https://www.notion.so/R4-Lightweight-user-execution-model-1bf8f96fb65c81dc9471c6a03d2c8513?pvs=21).
|
||||
|
||||
### Deliverables
|
||||
* RFC style documents for SE/DE
|
||||
* Document covering private, SE, DE transactions performed by light users
|
||||
with analysis on any privacy or security compromises.
|
||||
@@ -37,14 +37,28 @@ and introduced into the ecosystem.
|
||||
### Zk Consulting Nomos 1
|
||||
* fully qualified name: `vac:acz:nomos:2025q2-nomos-consulting:zk-consulting-nomos-1`
|
||||
* owner: Marvin
|
||||
* status: started (80%)
|
||||
* start-date: 2024/04/20
|
||||
* status: done
|
||||
* start-date: 2025/04/20
|
||||
* end-date: 2025/05/17
|
||||
|
||||
### Description
|
||||
Provide feedback Nomos' document analysis of failures in mix networks Design considerations page.
|
||||
|
||||
|
||||
### Deliverables
|
||||
- Provide comments for Nomos team to address in the document (and corresponding overleaf).
|
||||
- Add proofs to these documents as needed.
|
||||
|
||||
### Zk Consulting Nomos 2
|
||||
* fully qualified name: `vac:acz:nomos:2025q2-nomos-consulting:zk-consulting-nomos-2`
|
||||
* owner: Marvin
|
||||
* status: started (20%)
|
||||
* start-date: 2025/06/04
|
||||
* end-date: 2025/06/18
|
||||
|
||||
### Description
|
||||
Provide feedback Nomos’ document [Preliminary Research: Impact of the Service Declaration Protocol on the statistical inference of relative stake](https://www.notion.so/nomos-tech/Preliminary-Research-Impact-of-the-Service-Declaration-Protocol-on-the-statistical-inference-of-rel-206261aa09df807bad8afccf8474c6c9#209261aa09df803d9e07f14c76435c45) page.
|
||||
|
||||
### Deliverables
|
||||
- Provide comments for Nomos team to address in the document (and corresponding overleaf).
|
||||
- Add proofs to these documents as needed.
|
||||
69
content/acz/preview.md
Normal file
69
content/acz/preview.md
Normal file
@@ -0,0 +1,69 @@
|
||||
---
|
||||
title: ACZ Roadmap Preview
|
||||
tags:
|
||||
- acz
|
||||
- vac
|
||||
---
|
||||
|
||||
## Roadmap Preview
|
||||
|
||||
### 2025Q3
|
||||
|
||||
- Zerokit
|
||||
- Releasing Zerokit v0.9.0 (maintaining and fixing small updates)
|
||||
- de-MLS
|
||||
- multi steward implementation
|
||||
- Refinement and maintain de-MLS RFC
|
||||
- EF grant application
|
||||
- libp2p-mix
|
||||
- Publishing a blospot
|
||||
- SURB implementation
|
||||
- EF grant application
|
||||
- Initial incentivasation research
|
||||
- RLN Status L2
|
||||
- Testing RLN deployment
|
||||
- Research on better decentralized architecture
|
||||
- Discovery
|
||||
- Conducting initial research
|
||||
- IFT ZK Calls
|
||||
- Conducting monthly IFT ZK Calls
|
||||
|
||||
|
||||
### 2025Q4
|
||||
|
||||
- Zerokit
|
||||
- Releasing Zerokit v1.0
|
||||
- de-MLS
|
||||
- Integration Ethereum Authentication
|
||||
- Maintain de-MLS RFC
|
||||
- Ready for Waku interagtion with multi-steward
|
||||
- libp2p-mix
|
||||
- Releasing product ready core implementation,
|
||||
which is Sphinx package transmission including SURB.
|
||||
- RLN Status L2
|
||||
- Public testnet integration
|
||||
|
||||
### 2026Q1 and beyond
|
||||
|
||||
- Zerokit
|
||||
- Releasing Zerokit v1.1
|
||||
- de-MLS
|
||||
- Public testnet
|
||||
- Ready for Waku production
|
||||
- RLN Status L2
|
||||
- Design V1 for fully decentralized architecture
|
||||
|
||||
|
||||
### Uncategorized
|
||||
The following items are not part of our current roadmap.
|
||||
|
||||
- de-MLS
|
||||
- Applyting EF grant
|
||||
- RLNV3
|
||||
- RLNv3 RFC creation
|
||||
- Zerokit
|
||||
RLNv3 integration
|
||||
- libp2p-mix
|
||||
- Incentivation research in details
|
||||
|
||||
|
||||
@@ -76,7 +76,7 @@ If possible, adapt this to be able to run it from inside and outside the cluster
|
||||
|
||||
* fully qualified name: `vac:dst:ift:2025q2-dst-tooling:analysis-refactor`
|
||||
* owner: Alberto
|
||||
* status: 60%
|
||||
* status: 100%
|
||||
* start-date: 2025/05/20
|
||||
* end-date: 2025/06/06
|
||||
|
||||
@@ -91,7 +91,7 @@ Also provide examples of usage, and documentation.
|
||||
|
||||
#### Deliverables
|
||||
- PRs:
|
||||
- [Github: Draft PR](https://github.com/vacp2p/10ksim/pull/66)
|
||||
- [Github: PR](https://github.com/vacp2p/10ksim/pull/66)
|
||||
- Related Documents:
|
||||
|
||||
|
||||
@@ -99,16 +99,18 @@ Also provide examples of usage, and documentation.
|
||||
|
||||
* fully qualified name: `vac:dst:ift:2025q2-dst-tooling:adapt-experiments`
|
||||
* owner: Pearson
|
||||
* status: 0%
|
||||
* status: 100%
|
||||
* start-date: 2025/06/02
|
||||
* end-date: 2025/06/20
|
||||
|
||||
#### Description
|
||||
Adapt previous experiments that were realized by DST with the deployment
|
||||
system created in `vac:dst:ift:2025q2-dst-tooling:python-deployment-scaffold`.
|
||||
I necessary, realize changes to the code structure to allow better integration
|
||||
If necessary, realize changes to the code structure to allow better integration
|
||||
ot the aforementioned experiments, while maintaining adaptability for new ones.
|
||||
|
||||
#### Deliverables
|
||||
- PRs:
|
||||
- [Github: PR](https://github.com/vacp2p/10ksim/pull/70)
|
||||
- [Github: PR](https://github.com/vacp2p/10ksim/pull/72)
|
||||
- Related Documents:
|
||||
|
||||
75
content/dst/ift/2025q3-dst-research-destination.md
Normal file
75
content/dst/ift/2025q3-dst-research-destination.md
Normal file
@@ -0,0 +1,75 @@
|
||||
---
|
||||
title: DST Research destination
|
||||
tags:
|
||||
- "2025q3"
|
||||
- "dst"
|
||||
- "ift"
|
||||
draft: false
|
||||
description: "Forum posts and public reports sharing DST results and insights,
|
||||
aimed at informing the public and engaging the community."
|
||||
---
|
||||
|
||||
`vac:dst:ift:2025q3-dst-research-destination`
|
||||
|
||||
|
||||
## Description
|
||||
Create and share forum posts and public reports
|
||||
that present DST results and insights in a clear and engaging way.
|
||||
The goal is to break down complex findings
|
||||
so they’re accessible to the broader community,
|
||||
sparking discussions, feedback, and new ideas.
|
||||
Focus on making the content informative,
|
||||
easy to understand, and inviting for people to participate.
|
||||
|
||||
### Background
|
||||
When people understand the outcomes and insights,
|
||||
they’re more likely to engage, contribute, and collaborate.
|
||||
By putting these results out there through forums and public reports,
|
||||
we open doors for more feedback, ideas, and maybe even unexpected collaborations.
|
||||
It also helps keep the community informed about what’s happening,
|
||||
making them feel like they're part of the process
|
||||
rather than on the outside looking in.
|
||||
|
||||
### Narratives
|
||||
We will support Conduit of Expertise by making the reports
|
||||
and forum posts help establish an RFC culture
|
||||
where the community can see, understand, and even help improve the work.
|
||||
We will support Premier Research of Destination
|
||||
by making sure we’re open, accessible, and continuously learning from each other.
|
||||
|
||||
### Additional info
|
||||
|
||||
## Task List
|
||||
|
||||
### Ethereum foundation protocol test
|
||||
|
||||
* fully qualified name: `vac:dst:ift:2025q3-dst-research-destination:ethereum-foundation`
|
||||
* owner: Alberto
|
||||
* status: recurring
|
||||
* start-date: 2025-07-01
|
||||
* end-date: 2025-09-30
|
||||
|
||||
#### Description
|
||||
|
||||
Ethereum foundation is looking for a [Protocol Tester](https://jobs.lever.co/ethereumfoundation/c9ef74e7-1fb7-4a8e-88cc-11aa178d49e2).
|
||||
This can be an opportunity to get in contact with EF,
|
||||
through the [Project Grants](https://esp.ethereum.foundation/applicants/project-grants).
|
||||
|
||||
#### Deliverables
|
||||
|
||||
|
||||
### Forum posts (recurring)
|
||||
|
||||
* fully qualified name: `vac:dst:ift:2025q3-dst-research-destination:forum-post`
|
||||
* owner: Alberto
|
||||
* status: recurring
|
||||
* start-date: 2025-07-01
|
||||
* end-date: 2025-09-30
|
||||
|
||||
### Public reports (recurring)
|
||||
|
||||
* fully qualified name: `vac:dst:ift:2025q3-dst-research-destination:public-reports`
|
||||
* owner: Alberto
|
||||
* status: recurring
|
||||
* start-date: 2025-07-01
|
||||
* end-date: 2025-09-30
|
||||
115
content/dst/ift/2025q3-dst-tooling.md
Normal file
115
content/dst/ift/2025q3-dst-tooling.md
Normal file
@@ -0,0 +1,115 @@
|
||||
---
|
||||
title: DST Tooling
|
||||
tags:
|
||||
- "2025q3"
|
||||
- "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:2025q3-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.
|
||||
|
||||
|
||||
### Background
|
||||
|
||||
### Narratives
|
||||
|
||||
These efforts will support the Conduit of Expertise narrative by
|
||||
accelerating DST/IFT Improvements,
|
||||
providing measurable insights
|
||||
to enhance developer experience
|
||||
within and beyond the IFT ecosystem.
|
||||
Also, ideally these tools can be shared across projects,
|
||||
reinforcing cross project collaboration.
|
||||
|
||||
|
||||
## Task list
|
||||
|
||||
### Improve tooling
|
||||
|
||||
* fully qualified name: `vac:dst:ift:2025q3-dst-tooling:improve tooling`
|
||||
* owner: Pearson
|
||||
* status: 0%
|
||||
* start-date: 2025/07/01
|
||||
* end-date: 2025/07/04
|
||||
|
||||
#### Description
|
||||
Move values.yamls to same place under experiments (instead of spread throughout node/publisher/etc.)
|
||||
Ensure fixes made during regression testing are merged in.
|
||||
Add get-filter-messages and get-store-messages images.
|
||||
Create, organize and prioritize nice-to-haves in the codebase.
|
||||
|
||||
#### Deliverables
|
||||
- PRs:
|
||||
- Related Documents:
|
||||
|
||||
|
||||
### Adversarial scenarios
|
||||
|
||||
* fully qualified name: `vac:dst:ift:2025q3-dst-tooling:status-waku-log-parser`
|
||||
* owner: Alberto
|
||||
* status: 0%
|
||||
* start-date: -
|
||||
* end-date: -
|
||||
|
||||
#### Description
|
||||
The goal of this task is to extend the DST log parser tool to
|
||||
assist developers in debugging and analyzing message histories and activity
|
||||
within the Waku and Status ecosystems. The tool should consolidate and
|
||||
process data from diverse log sources, including Status app logs,
|
||||
nWaku application logs, nWaku fleet logs (via Kibana API), and
|
||||
Status mobile logs.
|
||||
The tool’s primary focus is to support developers by retrieving the
|
||||
complete lifecycle and related histories for given Waku message IDs or
|
||||
Status envelope IDs. This will empower developers to better understand
|
||||
network events, troubleshoot issues, and optimize usage scenarios within
|
||||
libp2p, Gossipsub, MVDS, and SDS protocols.
|
||||
|
||||
#### Deliverables
|
||||
- PRs:
|
||||
- Related Documents:
|
||||
|
||||
|
||||
### Adversarial scenarios
|
||||
|
||||
* fully qualified name: `vac:dst:ift:2025q3-dst-tooling:scenario-workflow-manager`
|
||||
* owner: Alberto
|
||||
* status: 0%
|
||||
* start-date: -
|
||||
* end-date: -
|
||||
|
||||
#### Description
|
||||
The objective of this task is to create a workflow management tool to design,
|
||||
execute, and evaluate specialized network scenarios tailored to the analysis of
|
||||
libp2p and Gossipsub protocols. The tool will enable developers and researchers
|
||||
to simulate and study adversarial conditions and control message patterns in a
|
||||
controlled and reproducible manner.
|
||||
The scenarios will provide insights into network behavior under various conditions,
|
||||
facilitating performance optimizations, behavioral analysis, and the exploration of
|
||||
message interactions in distributed environments. This tool aims to
|
||||
improve understanding of protocols like Gossipsub and libp2p, both in regular
|
||||
workflows and edge-case scenarios.
|
||||
|
||||
#### Deliverables
|
||||
- PRs:
|
||||
- Related Documents:
|
||||
@@ -1,15 +1,15 @@
|
||||
---
|
||||
title: Scaling think tank
|
||||
tags:
|
||||
- "2025qx"
|
||||
- "2025q3"
|
||||
- "dst"
|
||||
- "ift"
|
||||
draft: true
|
||||
draft: false
|
||||
description: "List and explain the scaling ideas
|
||||
that IFT project are using in their projects."
|
||||
---
|
||||
|
||||
`vac:dst:ift:2025qx-scaling-think-tank`
|
||||
`vac:dst:ift:2025q3-scaling-think-tank`
|
||||
|
||||
## Description
|
||||
List, analyze and explain how IFT teams
|
||||
@@ -28,7 +28,7 @@ scaling ideas, and other insights.
|
||||
### Scaling analysis
|
||||
|
||||
* fully qualified name: `vac:dst:vac:2025qx-scaling-think-tank:scaling-analysis`
|
||||
* owner: N/A
|
||||
* owner: Pearson
|
||||
* status: N/A
|
||||
* start-date: N/A
|
||||
* end-date: N/A
|
||||
@@ -5,74 +5,109 @@ tags:
|
||||
- vac
|
||||
---
|
||||
|
||||
## 2025q2 `vac:dst:`
|
||||
|
||||
## `vac:dst:`
|
||||
|
||||
---
|
||||
|
||||
The DST Service unit is responsible of the execution of large-scale
|
||||
experiments focused on performance evaluation and scalability analysis.
|
||||
Additionally, it offers a range of tools to IFT projects for benchmarking
|
||||
both new functionalities and modifications to existing ones.
|
||||
These tools enable precise evaluation of changes, ensuring that updates
|
||||
are not only effective but also maintain or improve system performance and scalability.
|
||||
|
||||
|
||||
[[preview|Roadmap Preview]]
|
||||
|
||||
## 2025q3 `vac:dst:`
|
||||
---
|
||||
|
||||
### `ift`
|
||||
* [ ] [[dst/ift/2025q2-dst-tooling|dst-tooling]]
|
||||
* [ ] [[dst/ift/2025q2-dst-conduit|dst-conduit]]
|
||||
* [ ] [[dst/ift/2025q2-dst-research-destination|dst-research-destination]]
|
||||
* [ ] [[dst/ift/2025q2-vaclab|vaclab]]
|
||||
<!--
|
||||
* [ ] [[dst/ift/2025qx-scaling-think-tank|scaling-think-tank]]
|
||||
-->
|
||||
* [ ] [[dst/ift/2025q3-dst-tooling|dst-tooling]]
|
||||
* [ ] [[dst/ift/2025q3-dst-research-destination|dst-research-destination]]
|
||||
* [ ] [[dst/ift/2025q3-scaling-think-tank|scaling-think-tank]]
|
||||
|
||||
### `nomos`
|
||||
* [ ] [[dst/nomos/2025q2-nomos-scaling|nomos-scaling]]
|
||||
* [ ] [[dst/nomos/2025q3-nomos-scaling|nomos-scaling]]
|
||||
|
||||
### `status`
|
||||
* [ ] [[dst/status/2025q2-status-go-chat-protocol-benchmarks|status-go-chat-protocol-benchmarks]]
|
||||
* [ ] [[dst/status/2025q2-status-go-evaluation|status-go-evaluation]]
|
||||
|
||||
### `vac`
|
||||
* [ ] [[dst/vac/2025q2-libp2p-evaluation|libp2p-evaluation]]
|
||||
* [ ] [[dst/vac/2025q3-libp2p-evaluation|libp2p-evaluation]]
|
||||
|
||||
### `waku`
|
||||
* [ ] [[dst/waku/2025q2-waku-evaluation|waku-evaluation]]
|
||||
* [ ] [[dst/waku/2025q2-waku-scaling|waku-scaling]]
|
||||
* [ ] [[dst/waku/2025q2-waku-tooling|waku-tooling]]
|
||||
* [ ] [[dst/waku/2025q3-waku-evaluation|waku-evaluation]]
|
||||
* [ ] [[dst/waku/2025q3-waku-scaling|waku-scaling]]
|
||||
* [ ] [[dst/waku/2025q3-waku-theoretical-analysis|walu-theoretical-analysis]]
|
||||
|
||||
---
|
||||
## 2025q2 `vac:dst:`
|
||||
---
|
||||
|
||||
### `ift`
|
||||
* [[dst/ift/2025q2-dst-tooling|dst-tooling]]
|
||||
* [[dst/ift/2025q2-dst-conduit|dst-conduit]]
|
||||
* [[dst/ift/2025q2-dst-research-destination|dst-research-destination]]
|
||||
* [[dst/ift/2025q2-vaclab|vaclab]]
|
||||
|
||||
### `nomos`
|
||||
* [[dst/nomos/2025q2-nomos-scaling|nomos-scaling]]
|
||||
|
||||
### `status`
|
||||
* [[dst/status/2025q2-status-go-chat-protocol-benchmarks|status-go-chat-protocol-benchmarks]]
|
||||
* [[dst/status/2025q2-status-go-evaluation|status-go-evaluation]]
|
||||
|
||||
### `vac`
|
||||
* [[dst/vac/2025q2-libp2p-evaluation|libp2p-evaluation]]
|
||||
|
||||
### `waku`
|
||||
* [[dst/waku/2025q2-waku-evaluation|waku-evaluation]]
|
||||
* [[dst/waku/2025q2-waku-scaling|waku-scaling]]
|
||||
* [[dst/waku/2025q2-waku-tooling|waku-tooling]]
|
||||
|
||||
---
|
||||
## 2025q1 `vac:dst:`
|
||||
---
|
||||
### `codex`
|
||||
* [ ] [[dst/codex/2025q1-codex-base-capacity|codex-base-capacity]]
|
||||
* [ ] [[dst/codex/2025q1-codex-comparison|codex-comparison]]
|
||||
* [[dst/codex/2025q1-codex-base-capacity|codex-base-capacity]]
|
||||
* [[dst/codex/2025q1-codex-comparison|codex-comparison]]
|
||||
|
||||
### `ift`
|
||||
* [ ] [[dst/ift/2025q1-dst-conduit|dst-conduit]]
|
||||
* [ ] [[dst/ift/2025q1-dst-research-destination|dst-research-destination]]
|
||||
* [ ] [[dst/ift/2025q1-vaclab|vaclab]]
|
||||
* [[dst/ift/2025q1-dst-conduit|dst-conduit]]
|
||||
* [[dst/ift/2025q1-dst-research-destination|dst-research-destination]]
|
||||
* [[dst/ift/2025q1-vaclab|vaclab]]
|
||||
|
||||
### `nomos`
|
||||
* [ ] [[dst/nomos/2025q1-nomos-scaling|nomos-scaling]]
|
||||
* [[dst/nomos/2025q1-nomos-scaling|nomos-scaling]]
|
||||
|
||||
### `status`
|
||||
* [ ] [[dst/status/2025q1-status-go-evaluation|status-go-evaluation]]
|
||||
* [[dst/status/2025q1-status-go-evaluation|status-go-evaluation]]
|
||||
|
||||
### `vac`
|
||||
* [ ] [[dst/vac/2025q1-libp2p-evaluation|libp2p-evaluation]]
|
||||
* [[dst/vac/2025q1-libp2p-evaluation|libp2p-evaluation]]
|
||||
|
||||
### `waku`
|
||||
* [ ] [[dst/waku/2025q1-waku-evaluation|waku-evaluation]]
|
||||
* [ ] [[dst/waku/2025q1-waku-scaling|waku-scaling]]
|
||||
* [ ] [[dst/waku/2025q1-waku-tooling|waku-tooling]]
|
||||
* [[dst/waku/2025q1-waku-evaluation|waku-evaluation]]
|
||||
* [[dst/waku/2025q1-waku-scaling|waku-scaling]]
|
||||
* [[dst/waku/2025q1-waku-tooling|waku-tooling]]
|
||||
|
||||
---
|
||||
## 2024q4 `vac:dst:`
|
||||
---
|
||||
### `codex`
|
||||
* [ ] [[dst/codex/2024q4-codex-base-capacity|codex-base-capacity]]
|
||||
* [ ] [[dst/codex/2024q4-codex-comparison|codex-comparison]]
|
||||
* [[dst/codex/2024q4-codex-base-capacity|codex-base-capacity]]
|
||||
* [[dst/codex/2024q4-codex-comparison|codex-comparison]]
|
||||
|
||||
### `ift`
|
||||
* [ ] [[dst/ift/2024q4-dst-conduit|dst-conduit]]
|
||||
* [ ] [[dst/ift/2024q4-dst-research-destination|dst-research-destination]]
|
||||
* [ ] [[dst/ift/2024q4-vaclab|vaclab]]
|
||||
* [ ] [[dst/ift/2024q4-visualiser-tool|visualiser-tool]]
|
||||
* [[dst/ift/2024q4-dst-conduit|dst-conduit]]
|
||||
* [[dst/ift/2024q4-dst-research-destination|dst-research-destination]]
|
||||
* [[dst/ift/2024q4-vaclab|vaclab]]
|
||||
* [[dst/ift/2024q4-visualiser-tool|visualiser-tool]]
|
||||
|
||||
### `vac`
|
||||
* [ ] [[dst/vac/2024q4-libp2p-evaluation|libp2p-evaluation]]
|
||||
* [[dst/vac/2024q4-libp2p-evaluation|libp2p-evaluation]]
|
||||
|
||||
### `waku`
|
||||
* [ ] [[dst/waku/2024q4-waku-evaluation|waku-evaluation]]
|
||||
* [ ] [[dst/waku/2024q4-waku-scaling|waku-scaling]]
|
||||
* [[dst/waku/2024q4-waku-evaluation|waku-evaluation]]
|
||||
* [[dst/waku/2024q4-waku-scaling|waku-scaling]]
|
||||
93
content/dst/nomos/2025q3-nomos-scaling.md
Normal file
93
content/dst/nomos/2025q3-nomos-scaling.md
Normal file
@@ -0,0 +1,93 @@
|
||||
---
|
||||
title: Nomos Scaling
|
||||
tags:
|
||||
- "2025q3"
|
||||
- "dst"
|
||||
- "nomos"
|
||||
draft: false
|
||||
description: "Help Nomos understand and improve
|
||||
the properties of Nomos.
|
||||
Improve privacy and security,
|
||||
and improve scaling properties."
|
||||
---
|
||||
|
||||
`vac:dst:nomos:2025q3-nomos-scaling`
|
||||
|
||||
|
||||
## 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.
|
||||
|
||||
### Background
|
||||
|
||||
### Narratives
|
||||
|
||||
We will support the Conduit of Expertise narrative directly
|
||||
by providing valuable insights to Nomos
|
||||
and the ability to theorise, reason about,
|
||||
test, measure and improve
|
||||
the performance, stability and scalability of Nomos.
|
||||
|
||||
These efforts will contribute in these ways to the Conduit of Expertise narrative:
|
||||
|
||||
* Help Nomos ship a more scalable mixnet,
|
||||
unlocking capabilities across IFT's teams and ecosystem
|
||||
and allowing for more use cases to be supported and understood.
|
||||
This will also help spur on outside adoption and contributions.
|
||||
* Improve the RFC culture
|
||||
by allowing for faster and easier development of RFCs
|
||||
with the aid of rapidly accelerated insights into how an RFC in development will perform as it's being expanded and going through the draft process.
|
||||
* Allow easier post-mortem analysis of the success or relative performance of a given RFC
|
||||
|
||||
### Additional info
|
||||
|
||||
## Task List
|
||||
|
||||
### Nomos deployment test
|
||||
|
||||
* fully qualified name: `vac:dst:nomos:2025q3-nomos-scaling:nomos-deployment-test`
|
||||
* owner: Alberto
|
||||
* status: 0%
|
||||
* start-date: <yyyy/mm/dd>
|
||||
* end-date: <yyyy/mm/dd>
|
||||
|
||||
#### Description
|
||||
|
||||
Utilize the current state of Nomos** in the DST experiments workflow to gather
|
||||
early feedback and identify any missing functionalities required for effective experimentation.
|
||||
This process will ensure Nomos meets the specific needs of the DST team and vice-versa,
|
||||
and is well-prepared to support advanced experiments like Blendnet.
|
||||
|
||||
|
||||
#### Deliverables
|
||||
* PRs:
|
||||
* Report published with all relevant details
|
||||
|
||||
|
||||
### Blend benchmarking
|
||||
|
||||
* fully qualified name: `vac:dst:nomos:2025q3-nomos-scaling:nomos-benchmarking`
|
||||
* owner: Alberto
|
||||
* status: 0%
|
||||
* start-date: <yyyy/mm/dd>
|
||||
* end-date: <yyyy/mm/dd>
|
||||
|
||||
#### Description
|
||||
|
||||
Measure the speed and reliability of Nomos's blendnet.
|
||||
|
||||
#### Deliverables
|
||||
* Benchmarks done
|
||||
* Report published with all relevant details
|
||||
52
content/dst/preview.md
Normal file
52
content/dst/preview.md
Normal file
@@ -0,0 +1,52 @@
|
||||
---
|
||||
title: DST Roadmap Preview
|
||||
tags:
|
||||
- dst
|
||||
- vac
|
||||
---
|
||||
|
||||
## Roadmap Preview
|
||||
|
||||
### 2025Q4
|
||||
|
||||
- Waku
|
||||
- Keep assisting waku team with regression analysis on each new version
|
||||
- Perform theoretical and statistical models
|
||||
- Analyze scaling behavior
|
||||
|
||||
- Nomos
|
||||
- Start assisting nomos 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
|
||||
|
||||
- VAC
|
||||
- Build a simulation tool to test scalability and resilience by intentionally injecting adversarial behaviors (e.g., spam, Sybil attacks, network partitions) in projects like nimlibp2p, Waku and Nomos.
|
||||
- Keep supporting FURPS by doing necessary experiments to projects.
|
||||
|
||||
### 2026Q1 and beyond
|
||||
- Waku
|
||||
- Keep assisting waku team with regression analysis on each new version
|
||||
- Perform theoretical and statistical models
|
||||
- Analyze scaling behavior
|
||||
|
||||
- Nomos
|
||||
- Keep assisting nomos 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
|
||||
|
||||
- VAC
|
||||
- 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.
|
||||
@@ -70,5 +70,17 @@ with past ones. Make sure regressions are not happening,
|
||||
or any other functionality specific request that can come from the status team.
|
||||
|
||||
#### Deliverables
|
||||
* [ ] Reports:
|
||||
* [ ] Related PRs if apply:
|
||||
* Reports:
|
||||
* Related PRs if apply:
|
||||
- [Merged PR #1: Base-manifests](https://github.com/vacp2p/status-benchmarks/pull/1)
|
||||
- [To review PR #2: Controlbox](https://github.com/vacp2p/status-benchmarks/pull/2)
|
||||
- [To review PR #3: Status-Subscriber](https://github.com/vacp2p/status-benchmarks/pull/3)
|
||||
- [To review PR #4: Status-Init](https://github.com/vacp2p/status-benchmarks/pull/4)
|
||||
- [To review PR #5: Deployment Files](https://github.com/vacp2p/status-benchmarks/pull/5)
|
||||
- [To review PR #6: Logger](https://github.com/vacp2p/status-benchmarks/pull/6)
|
||||
- [To review PR #7: K8s Utils](https://github.com/vacp2p/status-benchmarks/pull/7)
|
||||
- [To review PR #8: RPC & Signal clients](https://github.com/vacp2p/status-benchmarks/pull/8)
|
||||
- [To review PR #9: Services](https://github.com/vacp2p/status-benchmarks/pull/9)
|
||||
- [To review PR #10: StatusBackend](https://github.com/vacp2p/status-benchmarks/pull/10)
|
||||
- [To review PR #11: Message Injection](https://github.com/vacp2p/status-benchmarks/pull/11)
|
||||
- [To review PR #12: Setup StatusBackend functions](https://github.com/vacp2p/status-benchmarks/pull/12)
|
||||
|
||||
@@ -78,6 +78,7 @@ and ensure they don't happen again.
|
||||
* Analysis done
|
||||
* [Notion: Quic Issues](https://www.notion.so/List-of-Issues-1ca8f96fb65c801b9c9ad4cceb16fa72)
|
||||
* [Notion: Nim-libp2p 1.10.0](https://www.notion.so/Nim-libp2p-v1-10-0-regression-testing-May-2025-1f28f96fb65c80d58334f0c1a98ba23b)
|
||||
* [Notion: Nim-libp2p 1.11.0](https://www.notion.so/Nim-libp2p-v1-11-0-regression-testing-June-2025-2118f96fb65c802ca1b7c4233271ca26)
|
||||
* Report published with all relevant details
|
||||
* RFC's GitHub issue updated
|
||||
with links to the analysis and results.
|
||||
@@ -107,7 +108,7 @@ compare same scenario with and without using mix.
|
||||
|
||||
* fully qualified name: `vac:dst:vac:2025q2-libp2p-evaluation:mix-gossipsub`
|
||||
* owner: Alberto
|
||||
* status: 0%
|
||||
* status: 100%
|
||||
* start-date: 2025-06-02
|
||||
* end-date: 2025-06-13
|
||||
|
||||
@@ -122,12 +123,15 @@ as it should.
|
||||
|
||||
#### Deliverables
|
||||
* Analysis done:
|
||||
* [Notion: Mix report extended](https://www.notion.so/Nim-libp2p-Mix-May-2025-1f38f96fb65c800a8466f68472e799db?source=copy_link#2188f96fb65c8096a18ceba3d1c3fea8)
|
||||
* PRs:
|
||||
* [Github analysis PR](https://github.com/vacp2p/10ksim/pull/71)
|
||||
|
||||
### IDontWant statistical analysis
|
||||
|
||||
* fully qualified name: `vac:dst:vac:2025q2-libp2p-evaluation:idontwant-statistical-analysis`
|
||||
* owner: Pearson
|
||||
* status: 0%
|
||||
* status: 90%
|
||||
* start-date: 2025-06-09
|
||||
* end-date: 2025-06-20
|
||||
|
||||
@@ -153,5 +157,7 @@ late arrivals and better handle them in the network.
|
||||
|
||||
#### Deliverables
|
||||
* PRs:
|
||||
* [Github: Refactor PR](https://github.com/vacp2p/research/pull/204)
|
||||
* [Github: Add case PR](https://github.com/vacp2p/research/pull/205)
|
||||
* Documents:
|
||||
|
||||
|
||||
98
content/dst/vac/2025q3-libp2p-evaluation.md
Normal file
98
content/dst/vac/2025q3-libp2p-evaluation.md
Normal file
@@ -0,0 +1,98 @@
|
||||
---
|
||||
title: Libp2p Evaluation
|
||||
tags:
|
||||
- "2025q3"
|
||||
- "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:2025q3-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.
|
||||
|
||||
### Background
|
||||
|
||||
We want to learn specific, actionable information
|
||||
about libp2p'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 simulation
|
||||
to determine and measure the success,
|
||||
side effects and other factors of libp2p and its evolution.
|
||||
|
||||
### Narrative
|
||||
|
||||
We will support the Conduit of Expertise narrative directly
|
||||
by analysing and evaluating new libp2p releases and their features,
|
||||
both with regards to features they have today
|
||||
and with regards to how that compares to past behaviour.
|
||||
|
||||
Additionally, these efforts will contribute
|
||||
to the Premier Research destination narrative by
|
||||
improving and strengthening our relationship with the libp2p team
|
||||
and thus increasing the reach and influence of the IFT,
|
||||
and improving the chances
|
||||
that we successfully grow our ecosystem's products and collaborations
|
||||
and especially those we want to work with externally.
|
||||
|
||||
### Additional info
|
||||
|
||||
## Task list
|
||||
|
||||
### Regression testing (recurring)
|
||||
|
||||
* fully qualified name: `vac:dst:vac:2025q3-libp2p-evaluation:regression-testing`
|
||||
* owner: Alberto
|
||||
* status: recurring
|
||||
* start-date: 2025-07-01
|
||||
* end-date: 2025-09-30
|
||||
|
||||
#### 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 done
|
||||
* Report published with all relevant details
|
||||
* RFC's GitHub issue updated
|
||||
with links to the analysis and results.
|
||||
|
||||
|
||||
### Universal connectivity
|
||||
|
||||
* fully qualified name: `vac:dst:vac:2025q3-libp2p-evaluation:universal-connectivity`
|
||||
* owner: Alberto
|
||||
* status: -
|
||||
* start-date: -
|
||||
* end-date: -
|
||||
|
||||
#### Description
|
||||
Help p2p team running scenarios with universal connectivity app
|
||||
and checking functionality with other libp2p implementations.
|
||||
|
||||
#### Deliverables
|
||||
* PRs:
|
||||
* Report:
|
||||
@@ -84,7 +84,7 @@ and report findings.
|
||||
### Regression testing (recurring)
|
||||
|
||||
* fully qualified name: `vac:dst:waku:2025q2-waku-evaluation:regression-testing`
|
||||
* owner: Alberto
|
||||
* owner: Pearson
|
||||
* status: recurring
|
||||
* start-date: 2025-04-01
|
||||
* end-date: 2025-06-30
|
||||
@@ -100,4 +100,7 @@ and ensure they don't happen again.
|
||||
|
||||
#### Deliverables
|
||||
- Reports:
|
||||
- [Notion: nWaku v0.36](https://www.notion.so/Waku-regression-testing-v0-36-21c8f96fb65c804dab04d676c2a6121e)
|
||||
- [Notion: nWaku v0.36 notes](https://www.notion.so/Experiments-for-nWaku-v36-0-21e8f96fb65c801e9ffcd25cf0d88370)
|
||||
- Related PRs if apply:
|
||||
- [Github Commit: Cript to generate input for log scraping](https://github.com/vacp2p/10ksim/commit/5ae2a3ca6faf2b6c8d0cb750c37c7c2afaa23e66)
|
||||
113
content/dst/waku/2025q3-waku-evaluation.md
Normal file
113
content/dst/waku/2025q3-waku-evaluation.md
Normal file
@@ -0,0 +1,113 @@
|
||||
---
|
||||
title: Waku Evaluation
|
||||
tags:
|
||||
- "2025q3"
|
||||
- "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:2025q3-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.
|
||||
|
||||
### Background
|
||||
|
||||
We want to learn specific, actionable information
|
||||
about Waku'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 simulation
|
||||
to determine and measure the success,
|
||||
side effects and other factors of Waku and its evolution.
|
||||
|
||||
### Narratives
|
||||
We will support the Conduit of Expertise narrative directly
|
||||
by analysing and evaluating new Waku releases and their features,
|
||||
both with regards to features they have today
|
||||
and with regards to how that compares to past behaviour.
|
||||
|
||||
We will:
|
||||
|
||||
* Enable improvements to Waku
|
||||
by allowing for repeatable, measureable
|
||||
and real world insights into Waku,
|
||||
all the way from theory to practice and back.
|
||||
* Reduce the risk of a Waku regression
|
||||
making it into a new release of Waku.
|
||||
|
||||
Additionally, these efforts will contribute
|
||||
to the Premier Research destination narrative by:
|
||||
|
||||
* Improving and strengthening our relationship with the Waku team
|
||||
and improving the quality and reputation of IFT's work, inside
|
||||
and outside of Waku.
|
||||
|
||||
### Additional info
|
||||
|
||||
## Task list
|
||||
|
||||
### Regression testing (recurring)
|
||||
|
||||
* fully qualified name: `vac:dst:waku:2025q3-waku-evaluation:regression-testing`
|
||||
* owner: Alberto
|
||||
* status: recurring
|
||||
* start-date: 2025-07-01
|
||||
* end-date: 2025-09-30
|
||||
|
||||
#### 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.
|
||||
|
||||
#### Deliverables
|
||||
- Reports:
|
||||
- Related PRs if apply:
|
||||
|
||||
### Quic-vs-tcp
|
||||
|
||||
* fully qualified name: `vac:dst:waku:2025q3-waku-evaluation:quic-vs-tcp`
|
||||
* owner: Alberto
|
||||
* status: 0%
|
||||
* start-date: -
|
||||
* end-date: -
|
||||
|
||||
#### Description
|
||||
|
||||
Perform a comparison between Waku using quic and waku using mplex and yamux.
|
||||
|
||||
#### Deliverables
|
||||
- Reports:
|
||||
- Related PRs if apply:
|
||||
|
||||
### JS waku
|
||||
|
||||
* fully qualified name: `vac:dst:waku:2025q3-waku-evaluation:js-waku`
|
||||
* owner: Alberto
|
||||
* status: 0%
|
||||
* start-date: -
|
||||
* end-date: -
|
||||
|
||||
#### Description
|
||||
|
||||
Start integrating js waku in DST experiments
|
||||
|
||||
#### Deliverables
|
||||
- Reports:
|
||||
- Related PRs if apply:
|
||||
194
content/dst/waku/2025q3-waku-scaling.md
Normal file
194
content/dst/waku/2025q3-waku-scaling.md
Normal file
@@ -0,0 +1,194 @@
|
||||
---
|
||||
title: Waku Scaling
|
||||
tags:
|
||||
- "2025q3"
|
||||
- "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:2025q3-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.
|
||||
|
||||
|
||||
### Background
|
||||
|
||||
### Narratives
|
||||
|
||||
These efforts will support the Conduit of Expertise narrative by
|
||||
accelerating Waku Improvements,
|
||||
providing measurable insights
|
||||
to enhance developer experience
|
||||
within and beyond the IFT ecosystem.
|
||||
Enhancing RFC Development by enabling faster,
|
||||
more informed RFC development
|
||||
through performance insights during the drafting process.
|
||||
|
||||
## Task list
|
||||
|
||||
|
||||
### TWN supports RLN onchain tree and deposits, existing memberships only
|
||||
> *Note*: This needs more input from project
|
||||
|
||||
[Link to Waku FURPS](https://github.com/waku-org/pm/blob/master/draft-roadmap/deploy_rln_onchain_tree_on_l2_testnet.md#twn-supports-rln-onchain-tree-and-deposits-existing-memberships-only)
|
||||
[Link to Waku FURPS](https://github.com/waku-org/pm/blob/master/draft-roadmap/rln_mainnet.md#twn-supports-rln-onchain-tree-and-deposits-existing-memberships-only)
|
||||
|
||||
* fully qualified name: `-`
|
||||
* owner: -
|
||||
* status: -
|
||||
* start-date: -
|
||||
* end-date: -
|
||||
|
||||
#### Description
|
||||
Waku estimated date of completion: 30 June 2025
|
||||
|
||||
Prove that a new node setup with an RLN membership can be ready
|
||||
to verify RLN proof within 5s, no matter the size of the tree.
|
||||
|
||||
#### Deliverables
|
||||
- Code:
|
||||
- Report:
|
||||
|
||||
|
||||
|
||||
### Hardening and Scaling Foundations for Private Chats
|
||||
> *Note*: This needs more input from project
|
||||
|
||||
[Link to Waku FURPS](https://github.com/waku-org/pm/blob/master/draft-roadmap/hardening_and_scaling_foundation_for_private_chat.md#hardening-and-scaling-foundations-for-private-chats)
|
||||
|
||||
* fully qualified name: `-`
|
||||
* owner: -
|
||||
* status: -
|
||||
* start-date: -
|
||||
* end-date: -
|
||||
|
||||
#### Description
|
||||
|
||||
To have: Vac-DST: status-backend benchmarks
|
||||
|
||||
#### Deliverables
|
||||
- Code:
|
||||
- Report:
|
||||
|
||||
|
||||
### Optimise Browser Bootstrapping
|
||||
> *Note*: This needs more input from project
|
||||
|
||||
[Link to Waku FURPS](https://github.com/waku-org/pm/blob/master/draft-roadmap/improve_devex_api_twn_metrics_docs.md#optimise-browser-bootstrapping)
|
||||
|
||||
* fully qualified name: `-`
|
||||
* owner: -
|
||||
* status: -
|
||||
* start-date: -
|
||||
* end-date: -
|
||||
|
||||
#### Description
|
||||
Waku estimated date of compeltion: 31 Aug
|
||||
|
||||
Using js-waku, prove that:
|
||||
- From an operating state, a node can
|
||||
resume transmitting messages within 1 second
|
||||
after disconnection; in a network with 1 bootstrap node,
|
||||
100 service nodes and 500 browser nodes.
|
||||
|
||||
- From a cold start, a node can start transmitting
|
||||
messages within 5 seconds; in a network with 1 bootstrap
|
||||
node, 100 service nodes and 500 browser nodes.
|
||||
|
||||
#### Deliverables
|
||||
- Code:
|
||||
- Report:
|
||||
|
||||
|
||||
|
||||
### Integrate nwaku in Status Desktop, relay mode only
|
||||
> *Note*: This needs more input from project
|
||||
|
||||
[Link to Waku FURPS](https://github.com/waku-org/pm/blob/master/draft-roadmap/integrate_nwaku_in_status_desktop_relay_mode_only.md#integrate-nwaku-in-status-desktop-relay-mode-only)
|
||||
|
||||
* fully qualified name: `-`
|
||||
* owner: -
|
||||
* status: -
|
||||
* start-date: -
|
||||
* end-date: -
|
||||
|
||||
#### Description
|
||||
|
||||
Waku estimated date of completion: 30 June
|
||||
|
||||
Vac-DST to complete go-waku-based benchmark works and proceed with
|
||||
nwaku-based vs go-waku-based status-backend comparisons.
|
||||
|
||||
#### Deliverables
|
||||
- Code:
|
||||
- Report:
|
||||
|
||||
|
||||
### SDS protocol in Status - basic integration
|
||||
|
||||
> *Note*: This needs more input from project
|
||||
|
||||
[Link to Waku FURPS](https://github.com/waku-org/pm/blob/master/draft-roadmap/introduce_e2e_reliability_in_status.md#sds-protocol-in-status---basic-integration)
|
||||
|
||||
* fully qualified name: `-`
|
||||
* owner: -
|
||||
* status: -
|
||||
* start-date: -
|
||||
* end-date: -
|
||||
|
||||
#### Description
|
||||
Waku estimated date of completion: 31 Aug
|
||||
|
||||
Prove that:
|
||||
- When sending a message in a group, the publisher
|
||||
can ensure the message was received by at least one
|
||||
recipient within `S` seconds
|
||||
|
||||
- When receiving messages in a group, the receiver
|
||||
can detect 90% of missed messages within `3*S` seconds
|
||||
|
||||
|
||||
#### Deliverables
|
||||
- Code:
|
||||
- Report:
|
||||
|
||||
|
||||
|
||||
### SDS protocol in Status - basic recovery
|
||||
|
||||
> *Note*: This needs more input from project
|
||||
|
||||
[Link to Waku FURPS](https://github.com/waku-org/pm/blob/master/draft-roadmap/introduce_e2e_reliability_in_status.md#sds-protocol-in-status---basic-recovery)
|
||||
|
||||
* fully qualified name: `-`
|
||||
* owner: -
|
||||
* status: -
|
||||
* start-date: -
|
||||
* end-date: -
|
||||
|
||||
#### Description
|
||||
Waku estimated date of completion: 31 Aug 2025
|
||||
|
||||
Prove that:
|
||||
- When receiving messages in group, the receiver can
|
||||
- reach eventual consistency within `6*S` seconds
|
||||
|
||||
#### Deliverables
|
||||
- Code:
|
||||
- Report:
|
||||
51
content/p2p/acz/2025q3-acz-consulting.md
Normal file
51
content/p2p/acz/2025q3-acz-consulting.md
Normal file
@@ -0,0 +1,51 @@
|
||||
---
|
||||
|
||||
title: ACZ Consulting
|
||||
tags:
|
||||
- "2025q3"
|
||||
- "p2p"
|
||||
- "acz"
|
||||
- "waku"
|
||||
draft: false
|
||||
description: P2P ad-hoc consulting for ACZ
|
||||
|
||||
---
|
||||
|
||||
`vac:p2p:acz:2025q3-acz-consulting`
|
||||
|
||||
P2P ad-hoc consulting for ACZ
|
||||
|
||||
## Description
|
||||
|
||||
P2P provides consulting and support to ACZ by addressing queries,
|
||||
formulating and designing strategies to utilize nim-libp2p and Waku more effectively,
|
||||
and removing blockers related to these products.
|
||||
Additionally, P2P offers guidance on resolving coding challenges that may arise during the development of these tasks.
|
||||
|
||||
## Task List
|
||||
|
||||
### Mix Consulting
|
||||
|
||||
* fully qualified name: `vac:p2p:acz:2025q2-acz-consulting:libp2p-mix-consulting`
|
||||
* owner: rramos
|
||||
* status: not started
|
||||
* start-date: 2025/07/01
|
||||
* end-date: 2025/09/30
|
||||
|
||||
#### Description
|
||||
Assist ACZ with the integration of mix with Waku. This task is primarily reactive, so aside from periodically checking in with the team to determine if assistance is needed, no additional actions are required unless requested
|
||||
|
||||
#### Deliverables
|
||||
|
||||
### de-MLS Consulting
|
||||
|
||||
* fully qualified name: `vac:p2p:acz:2025q2-acz-consulting:de-mls-consulting`
|
||||
* owner: rramos
|
||||
* status: not started
|
||||
* start-date: 2025/07/01
|
||||
* end-date: 2025/09/30
|
||||
|
||||
#### Description
|
||||
Assist ACZ with the integration of de-MLS with Waku. This task is primarily reactive, so aside from periodically checking in with the team to determine if assistance is needed, no additional actions are required unless requested
|
||||
|
||||
#### Deliverables
|
||||
@@ -25,7 +25,7 @@ During this quarter, we focus on a detailed evaluation of upcoming GossipSub pro
|
||||
|
||||
* fully qualified name: `vac:p2p:ift:2025q2-gossipsub-perf-improvements:perf-comparison`
|
||||
* owner: farooq
|
||||
* status: 75%
|
||||
* status: 90%
|
||||
* start-date: 2025/04/01
|
||||
* end-date: 2025/05/15
|
||||
|
||||
@@ -43,7 +43,7 @@ Nim, go, and rust libp2p test nodes are already implemented for the shadow simul
|
||||
|
||||
* fully qualified name: `vac:p2p:ift:2025q2-gossipsub-perf-improvements:gossipsub-1_4-impl`
|
||||
* owner: farooq
|
||||
* status:
|
||||
* status: 90%
|
||||
* start-date: 2025/04/01
|
||||
* end-date: 2025/06/30
|
||||
|
||||
@@ -61,7 +61,7 @@ The PoC implementation for GossipSubv1.4 is already complete. This work focuses
|
||||
|
||||
* fully qualified name: `vac:p2p:ift:2025q2-gossipsub-perf-improvements:community-engangement`
|
||||
* owner: farooq
|
||||
* status: 25%
|
||||
* status: 50%
|
||||
* start-date: 2025/04/01
|
||||
* end-date: 2025/06/30
|
||||
|
||||
@@ -101,7 +101,7 @@ unsupported system calls in the shadow simulator) or any other issues.
|
||||
|
||||
* fully qualified name: `vac:p2p:ift:2025q2-gossipsub-perf-improvements:stream-prioritization`
|
||||
* owner: farooq
|
||||
* status:
|
||||
* status: 25%
|
||||
* start-date: 2025/04/01
|
||||
* end-date: 2025/06/30
|
||||
|
||||
|
||||
@@ -25,9 +25,9 @@ This task is limited to the client functionality; Server functionality could be
|
||||
|
||||
* fully qualified name: `vac:p2p:ift:2025q2-nimlibp2p-autotls:acme-registration`
|
||||
* owner: gabriel
|
||||
* status: 95%
|
||||
* status: 100%
|
||||
* start-date: 2025-04-14
|
||||
* end-date:
|
||||
* end-date: 2025-06-06
|
||||
|
||||
#### Description
|
||||
Register new account on ACME server
|
||||
@@ -40,9 +40,9 @@ Register new account on ACME server
|
||||
|
||||
* fully qualified name: `vac:p2p:ift:2025q2-nimlibp2p-autotls:certificate-request-challenge`
|
||||
* owner: gabriel
|
||||
* status: 95%
|
||||
* status: 100%
|
||||
* start-date: 2025-04-14
|
||||
* end-date:
|
||||
* end-date: 2025-06-06
|
||||
|
||||
#### Description
|
||||
Request challenge from the ACME server (typically Let's Encrypt)
|
||||
|
||||
35
content/p2p/ift/2025q3-gossipsub-perf-improvements.md
Normal file
35
content/p2p/ift/2025q3-gossipsub-perf-improvements.md
Normal file
@@ -0,0 +1,35 @@
|
||||
---
|
||||
|
||||
title: GossipSub Performance Improvements
|
||||
tags:
|
||||
- "2025q3"
|
||||
- "p2p"
|
||||
- "ift"
|
||||
draft: false
|
||||
description: GossipSub Performance Improvements
|
||||
|
||||
---
|
||||
|
||||
`vac:p2p:ift:2025q3-gossipsub-perf-improvements`
|
||||
|
||||
## Description
|
||||
|
||||
TODO
|
||||
|
||||
## Task List
|
||||
|
||||
|
||||
### TODO
|
||||
|
||||
* fully qualified name: `vac:p2p:ift:2025q3-gossipsub-perf-improvements:TODO`
|
||||
* owner:
|
||||
* status: not started
|
||||
* start-date: 2025/07/01
|
||||
* end-date: 2025/09/30
|
||||
|
||||
#### Description
|
||||
|
||||
TODO
|
||||
|
||||
#### Deliverables
|
||||
|
||||
49
content/p2p/ift/2025q3-nimlibp2p-autonat-v2.md
Normal file
49
content/p2p/ift/2025q3-nimlibp2p-autonat-v2.md
Normal file
@@ -0,0 +1,49 @@
|
||||
---
|
||||
|
||||
title: AutoNAT v2
|
||||
tags:
|
||||
- "2025q3"
|
||||
- "p2p"
|
||||
- "ift"
|
||||
draft: false
|
||||
description: Implement AutoNAT v2
|
||||
|
||||
---
|
||||
|
||||
`vac:p2p:ift:2025q3-nimlibp2p-autonat-v2`
|
||||
|
||||
Implement AutoNAT V2 based on the [libp2p specification](https://github.com/libp2p/specs/blob/master/autonat/autonat-v2.md).
|
||||
|
||||
## Task List
|
||||
|
||||
### Client
|
||||
|
||||
* fully qualified name: `vac:p2p:ift:2025q2-nimlibp2p-autonat-v2t:client`
|
||||
* owner: gabe
|
||||
* status:
|
||||
* start-date: 2025-07-01
|
||||
* end-date:
|
||||
|
||||
#### Description
|
||||
Implement client side, constructing and sending `DialRequest`, handling `DialDataRequest`/`DialDataResponse` exchange,
|
||||
validate nonce on `DialBack` and parse `DialResponse`.
|
||||
Ensure interop against other implementations
|
||||
|
||||
#### Deliverables
|
||||
|
||||
|
||||
|
||||
### Server
|
||||
|
||||
* fully qualified name: `vac:p2p:ift:2025q2-nimlibp2p-autonat-v2:server`
|
||||
* owner: gabe
|
||||
* status:
|
||||
* start-date: 2025-07-01
|
||||
* end-date:
|
||||
|
||||
#### Description
|
||||
Address selection, dial address, send `DialBack`, handle nonce and do amplification check.
|
||||
Ensure interop against other implementations
|
||||
|
||||
#### Deliverables
|
||||
|
||||
82
content/p2p/ift/2025q3-nimlibp2p-kademlia.md
Normal file
82
content/p2p/ift/2025q3-nimlibp2p-kademlia.md
Normal file
@@ -0,0 +1,82 @@
|
||||
---
|
||||
|
||||
title: Kademlia DHT
|
||||
tags:
|
||||
- "2025q3"
|
||||
- "p2p"
|
||||
- "ift"
|
||||
draft: false
|
||||
description: Implement Kademlia DHT
|
||||
|
||||
---
|
||||
|
||||
`vac:p2p:ift:2025q3-nimlibp2p-kad-dht`
|
||||
|
||||
Implement Kademlia Distributed Hash Table in nim-libp2p, based on the [libp2p specification](https://github.com/libp2p/specs/blob/master/kad-dht/) as an additional discovery mechanism.
|
||||
This commitment involves two main objectives: implementing nim-kademlia-dht, and integrating this in nim-libp2p
|
||||
This deliverable continues the work started in 2025q2
|
||||
|
||||
## Task List
|
||||
|
||||
### Routing table and RPC Protocol
|
||||
|
||||
* fully qualified name: `vac:p2p:ift:2025q2-nimlibp2p-kad-dht:routing-and-rpc`
|
||||
* owner: rramos
|
||||
* status: 50%
|
||||
* start-date: 2025-04-08
|
||||
* end-date:
|
||||
|
||||
#### Description
|
||||
Implement Kademlia’s XOR-based routing table with bucket management. Define RPC messages (`PING`, `STORE`, `FIND_NODE`,
|
||||
`FIND_VALUE`) for node communication.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
|
||||
|
||||
### Bootstrapping & Lookup Mechanism
|
||||
|
||||
* fully qualified name: `vac:p2p:ift:2025q3-nimlibp2p-kad-dht:bootstraping-and-lookup`
|
||||
* owner: rramos
|
||||
* status: 35%
|
||||
* start-date: 2025-05-05
|
||||
* end-date:
|
||||
|
||||
#### Description
|
||||
Enable nodes to join the network via bootstrap peers. Implement iterative lookup for efficient key
|
||||
discovery and retrieval
|
||||
|
||||
#### Deliverables
|
||||
|
||||
|
||||
|
||||
### Network Maintenance & Node Management
|
||||
|
||||
* fully qualified name: `vac:p2p:ift:2025q3-nimlibp2p-kad-dht:network-maintenance-node-management`
|
||||
* owner: rramos
|
||||
* status: not started
|
||||
* start-date:
|
||||
* end-date:
|
||||
|
||||
#### Description
|
||||
Handle bucket refresh, node eviction, and periodic pings to maintain an active routing table.
|
||||
Implement bucket splitting and adaptive refresh strategies.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
|
||||
|
||||
### Data Storage & Replication
|
||||
|
||||
* fully qualified name: `vac:p2p:ift:2025q3-nimlibp2p-kad-dht:data-storage`
|
||||
* owner: rramos
|
||||
* status: not started
|
||||
* start-date:
|
||||
* end-date:
|
||||
|
||||
#### Description
|
||||
Store key-value pairs with expiration and replication mechanisms. Ensure values persist despite churn, using periodic
|
||||
re-publication and redundancy strategies.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
77
content/p2p/ift/2025q3-nimlibp2p-maintenance.md
Normal file
77
content/p2p/ift/2025q3-nimlibp2p-maintenance.md
Normal file
@@ -0,0 +1,77 @@
|
||||
---
|
||||
|
||||
title: Nim-libp2p maintenance
|
||||
tags:
|
||||
- "2025q3"
|
||||
- "p2p"
|
||||
- "ift"
|
||||
draft: false
|
||||
description: Maintain nim-libp2p through improvements, bug fixes, and user support
|
||||
|
||||
---
|
||||
|
||||
`vac:p2p:ift:2025q3-nimlibp2p-maintenance`
|
||||
|
||||
Maintain nim-libp2p through improvements, bug fixes, and user support
|
||||
|
||||
## Description
|
||||
|
||||
Continue supporting and maintaining the nim-libp2p repository through ongoing improvements, refactoring, and bug fixes.
|
||||
This includes a range of ad-hoc tasks critical to sustaining code quality, overall stability, correct functionality,
|
||||
and performance of the project.
|
||||
Additionally, it provides a platform for addressing small developer requests,
|
||||
ensuring that nim-libp2p remains functional and usable for its primary users — Nimbus and Waku — helping to meet their evolving needs."
|
||||
|
||||
## Task List
|
||||
|
||||
### Maintenance
|
||||
|
||||
* fully qualified name: `vac:p2p:ift:2025q3-nimlibp2p-maintenance:maintenance`
|
||||
* owner: rramos
|
||||
* status: not started
|
||||
* start-date: 2025/07/01
|
||||
* end-date: 2025/09/30
|
||||
|
||||
#### Description
|
||||
Maintain [nim-libp2p](https://github.com/vacp2p/nim-libp2p) repository via improvements, refactors and bug fixes.
|
||||
|
||||
#### Deliverables
|
||||
- [[Deliverable] Maintenance 2025Q3](TODO)
|
||||
|
||||
|
||||
|
||||
### Remove go-libp2p daemon
|
||||
|
||||
* fully qualified name: `vac:p2p:ift:2025q3-nimlibp2p-maintenance:go-libp2p-daemon`
|
||||
* owner:
|
||||
* status: not started
|
||||
* start-date:
|
||||
* end-date:
|
||||
|
||||
#### Description
|
||||
The overall goal is simplify the developer experience and reinforce the
|
||||
self-sufficiency of the nim-libp2p codebase. For this the following tasks must be implemented:
|
||||
- Audit and remove the dependency on go-libp2p-daemon in examples and unit tests,
|
||||
replacing it with native nim-libp2p components wherever feasible.
|
||||
- Ensure all example code is runnable with a Nim-only toolchain.
|
||||
- Update CI workflows to eliminate installation of go-libp2p-daemon;
|
||||
if removal is impractical, implement caching to reduce execution time
|
||||
|
||||
|
||||
#### Deliverables
|
||||
|
||||
|
||||
|
||||
### Fix flaky tests
|
||||
|
||||
* fully qualified name: `vac:p2p:ift:2025q3-nimlibp2p-maintenance:flaky-tests`
|
||||
* owner:
|
||||
* status: not started
|
||||
* start-date:
|
||||
* end-date:
|
||||
|
||||
#### Description
|
||||
Systematically track flaky tests using CI logs and failure reports,
|
||||
and fix root causes where reproducible (e.g. race conditions, timeouts, dependency order)
|
||||
|
||||
#### Deliverables
|
||||
52
content/p2p/ift/2025q3-nimlibp2p-mix.md
Normal file
52
content/p2p/ift/2025q3-nimlibp2p-mix.md
Normal file
@@ -0,0 +1,52 @@
|
||||
---
|
||||
|
||||
title: Nim-libp2p Mix
|
||||
tags:
|
||||
- "2025q3"
|
||||
- "p2p"
|
||||
- "ift"
|
||||
draft: false
|
||||
description: stabilize and upstream mix in nim-libp2p
|
||||
|
||||
---
|
||||
|
||||
`vac:p2p:ift:2025q3-nimlibp2p-mix`
|
||||
|
||||
Stabilize mix in nim-libp2p
|
||||
|
||||
## Description
|
||||
|
||||
Bring initial mix support in nim-libp2p to prototype status—clean codebase, enforce style/CI, prep for PoCs; concurrently, work with ACZ to upstream the specs.
|
||||
|
||||
## Task List
|
||||
|
||||
### Maintenance
|
||||
|
||||
* fully qualified name: `vac:p2p:ift:2025q3-nimlibp2p-mix:mix-core`
|
||||
* owner:
|
||||
* status: not started
|
||||
* start-date:
|
||||
* end-date:
|
||||
|
||||
#### Description
|
||||
Get the core mix functionality in nim-libp2p as Prototype / Unstable state, this will allow mix to be used in PoCs or experiments. Some rough edges and minor issues expected, not recommended for production and API and internal structure subject to changes. Implement any needed refactorings, code cleanup and style conformity, as well as setting up the repository so CI tasks for running test units and ensuring code formatting is applied, and master branch protection is enabled.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
|
||||
|
||||
### Specs
|
||||
|
||||
* fully qualified name: `vac:p2p:ift:2025q3-nimlibp2p-mix:specs`
|
||||
* owner:
|
||||
* status: not started
|
||||
* start-date:
|
||||
* end-date:
|
||||
|
||||
#### Description
|
||||
Collaborate with ACZ team into upstreaming initial mix design and rationale to
|
||||
`libp2p/spec` as proposal or draft PR.
|
||||
|
||||
|
||||
#### Deliverables
|
||||
|
||||
125
content/p2p/ift/2025q3-nimlibp2p-webtransport.md
Normal file
125
content/p2p/ift/2025q3-nimlibp2p-webtransport.md
Normal file
@@ -0,0 +1,125 @@
|
||||
---
|
||||
|
||||
title: nim-libp2p Webtransport
|
||||
tags:
|
||||
- "2025q3
|
||||
- "ift"
|
||||
draft: false
|
||||
description: Add webtransport support to nim-libp2p
|
||||
|
||||
---
|
||||
|
||||
`vac:p2p:ift:2025q3-nimlibp2p-webtransport`
|
||||
|
||||
Add webtransport support to nim-libp2p
|
||||
|
||||
## Description
|
||||
|
||||
Extend the number of transports supported by nim-libp2p via the developent of Webtransport,
|
||||
which would allow browsers to establish bidirectional stream connections to nim-libp2p servers
|
||||
This deliverable continues the work started in 2025q2
|
||||
|
||||
## Task List
|
||||
|
||||
### Wrapping nghttp3
|
||||
|
||||
* fully qualified name: `vac:p2p:ift:2025q3-nimlibp2p-webtransport:nghttp3-wrapping`
|
||||
* owner: vlado
|
||||
* status: 90%
|
||||
* start-date: 2025-04-11
|
||||
* end-date:
|
||||
|
||||
#### Description
|
||||
Create wrapper around the [nghttp3](https://github.com/ngtcp2/nghttp3) C library for Nim.
|
||||
|
||||
#### Deliverables
|
||||
- add nghttp3 wrapping with futhark [nim-nghttp3 #1](https://github.com/vacp2p/nim-nghttp3/pull/1)
|
||||
- ci: add ci for linux and mac [nim-nghttp3 #2](https://github.com/vacp2p/nim-nghttp3/pull/2)
|
||||
|
||||
### HTTP/3 Client
|
||||
|
||||
* fully qualified name: `vac:p2p:ift:2025q3-nimlibp2p-webtransport:http3-client`
|
||||
* owner: vlado
|
||||
* status: 25%
|
||||
* start-date: 2025-04-14
|
||||
* end-date:
|
||||
|
||||
#### Description
|
||||
Implement HTTP/3 Client following [draft-ietf-webtrans-http3-02](https://www.ietf.org/archive/id/draft-ietf-webtrans-http3-02.html) specification.
|
||||
This should be done as part of the [nim-quic](https://github.com/vacp2p/nim-quic) module.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
### HTTP/3 Server
|
||||
|
||||
* fully qualified name: `vac:p2p:ift:2025q3-nimlibp2p-webtransport:http3-server`
|
||||
* owner: vlado
|
||||
* status:
|
||||
* start-date:
|
||||
* end-date:
|
||||
|
||||
#### Description
|
||||
Implement HTTP/3 Server following [draft-ietf-webtrans-http3-02](https://www.ietf.org/archive/id/draft-ietf-webtrans-http3-02.html) specification.
|
||||
This should be done as part of the [nim-quic](https://github.com/vacp2p/nim-quic) module.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
### HTTP/3 Maintenance
|
||||
|
||||
* fully qualified name: `vac:p2p:ift:2025q3-nimlibp2p-webtransport:http3-maintenance`
|
||||
* owner: vlado
|
||||
* status:
|
||||
* start-date:
|
||||
* end-date:
|
||||
|
||||
#### Description
|
||||
Final improvements, code polishing and interoperability testing after Client and Server are merged.
|
||||
|
||||
|
||||
#### Deliverables
|
||||
|
||||
|
||||
|
||||
### Certificate generation
|
||||
|
||||
* fully qualified name: `vac:p2p:ift:2025q3-nimlibp2p-webtransport:certificate`
|
||||
* owner: vlado
|
||||
* status: not started
|
||||
* start-date:
|
||||
* end-date:
|
||||
|
||||
#### Description
|
||||
Certificate generation according to libp2p webtransport [specification](https://github.com/libp2p/specs/tree/master/webtransport)
|
||||
|
||||
#### Deliverables
|
||||
|
||||
|
||||
|
||||
### Key components implementation
|
||||
|
||||
* fully qualified name: `vac:p2p:ift:2025q3-nimlibp2p-webtransport:key-components`
|
||||
* owner: vlado
|
||||
* status: not started
|
||||
* start-date:
|
||||
* end-date:
|
||||
|
||||
#### Description
|
||||
Implement webtransport key components: Client, Server, Session
|
||||
|
||||
#### Deliverables
|
||||
|
||||
|
||||
|
||||
### Noise handshake and certificate validation
|
||||
|
||||
* fully qualified name: `vac:p2p:ift:2025q3-nimlibp2p-webtransport:handshake-and-cert-validation`
|
||||
* owner: vlado
|
||||
* status: not started
|
||||
* start-date:
|
||||
* end-date:
|
||||
|
||||
#### Description
|
||||
1.3. Noise handshake and certificate validtion according to libp2p webtransport [specification](https://github.com/libp2p/specs/tree/master/webtransport)
|
||||
|
||||
#### Deliverables
|
||||
|
||||
@@ -17,6 +17,23 @@ Major future work items on nim-libp2p (also beyond this reporting period are cap
|
||||
|
||||
[[preview|Roadmap Preview]]
|
||||
|
||||
### 2025q3
|
||||
|
||||
#### `ift:`
|
||||
* [[p2p/ift/2025q3-gossipsub-perf-improvements|2025q3-gossipsub-perf-improvements]]
|
||||
* [[p2p/ift/2025q3-nimlibp2p-kademlia|2025q3-nimlibp2p-kademlia]]
|
||||
* [[p2p/ift/2025q3-nimlibp2p-maintenance|2025q3-nimlibp2p-maintenance]]
|
||||
* [[p2p/ift/2025q3-nimlibp2p-webtransport|2025q3-nimlibp2p-webtransport]]
|
||||
* [[p2p/ift/2025q3-nimlibp2p-autonat-v2|2025q3-nimlibp2p-autonat-v2]]
|
||||
* [[p2p/ift/2025q3-nimlibp2p-mix|2025q3-nimlibp2p-mix]]
|
||||
|
||||
#### `vac:`
|
||||
* [[p2p/vac/2025q3-nimlibp2p-test-coverage|2025q3-nimlibp2p-test-coverage]]
|
||||
|
||||
#### `acz:`
|
||||
* [[p2p/acz/2025q3-acz-consulting|2025q3-acz-consulting]]
|
||||
|
||||
|
||||
### 2025q2
|
||||
|
||||
#### `ift:`
|
||||
|
||||
69
content/p2p/vac/2025q3-nimlibp2p-test-coverage.md
Normal file
69
content/p2p/vac/2025q3-nimlibp2p-test-coverage.md
Normal file
@@ -0,0 +1,69 @@
|
||||
---
|
||||
|
||||
title: nim-libp2p Test Coverage
|
||||
tags:
|
||||
- "2025q3"
|
||||
- "p2p"
|
||||
- "vac"
|
||||
draft: false
|
||||
description: nim-libp2p Test Coverage
|
||||
|
||||
---
|
||||
|
||||
`vac:p2p:vac:2025q3-nimlibp2p-test-coverage`
|
||||
|
||||
|
||||
nim-libp2p Improved Test Coverage
|
||||
|
||||
## Description
|
||||
Work closely with the QA and DST teams to identify key areas for improvement in the release and testing of nim-libp2p,
|
||||
ensuring better test coverage and reliability.
|
||||
|
||||
|
||||
## Task List
|
||||
|
||||
### Improve DST test node
|
||||
|
||||
* fully qualified name: `vac:p2p:vac:2025q3-test-coverage:dst-test-node`
|
||||
* owner:
|
||||
* status: not started
|
||||
* start-date:
|
||||
* end-date:
|
||||
|
||||
#### Description
|
||||
DST uses this [node](https://github.com/vacp2p/dst-gossipsub-test-node/blob/dockerized/main.nim) to do regression testing
|
||||
on each libp2p release. DST team has suggested that we collaborate in the refactoring of the node to allow custom test
|
||||
scenarios via specifying arguments/flags:
|
||||
- Choose the multiplexer to use without having to recompile
|
||||
- Number of nodes to connect to
|
||||
- Message Ratio
|
||||
- Message Weight
|
||||
- Connection parameters (currently all nodes try to connect to other N nodes)
|
||||
- External script for message injection instead of cron job
|
||||
|
||||
#### Deliverables
|
||||
|
||||
|
||||
|
||||
### QA Consulting over test coverage
|
||||
|
||||
* fully qualified name: `vac:p2p:vac:2025q3-test-coverage:qa-consulting`
|
||||
* owner: vlado
|
||||
* status:
|
||||
* start-date: 2025-07-01
|
||||
* end-date:
|
||||
|
||||
P2P provides consulting and support to QA by addressing queries, reviewing, formulating and designing strategies to test
|
||||
nim-libp2p more effectively, as well as offering guidance on resolving coding challenges that may arise during the
|
||||
development of the test units.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -36,7 +36,7 @@ identifying gaps and proposing or creating additional tests as necessary.
|
||||
|
||||
* fully qualified name: `vac:qa:ift:2025q2-qa-rfc-sync-waku:nwaku`
|
||||
* owner: fbarbu15
|
||||
* status: in progress (40%)
|
||||
* status: done
|
||||
* start-date: 2025/04/01
|
||||
* end-date: 2025/06/30
|
||||
|
||||
@@ -51,6 +51,9 @@ identifying gaps and proposing or creating additional tests as necessary.
|
||||
- Relay [done](https://www.notion.so/Nwaku-Relay-1ce8f96fb65c803a90f5c25076206ee7)
|
||||
- Filter [done](https://www.notion.so/Nwaku-Filter-1d18f96fb65c80b1a465d1bd022cd3f9)
|
||||
- Lightpush [done](https://www.notion.so/Nwaku-Lighpush-1e48f96fb65c805e88b9c084013a5d0c)
|
||||
- Store [done](https://www.notion.so/Nwaku-Store-2188f96fb65c80e78d08d3199aa103d6)
|
||||
- Reported issue with [store missmaches found](https://github.com/waku-org/nwaku/issues/3462)
|
||||
- Peer exchange [done](https://www.notion.so/Nwaku-Peer-Exchange-21f8f96fb65c80b0be68cc33f32a423d)
|
||||
|
||||
### js-waku
|
||||
|
||||
@@ -68,6 +71,7 @@ identifying gaps and proposing or creating additional tests as necessary.
|
||||
- Coordinate with developers for bug fixes and/or additional tests.
|
||||
|
||||
#### Deliverables
|
||||
* Note!! Moved to Q3. Could not be completed in Q2 because we were responsible for integrating status QA CCs into our team.
|
||||
* Notion page summarizing the current implementation-to-RFC mapping, discrepancies, and action items.
|
||||
* GitHub issues for required fixes or RFC updates.
|
||||
* Recommendations for improved or additional test coverage.
|
||||
@@ -81,6 +85,7 @@ identifying gaps and proposing or creating additional tests as necessary.
|
||||
* end-date: 2025/06/30
|
||||
|
||||
#### Description
|
||||
* Note!! No longer needed as go-waku will be sunset.
|
||||
- Compare each core protocol implemented in `go-waku` against the Waku RFCs.
|
||||
- Document any discrepancies found, such as missing specifications or incomplete implementations,
|
||||
and clarify whether the RFC or the implementation requires an update.
|
||||
|
||||
134
content/qa/ift/2025q3-qa-rfc-sync-jswaku.md
Normal file
134
content/qa/ift/2025q3-qa-rfc-sync-jswaku.md
Normal file
@@ -0,0 +1,134 @@
|
||||
---
|
||||
|
||||
title: QA & RFC Synchronization for Js-Waku Project - Core Protocols
|
||||
tags:
|
||||
- "2025q3"
|
||||
- "qa"
|
||||
- "ift"
|
||||
draft: false
|
||||
description: Expand and formalize the QA & RFC synchronization process for the core protocols for js-waku implementation.
|
||||
|
||||
---
|
||||
|
||||
`vac:qa:ift:2025q3-qa-rfc-sync-jswaku`
|
||||
|
||||
## Description
|
||||
Expand and formalize the QA & RFC synchronization process for js-waku implementation
|
||||
ensuring that core protocol implementations match specifications and have adequate test coverage.
|
||||
|
||||
Building on the previous quarter's efforts,
|
||||
this commitment focuses on systematically reviewing each Waku implementation (nim, js, go).
|
||||
to ensure core protocol implementations match the corresponding RFCs.
|
||||
Any discrepancies will be flagged for either:
|
||||
1. RFC updates (in collaboration with the RFC team), or
|
||||
2. Bug fixes and/or implementing missing parts in the respective repositories.
|
||||
|
||||
As part of this process, we will also assess the level of test automation and coverage for each core protocol,
|
||||
identifying gaps and proposing or creating additional tests as necessary.
|
||||
|
||||
**Alignment with VAC Narratives:**
|
||||
* Continues fostering collaboration between QA, RFC contributors, and engineering teams, ensuring changes in one area promptly reflect across the ecosystem.
|
||||
* Helps maintain a high standard for both internal and external contributions by detecting discrepancies early and closing testing gaps.
|
||||
|
||||
## Task List
|
||||
|
||||
### relay
|
||||
|
||||
* fully qualified name: `vac:qa:ift:2025q3-qa-rfc-sync-jswaku:relay`
|
||||
* owner: fbarbu15
|
||||
* status:
|
||||
* start-date:
|
||||
* end-date:
|
||||
|
||||
#### Description
|
||||
- Compare `relay` protocol implemented in `js-waku` against the Waku RFCs.
|
||||
- Document any discrepancies found, such as missing specifications or incomplete implementations,
|
||||
and clarify whether the RFC or the implementation requires an update.
|
||||
- Verify test automation exists for this protocol and note any coverage gaps.
|
||||
- Coordinate with developers for bug fixes and/or additional tests.
|
||||
|
||||
#### Deliverables
|
||||
- Notion page summarizing the current implementation-to-RFC mapping, discrepancies, and action items.
|
||||
- GitHub issues for required fixes or RFC updates.
|
||||
- Recommendations for improved or additional test coverage.
|
||||
|
||||
### filter
|
||||
|
||||
* fully qualified name: `vac:qa:ift:2025q3-qa-rfc-sync-jswaku:filter`
|
||||
* owner: fbarbu15
|
||||
* status:
|
||||
* start-date:
|
||||
* end-date:
|
||||
|
||||
#### Description
|
||||
- Compare `filter` protocol implemented in `js-waku` against the Waku RFCs.
|
||||
- Document any discrepancies found, such as missing specifications or incomplete implementations,
|
||||
and clarify whether the RFC or the implementation requires an update.
|
||||
- Verify test automation exists for this protocol and note any coverage gaps.
|
||||
- Coordinate with developers for bug fixes and/or additional tests.
|
||||
|
||||
#### Deliverables
|
||||
- Notion page summarizing the current implementation-to-RFC mapping, discrepancies, and action items.
|
||||
- GitHub issues for required fixes or RFC updates.
|
||||
- Recommendations for improved or additional test coverage.
|
||||
|
||||
### lightpush
|
||||
|
||||
* fully qualified name: `vac:qa:ift:2025q3-qa-rfc-sync-jswaku:lightpush`
|
||||
* owner: fbarbu15
|
||||
* status:
|
||||
* start-date:
|
||||
* end-date:
|
||||
|
||||
#### Description
|
||||
- Compare `lightpush` protocol implemented in `js-waku` against the Waku RFCs.
|
||||
- Document any discrepancies found, such as missing specifications or incomplete implementations,
|
||||
and clarify whether the RFC or the implementation requires an update.
|
||||
- Verify test automation exists for this protocol and note any coverage gaps.
|
||||
- Coordinate with developers for bug fixes and/or additional tests.
|
||||
|
||||
#### Deliverables
|
||||
- Notion page summarizing the current implementation-to-RFC mapping, discrepancies, and action items.
|
||||
- GitHub issues for required fixes or RFC updates.
|
||||
- Recommendations for improved or additional test coverage.
|
||||
|
||||
### store
|
||||
|
||||
* fully qualified name: `vac:qa:ift:2025q3-qa-rfc-sync-jswaku:store`
|
||||
* owner: fbarbu15
|
||||
* status:
|
||||
* start-date:
|
||||
* end-date:
|
||||
|
||||
#### Description
|
||||
- Compare `store` protocol implemented in `js-waku` against the Waku RFCs.
|
||||
- Document any discrepancies found, such as missing specifications or incomplete implementations,
|
||||
and clarify whether the RFC or the implementation requires an update.
|
||||
- Verify test automation exists for this protocol and note any coverage gaps.
|
||||
- Coordinate with developers for bug fixes and/or additional tests.
|
||||
|
||||
#### Deliverables
|
||||
- Notion page summarizing the current implementation-to-RFC mapping, discrepancies, and action items.
|
||||
- GitHub issues for required fixes or RFC updates.
|
||||
- Recommendations for improved or additional test coverage.
|
||||
|
||||
|
||||
### peer exchange
|
||||
|
||||
* fully qualified name: `vac:qa:ift:2025q3-qa-rfc-sync-jswaku:peer-exchange`
|
||||
* owner: fbarbu15
|
||||
* status:
|
||||
* start-date:
|
||||
* end-date:
|
||||
|
||||
#### Description
|
||||
- Compare `peer-exchange` protocol implemented in `js-waku` against the Waku RFCs.
|
||||
- Document any discrepancies found, such as missing specifications or incomplete implementations,
|
||||
and clarify whether the RFC or the implementation requires an update.
|
||||
- Verify test automation exists for this protocol and note any coverage gaps.
|
||||
- Coordinate with developers for bug fixes and/or additional tests.
|
||||
|
||||
#### Deliverables
|
||||
- Notion page summarizing the current implementation-to-RFC mapping, discrepancies, and action items.
|
||||
- GitHub issues for required fixes or RFC updates.
|
||||
- Recommendations for improved or additional test coverage.
|
||||
@@ -6,6 +6,30 @@ tags:
|
||||
|
||||
---
|
||||
|
||||
## 2025q3 `vac:qa:`
|
||||
---
|
||||
|
||||
### `ift:`
|
||||
* [[qa/ift/2025q3-qa-rfc-sync-jswaku|2025q3-qa-rfc-sync-jswaku ]]
|
||||
|
||||
### `vac:`
|
||||
* [[qa/vac/2025q3-nim-libp2p-testing|2025q3-nim-libp2p-testing ]]
|
||||
|
||||
### `waku:`
|
||||
* [[qa/waku/2025q3-waku-interop-testing|2025q3-waku-interop-testing ]]
|
||||
* [[qa/waku/2025q3-waku-chat-sdk-testing|2025q3-waku-chat-sdk-testing ]]
|
||||
* [[qa/waku/2025q3-waku-sync-int-testing|2025q3-waku-sync-int-testing ]]
|
||||
|
||||
### `status:`
|
||||
* [[qa/status/2025q3-status-go-functional-testing|2025q3-status-go-functional-testing ]]
|
||||
* [[qa/status/2025q3-status-qa-desktop|2025q3-status-qa-desktop ]]
|
||||
* [[qa/status/2025q3-status-qa-documentation|2025q3-status-qa-documentation ]]
|
||||
* [[qa/status/2025q3-status-qa-mobile|2025q3-status-qa-mobile ]]
|
||||
|
||||
### `keycard:`
|
||||
* [[qa/keycard/2025q3-keycard-testing|2025q3-keycard-testing ]]
|
||||
---
|
||||
|
||||
## 2025q2 `vac:qa:`
|
||||
---
|
||||
|
||||
@@ -19,7 +43,6 @@ tags:
|
||||
* [[qa/waku/2025q2-interop-testing|2025q2-interop-testing ]]
|
||||
* [[qa/waku/2025q2-waku-go-bindings-testing|2025q2-waku-go-bindings-testing ]]
|
||||
* [[qa/waku/2025q2-messaging-api-testing|2025q2-messaging-api-testing ]]
|
||||
* [[qa/waku/2025q2-status-go-functional-testing|2025q2-status-go-functional-testing ]]
|
||||
* [[qa/waku/2025q2-waku-sync-testing|2025q2-waku-sync-testing ]]
|
||||
|
||||
### `nomos:`
|
||||
@@ -28,6 +51,7 @@ tags:
|
||||
|
||||
### `status:`
|
||||
* [[qa/status/2025q2-status-qa|2025q2-status-qa ]]
|
||||
* [[qa/status/2025q2-status-go-functional-testing|2025q2-status-go-functional-testing ]]
|
||||
|
||||
---
|
||||
|
||||
|
||||
62
content/qa/keycard/2025q3-keycard-testing.md
Normal file
62
content/qa/keycard/2025q3-keycard-testing.md
Normal file
@@ -0,0 +1,62 @@
|
||||
---
|
||||
title: Keycard Testing
|
||||
tags:
|
||||
- "2025q3"
|
||||
- "qa"
|
||||
- "keycard"
|
||||
draft: true
|
||||
description: Ensure quality of Keycard applications.
|
||||
---
|
||||
|
||||
`vac:qa:keycard:2025q3-keycard-testing`
|
||||
|
||||
## Description
|
||||
|
||||
**Alignment with VAC Narratives:**
|
||||
|
||||
* The VAC QA team supports internal collaboration and efficiency
|
||||
by maintaining the quality and reliability of Keycard applications.
|
||||
|
||||
## Task List
|
||||
|
||||
### Keycard Shell Tests
|
||||
|
||||
* fully qualified name: `vac:qa:keycard:2025q3-keycard-testing:shell-tests`
|
||||
* owner: romanzac
|
||||
* status: not started
|
||||
* start-date:
|
||||
* end-date:
|
||||
|
||||
#### Description
|
||||
Create a suite of tests that verify that the Keycard Shell works as expected.
|
||||
|
||||
#### Deliverables
|
||||
- Test plan and test execution reports
|
||||
|
||||
### Keycard-go Unit Tests
|
||||
|
||||
* fully qualified name: `vac:qa:keycard:2025q3-keycard-testing:keycard-go-unit-tests`
|
||||
* owner: romanzac
|
||||
* status: not started
|
||||
* start-date:
|
||||
* end-date:
|
||||
|
||||
#### Description
|
||||
Review existing tests and add more tests to improve coverage. Add debugging tools and test coverage reporting.
|
||||
|
||||
#### Deliverables
|
||||
- PRs and CI runs
|
||||
|
||||
### Status-keycard-java Unit Tests
|
||||
|
||||
* fully qualified name: `vac:qa:keycard:2025q3-keycard-testing:status-keycard-java-unit-tests`
|
||||
* owner: romanzac
|
||||
* status: not started
|
||||
* start-date:
|
||||
* end-date:
|
||||
|
||||
#### Description
|
||||
Review existing tests and add more tests to improve coverage. Add debugging tools and test coverage reporting.
|
||||
|
||||
#### Deliverables
|
||||
- PRs and CI runs
|
||||
@@ -61,7 +61,7 @@ to ensure correct data flow and end-to-end processing.
|
||||
|
||||
* fully qualified name: `vac:qa:nomos:2025q2-da-testing:data-confidentiality`
|
||||
* owner: romanzac
|
||||
* status: in progress (30%)
|
||||
* status: done
|
||||
* start-date: 2025/05/19
|
||||
* end-date: 2025/06/6
|
||||
|
||||
@@ -71,13 +71,13 @@ ensuring secure communications, and controlling unauthorized access.
|
||||
|
||||
#### Deliverables
|
||||
- [test: Da networking encryption - PoC](https://github.com/logos-co/nomos-security-tests/pull/1)
|
||||
|
||||
- [test: data confidentiality](https://github.com/logos-co/nomos-e2e-tests/pull/18)
|
||||
|
||||
### Data Integrity and Dispersal Process Resilience
|
||||
|
||||
* fully qualified name: `vac:qa:nomos:2025q2-da-testing:dispersal-resilience`
|
||||
* owner: romanzac
|
||||
* status: not started
|
||||
* status: done
|
||||
* start-date: 2025/06/9
|
||||
* end-date: 2025/06/30
|
||||
|
||||
@@ -86,5 +86,13 @@ Add integration tests to verify the robustness of internal processes against tam
|
||||
and maintaining the integrity of the data handling mechanisms.
|
||||
|
||||
#### Deliverables
|
||||
* PR link with added tests
|
||||
* CI runs showing successful or failed executions with detailed reports
|
||||
- chore: Nomos node with mutated DA layer
|
||||
[PR 2](https://github.com/logos-co/nomos-security-tests/pull/2) -> cleanup into [PR 3](https://github.com/logos-co/nomos-security-tests/pull/3) is in progress
|
||||
- Test/dispersal resilience
|
||||
[PR 19](https://github.com/logos-co/nomos-e2e-tests/pull/19)
|
||||
- Dispersal not prevented for a blob with tampered data
|
||||
[Issue 1369 - open](https://github.com/logos-co/nomos/issues/1369)
|
||||
- Error 'blob sampling timed out' too generic to hint about problem with RS encoding
|
||||
[Issue 1383 - open](https://github.com/logos-co/nomos/issues/1383)
|
||||
- TF-IDF based log parsing
|
||||
[PR 20 - merged](https://github.com/logos-co/nomos-e2e-tests/pull/20)
|
||||
|
||||
@@ -27,7 +27,7 @@ and performing minor improvements to keep the framework functional and effective
|
||||
|
||||
* fully qualified name: `vac:qa:nomos:2025q2-e2e-testing:maintenance`
|
||||
* owner: romanzac
|
||||
* status: in progress (30%)
|
||||
* status: done
|
||||
* start-date: 2025/04/01
|
||||
* end-date: 2025/06/30
|
||||
|
||||
|
||||
@@ -3,12 +3,12 @@ title: Status Go Functional Testing
|
||||
tags:
|
||||
- "2025q2"
|
||||
- "qa"
|
||||
- "waku"
|
||||
- "status"
|
||||
draft: false
|
||||
description: Enhance functional testing for status-go features by implementing tests focused on Waku functionality.
|
||||
---
|
||||
|
||||
`vac:qa:waku:2025q2-status-go-functional-testing`
|
||||
`vac:qa:status:2025q2-status-go-functional-testing`
|
||||
|
||||
## Description
|
||||
Expand functional testing for status-go by implementing targeted Waku feature tests,
|
||||
@@ -26,7 +26,7 @@ as outlined in this [epic](https://github.com/status-im/status-go/issues/6064).
|
||||
|
||||
### Chat actions tests
|
||||
|
||||
* fully qualified name: `vac:qa:waku:2025q2-status-go-functional-testing:chat-actions-tests`
|
||||
* fully qualified name: `vac:qa:status:2025q2-status-go-functional-testing:chat-actions-tests`
|
||||
* owner: radek
|
||||
* status: done
|
||||
* start-date: 2025/04/01
|
||||
@@ -44,28 +44,30 @@ Cover the core functionality of Status related to [wakuext messages](https://git
|
||||
|
||||
### Contact requests tests
|
||||
|
||||
* fully qualified name: `vac:qa:waku:2025q2-status-go-functional-testing:contact-requests-tests`
|
||||
* fully qualified name: `vac:qa:status:2025q2-status-go-functional-testing:contact-requests-tests`
|
||||
* owner: fbarbu15
|
||||
* status: not started
|
||||
* start-date:
|
||||
* end-date:
|
||||
* status: done
|
||||
* start-date: 2025/04/01
|
||||
* end-date: 2025/04/07
|
||||
|
||||
#### Description
|
||||
Cover the [wakuext contact requests](https://github.com/status-im/status-go/issues/6085)
|
||||
|
||||
#### Deliverables
|
||||
* PRs with the new tests
|
||||
* [test_: contact requests 1](https://github.com/status-im/status-go/pull/6425)
|
||||
* [test_: contact requests 2](https://github.com/status-im/status-go/pull/6437)
|
||||
|
||||
|
||||
### Group chats tests
|
||||
|
||||
* fully qualified name: `vac:qa:waku:2025q2-status-go-functional-testing:group-chats-tests`
|
||||
* fully qualified name: `vac:qa:status:2025q2-status-go-functional-testing:group-chats-tests`
|
||||
* owner: fbarbu15
|
||||
* status: not started
|
||||
* start-date:
|
||||
* end-date:
|
||||
|
||||
#### Description
|
||||
Moved to Q3! Could not be completed in Q2 because we were responsible for integrating status QA CCs into our team.
|
||||
Cover the [wakuext group chats](https://github.com/status-im/status-go/issues/6071)
|
||||
|
||||
#### Deliverables
|
||||
@@ -73,9 +75,9 @@ Cover the [wakuext group chats](https://github.com/status-im/status-go/issues/60
|
||||
|
||||
### Tests on light mode
|
||||
|
||||
* fully qualified name: `vac:qa:waku:2025q2-status-go-functional-testing:light-mode`
|
||||
* fully qualified name: `vac:qa:status:2025q2-status-go-functional-testing:light-mode`
|
||||
* owner: fbarbu15
|
||||
* status: in progress (50%)
|
||||
* status: done
|
||||
* start-date: 2025/04/07
|
||||
* end-date: 2025/04/24
|
||||
|
||||
@@ -84,3 +86,4 @@ Enable running all waku tests also on light client mode
|
||||
|
||||
#### Deliverables
|
||||
- Enabled light client mode for [waku functional tests](https://github.com/status-im/status-go/pull/6518/files)
|
||||
- Created dedicated Readme for the status-backend reliability [test suite](https://github.com/status-im/status-go/pull/6700)
|
||||
@@ -21,11 +21,41 @@ QA work for Status for Q3 will be defined in follow up commitments.
|
||||
### Maintenance
|
||||
|
||||
* fully qualified name: `vac:qa:status:2025q2-status-qa:v2-34`
|
||||
* owner:
|
||||
* status: in progress ()
|
||||
* owner: nastya,tetiana,magnus
|
||||
* status: done
|
||||
* start-date: 2025/05/20
|
||||
* end-date: 2025/06/10
|
||||
|
||||
#### Description
|
||||
|
||||
#### Deliverables
|
||||
- finished the main round testing for mobile 2.34, the full report is [here](https://www.notion.so/2-34-Mobile-Release-Coordination-1f88f96fb65c80589326d087cfc6f0f5)
|
||||
- retested several fixes, reported 12 issues [here](https://www.notion.so/2-34-Mobile-Release-Coordination-1f88f96fb65c80589326d087cfc6f0f5)
|
||||
- logged a couple of issues for desktop (including the results of e2e):
|
||||
- https://github.com/status-im/status-desktop/issues/18053
|
||||
- https://github.com/status-im/status-desktop/issues/18043
|
||||
- https://github.com/status-im/status-desktop/issues/18018
|
||||
- https://github.com/status-im/status-desktop/issues/18063
|
||||
- opened a PR to partially remove unused code and merge 2 tests of similar functionality in 1 https://github.com/status-im/status-desktop/pull/18052
|
||||
- started fixing tests to fit them into qt 6.9 app (in scope of https://github.com/status-im/status-desktop/pull/18019)
|
||||
- Research and shared findings regarding opening RC testing to community
|
||||
- Tested fix of 2 blockers
|
||||
- Tested new feature required for 2.34
|
||||
- Tested a fix for [18063](https://github.com/status-im/status-desktop/issues/18063)
|
||||
- Signed off the final mobile build
|
||||
- [critical flow RecoverAndLogin with 12,15,24 words mnemonic](https://github.com/status-im/status-go/pull/6688)
|
||||
- [enhance pytest logging - filter noise, show full logs on failure](https://github.com/status-im/status-go/pull/6697)
|
||||
- Qt6 migration support
|
||||
- Created test plan for Shell
|
||||
- Added basic support for Shell to e2e (https://github.com/status-im/status-desktop/pull/18172/)
|
||||
- Fixed nightly [fails](https://github.com/status-im/status-desktop/pull/18212)
|
||||
- Reviewed failed tests and confirmed a [bug](https://github.com/status-im/status-desktop/pull/18169)
|
||||
- continue on supporting tests for [QT6](https://github.com/status-im/status-desktop/pull/18019)
|
||||
- [Remove or replace Ethereum Testnet (Ropsten) derivation path option](https://github.com/status-im/status-desktop/issues/18241)
|
||||
- investigated issue with non-draggable window on [Mac](https://github.com/status-im/status-desktop/issues/18261)
|
||||
- fix nightly failures due to shell screen being [enabled](https://github.com/status-im/status-desktop/pull/18254)
|
||||
- Profile popup is too wide on [MacOS](https://github.com/status-im/status-desktop/issues/18264)
|
||||
- logging [improvements](https://github.com/status-im/status-go/pull/6697)
|
||||
- fixture-based refactor of [StatusBackend](https://github.com/status-im/status-go/issues/6718)
|
||||
- Added support for shell on [critical tests](https://github.com/status-im/status-desktop/pull/18172)
|
||||
- Adding support for squish to [tablet build](https://github.com/status-im/status-desktop/pull/18267)
|
||||
|
||||
108
content/qa/status/2025q3-status-go-functional-testing.md
Normal file
108
content/qa/status/2025q3-status-go-functional-testing.md
Normal file
@@ -0,0 +1,108 @@
|
||||
---
|
||||
title: Status Go Functional Testing
|
||||
tags:
|
||||
- "2025q3"
|
||||
- "qa"
|
||||
- "status"
|
||||
draft: false
|
||||
description: Enhance functional and e2e testing for status-go features by implementing tests using status-backend.
|
||||
---
|
||||
|
||||
`vac:qa:status:2025q3-status-go-functional-testing`
|
||||
|
||||
## Description
|
||||
Expand functional and e2e testing for status-go by implementing tests using status-backend,
|
||||
as outlined in this [epic](https://github.com/status-im/status-go/issues/6064).
|
||||
|
||||
**Alignment with VAC Narratives:**
|
||||
* By helping create a robust functional testing framework for Status Go,
|
||||
VAC QA contributes directly to the narrative of internal collaboration and efficiency.
|
||||
* By finding issues in the project code and specs during testing,
|
||||
VAC QA strengthens the RFC culture, contributing to continuous improvement and community engagement.
|
||||
|
||||
## Task List
|
||||
|
||||
### Critical user flows
|
||||
|
||||
* fully qualified name: `vac:qa:status:2025q3-status-go-functional-testing:critical-flows`
|
||||
* owner: chu
|
||||
* status: not started
|
||||
* start-date:
|
||||
* end-date:
|
||||
|
||||
#### Description
|
||||
Add functional test coverage to critical user flows like onboarding,
|
||||
asset management or messaging as described in this [epic](https://github.com/status-im/status-go/issues/6064).
|
||||
|
||||
#### Deliverables
|
||||
* PRs with the new tests
|
||||
|
||||
|
||||
### Wallet features
|
||||
|
||||
* fully qualified name: `vac:qa:status:2025q3-status-go-functional-testing:wallet`
|
||||
* owner: chu
|
||||
* status: not started
|
||||
* start-date:
|
||||
* end-date:
|
||||
|
||||
#### Description
|
||||
Add functional test coverage to wallet features,
|
||||
in order to catch regressions introduced by wallet backend refactoring.
|
||||
Focus on e2e scenarios that can be automated at this level.
|
||||
TODO! This taks will need to be broken down into smaller task once we have more info
|
||||
|
||||
#### Deliverables
|
||||
* Test plans
|
||||
* PRs with the new tests
|
||||
|
||||
|
||||
### Framework usage improvements
|
||||
|
||||
* fully qualified name: `vac:qa:status:2025q3-status-go-functional-testing:framework-improvements`
|
||||
* owner: chu
|
||||
* status: not started
|
||||
* start-date:
|
||||
* end-date:
|
||||
|
||||
#### Description
|
||||
Improve and simplify user/dev experience when running tests locally.
|
||||
Update readme and debugging.
|
||||
|
||||
#### Deliverables
|
||||
* PRs with the new tests
|
||||
|
||||
|
||||
### Status-backend based on nwaku
|
||||
|
||||
* fully qualified name: `vac:qa:status:2025q3-status-go-functional-testing:status-based-on-nwaku`
|
||||
* owner: chu
|
||||
* status: not started
|
||||
* start-date:
|
||||
* end-date:
|
||||
|
||||
#### Description
|
||||
Run all status-backend tests on a
|
||||
[nwaku-based build](https://github.com/waku-org/pm/blob/2025H2/draft-roadmap/integrate_nwaku_in_status_desktop_relay_mode_only.md?plain=1#L7)
|
||||
as described in the Waku FURPS
|
||||
|
||||
#### Deliverables
|
||||
* Test Reports
|
||||
|
||||
|
||||
### Reliability in Status Communities
|
||||
|
||||
* fully qualified name: `vac:qa:status:2025q3-status-go-functional-testing:reliability-communities`
|
||||
* owner: chu
|
||||
* status: not started
|
||||
* start-date:
|
||||
* end-date:
|
||||
|
||||
#### Description
|
||||
- R1. When sending a message in a group, the publisher can ascertain the message was received by at least one recipient.
|
||||
- R2. When receiving messages in a group, the receiver can ascertain most missed messages by receiving one recent message from the group.
|
||||
- See [Waku FURPS](https://github.com/waku-org/pm/blob/2025H2/draft-roadmap/introduce_e2e_reliability_in_status.md?plain=1#L40)
|
||||
|
||||
#### Deliverables
|
||||
* PRs with the new tests
|
||||
|
||||
108
content/qa/status/2025q3-status-qa-desktop.md
Normal file
108
content/qa/status/2025q3-status-qa-desktop.md
Normal file
@@ -0,0 +1,108 @@
|
||||
---
|
||||
|
||||
title: Status QA Desktop
|
||||
tags:
|
||||
- "2025q3"
|
||||
- "qa"
|
||||
- "status"
|
||||
draft: false
|
||||
description: Status QA Desktop
|
||||
|
||||
---
|
||||
|
||||
`vac:qa:status:2025q3-status-qa-desktop`
|
||||
|
||||
## Description
|
||||
Collaborate with Status team to ensure that the Status Desktop app behaves as expected.
|
||||
Add new automated tests to the existing e2e testing framework for new features.
|
||||
Oversee testing strategy around releases.
|
||||
|
||||
|
||||
**Alignment with VAC Narratives:**
|
||||
* By helping to test the Status Desktop application,
|
||||
VAC QA contributes directly to the narrative of internal collaboration and efficiency..
|
||||
* Helps maintain a high standard for both internal and external contributions
|
||||
by detecting discrepancies early and closing testing gaps.
|
||||
|
||||
## Task List
|
||||
|
||||
### Release Testing
|
||||
|
||||
* fully qualified name: `vac:qa:status:2025q3-status-qa-desktop:release-testing`
|
||||
* owner: nastya
|
||||
* status:
|
||||
* start-date:
|
||||
* end-date:
|
||||
|
||||
#### Description
|
||||
- Oversee testing strategy for new releases.
|
||||
- Ensure that the VAC QA team, Status developers, and the community
|
||||
provide sufficient testing to support high-quality releases.
|
||||
|
||||
#### Deliverables
|
||||
- PRs
|
||||
|
||||
|
||||
### Shell view
|
||||
|
||||
* fully qualified name: `vac:qa:status:2025q3-status-qa-desktop:shell-view`
|
||||
* owner: nastya
|
||||
* status:
|
||||
* start-date:
|
||||
* end-date:
|
||||
|
||||
#### Description
|
||||
- Add new automated tests for the `Shell view` feature.
|
||||
- Review and assist devs with feature testing.
|
||||
|
||||
#### Deliverables
|
||||
- PRs
|
||||
|
||||
|
||||
### Ethereum follow protocol
|
||||
|
||||
* fully qualified name: `vac:qa:status:2025q3-status-qa-desktop:eth-follow-protocol`
|
||||
* owner: nastya
|
||||
* status:
|
||||
* start-date:
|
||||
* end-date:
|
||||
|
||||
#### Description
|
||||
- Add new automated tests for the `Ethereum follow protocol` feature.
|
||||
- Review and assist devs with feature testing.
|
||||
|
||||
#### Deliverables
|
||||
- PRs
|
||||
|
||||
|
||||
### Backup user data
|
||||
|
||||
* fully qualified name: `vac:qa:status:2025q3-status-qa-desktop:backup-user-data`
|
||||
* owner: nastya
|
||||
* status:
|
||||
* start-date:
|
||||
* end-date:
|
||||
|
||||
#### Description
|
||||
- Add new automated tests for the `Backup user data` feature.
|
||||
- Review and assist devs with feature testing.
|
||||
|
||||
#### Deliverables
|
||||
- PRs
|
||||
|
||||
|
||||
### Maintenance
|
||||
|
||||
* fully qualified name: `vac:qa:status:2025q3-status-qa-desktop:maintenance`
|
||||
* owner: nastya
|
||||
* status:
|
||||
* start-date:
|
||||
* end-date:
|
||||
|
||||
#### Description
|
||||
- Ongoing maintenance of Status Desktop tests. This includes updating tests for changes in status,
|
||||
addressing regressions, investigating and resolving issues,
|
||||
and implementing minor improvements to the testing framework as needed.
|
||||
|
||||
#### Deliverables
|
||||
- PRs
|
||||
84
content/qa/status/2025q3-status-qa-documentation.md
Normal file
84
content/qa/status/2025q3-status-qa-documentation.md
Normal file
@@ -0,0 +1,84 @@
|
||||
---
|
||||
|
||||
title: Status QA Documentation
|
||||
tags:
|
||||
- "2025q3"
|
||||
- "qa"
|
||||
- "status"
|
||||
draft: false
|
||||
description: QA documentation for the Status ecosystem.
|
||||
|
||||
---
|
||||
|
||||
`vac:qa:status:2025q3-status-qa-documentation`
|
||||
|
||||
## Description
|
||||
Establish QA documentation for the Status ecosystem,
|
||||
building on existing rfc and other documentation sources to cover app functionality.
|
||||
We should cover:
|
||||
- overall QA strategy Documentation
|
||||
- test plans for status features and components
|
||||
- requirements documentation framework that has:
|
||||
- feature tracking
|
||||
- document lifecycle management
|
||||
- tooling and templates to support community involvement in QA processes
|
||||
|
||||
|
||||
**Alignment with VAC Narratives:**
|
||||
* Continues fostering collaboration between QA, RFC contributors,
|
||||
and engineering teams, ensuring changes in one area promptly reflect across the ecosystem.
|
||||
* Helps maintain a high standard for both internal and external contributions
|
||||
by detecting discrepancies early and closing testing gaps.
|
||||
|
||||
## Task List
|
||||
|
||||
### QA Strategy
|
||||
|
||||
* fully qualified name: `vac:qa:status:2025q3-status-qa-documentation:strategy`
|
||||
* owner: magnus
|
||||
* status:
|
||||
* start-date:
|
||||
* end-date:
|
||||
|
||||
#### Description
|
||||
- Create a knowledge base containing the QA strategy
|
||||
for the core components under Status ecosystem.
|
||||
- For each components, we will document the existing tests, coverage,
|
||||
how and when they are run, any identified gaps, and recommendations for improvement.
|
||||
|
||||
#### Deliverables
|
||||
- Notion page with QA strategy
|
||||
|
||||
|
||||
### Test Plans
|
||||
|
||||
* fully qualified name: `vac:qa:status:2025q3-status-qa-documentation:test-plans`
|
||||
* owner: magnus
|
||||
* status:
|
||||
* start-date:
|
||||
* end-date:
|
||||
|
||||
#### Description
|
||||
- Create test plans for new Status features, releases and [RFCs](https://rfc.vac.dev/status).
|
||||
- Identify and flag gaps.
|
||||
|
||||
#### Deliverables
|
||||
- Notion pages with test plans
|
||||
|
||||
|
||||
### Requirements Documentation Framework
|
||||
* fully qualified name: `vac:qa:status:2025q3-status-qa-documentation:requirements-framework`
|
||||
* owner: magnus
|
||||
* status:
|
||||
* start-date:
|
||||
* end-date:
|
||||
|
||||
#### Description
|
||||
- Implement a framework covering Status Desktop core features,
|
||||
with workflows and compatibility with other tooling.
|
||||
|
||||
#### Deliverables
|
||||
- Adapt POC framework to Status with latest revisions (add Feature Context docs and lifecycle management)
|
||||
- Migrate existing docs and create tooling (GitHub Actions, static site generation, TestRail integration)
|
||||
- Expand coverage of core features (wallet, chat, communities, settings modules with full flow/screen documentation)
|
||||
- Develop team adoption workflows for new features (training materials, review processes, maintenance procedures)
|
||||
71
content/qa/status/2025q3-status-qa-mobile.md
Normal file
71
content/qa/status/2025q3-status-qa-mobile.md
Normal file
@@ -0,0 +1,71 @@
|
||||
---
|
||||
|
||||
title: Status QA Mobile
|
||||
tags:
|
||||
- "2025q3"
|
||||
- "qa"
|
||||
- "status"
|
||||
draft: false
|
||||
description: Status QA Mobile
|
||||
|
||||
---
|
||||
|
||||
`vac:qa:status:2025q3-status-qa-mobile`
|
||||
|
||||
## Description
|
||||
Collaborate with Status team to ensure that the new Status mobile/tablet app behaves as expected.
|
||||
Extend and adjust the existing e2e test Framework to support testing on mobile/tablet.
|
||||
|
||||
|
||||
**Alignment with VAC Narratives:**
|
||||
* By helping create a robust mobile testing framework for the new Status App,
|
||||
VAC QA contributes directly to the narrative of internal collaboration and efficiency..
|
||||
* Helps maintain a high standard for both internal and external contributions
|
||||
by detecting discrepancies early and closing testing gaps.
|
||||
|
||||
## Task List
|
||||
|
||||
### Framework Adjustments
|
||||
|
||||
* fully qualified name: `vac:qa:status:2025q3-status-qa-mobile:framework-adjustments`
|
||||
* owner: nastya
|
||||
* status:
|
||||
* start-date:
|
||||
* end-date:
|
||||
|
||||
#### Description
|
||||
- Adjust the existing squish Framework to run on mobile/tablet.
|
||||
- POC: Port at least 1 test to run on mobile/tablet.
|
||||
|
||||
#### Deliverables
|
||||
- PRs
|
||||
|
||||
|
||||
### Port desktop tests
|
||||
|
||||
* fully qualified name: `vac:qa:status:2025q3-status-qa-mobile:port-tests`
|
||||
* owner: magnus
|
||||
* status:
|
||||
* start-date:
|
||||
* end-date:
|
||||
|
||||
#### Description
|
||||
- Port all relevant tests to run on mobile/tablet.
|
||||
|
||||
#### Deliverables
|
||||
- PRs
|
||||
|
||||
|
||||
### Multiple devices
|
||||
|
||||
* fully qualified name: `vac:qa:status:2025q3-status-qa-mobile:multiple-devices`
|
||||
* owner: magnus
|
||||
* status:
|
||||
* start-date:
|
||||
* end-date:
|
||||
|
||||
#### Description
|
||||
- Make necessary changes so that tests can run on different Android and iOS mobile/table devices.
|
||||
|
||||
#### Deliverables
|
||||
- PRs and CI runs
|
||||
@@ -68,7 +68,7 @@ Focus: clean up `nim-libp2p` PRs and issues related to `GossipSub` tests which w
|
||||
|
||||
* fully qualified name: `vac:qa:vac:2025q2-nim-libp2p-testing:gossipsub-extended-part2`
|
||||
* owner: radek
|
||||
* status: in progress (70%)
|
||||
* status: done
|
||||
* start-date: 2025/05/19
|
||||
* end-date: 2025/06/09
|
||||
|
||||
@@ -85,12 +85,16 @@ Focus: implementation of tests according to the test plan, sections:
|
||||
- [test(gossipsub): heartbeat tests](https://github.com/vacp2p/nim-libp2p/pull/1391)
|
||||
- [test(gossipsub): include missing test files and handle flaky tests](https://github.com/vacp2p/nim-libp2p/pull/1416)
|
||||
- [fix(gossipsub): save iDontWants messages in the first element of history](https://github.com/vacp2p/nim-libp2p/pull/1393)
|
||||
- [test(gossipsub): message cache](https://github.com/vacp2p/nim-libp2p/pull/1431)
|
||||
- [test: checkUntilTimeout refactor](https://github.com/vacp2p/nim-libp2p/pull/1437)
|
||||
- [fix(GossipSub): save sent iHave in first element](https://github.com/vacp2p/nim-libp2p/pull/1405)
|
||||
- [test(gossipsub): paremeters](https://github.com/vacp2p/nim-libp2p/pull/1442)
|
||||
|
||||
### Gossipsub Extended - part3
|
||||
|
||||
* fully qualified name: `vac:qa:vac:2025q2-nim-libp2p-testing:gossipsub-extended-part3`
|
||||
* owner: radek
|
||||
* status: not started (0%)
|
||||
* status: done
|
||||
* start-date: 2025/06/09
|
||||
* end-date: 2025/06/30
|
||||
|
||||
@@ -102,7 +106,16 @@ Focus: implementation of tests according to the test plan, sections:
|
||||
- Compatibility of Older/Newer Versions of the Protocol
|
||||
|
||||
#### Deliverables
|
||||
* PRs with links to added tests
|
||||
- [test(gossipsub): flaky tests](https://github.com/vacp2p/nim-libp2p/pull/1451)
|
||||
- [test: increase timeout](https://github.com/vacp2p/nim-libp2p/pull/1460)
|
||||
- [test(gossipsub): refactor and unify scoring tests](https://github.com/vacp2p/nim-libp2p/pull/1461)
|
||||
- [test(gossipsub): GossipThreshold and PublishThreshold tests](https://github.com/vacp2p/nim-libp2p/pull/1464)
|
||||
- [test(gossipsub): split unit and integration tests](https://github.com/vacp2p/nim-libp2p/pull/1465)
|
||||
- [test(gossipsub): rpcHandler - rateLimit and punishInvalidMessage tests](https://github.com/vacp2p/nim-libp2p/pull/1467)
|
||||
- [test(gossipsub): organise Behavior tests](https://github.com/vacp2p/nim-libp2p/pull/1468)
|
||||
- [test(gossipsub): behaviourPenalty tests](https://github.com/vacp2p/nim-libp2p/pull/1469)
|
||||
- [test(gossipsub): updateScores tests](https://github.com/vacp2p/nim-libp2p/pull/1471)
|
||||
- [test(gossipsub): scoring integration test](https://github.com/vacp2p/nim-libp2p/pull/1487)
|
||||
|
||||
### Pubsub
|
||||
|
||||
@@ -113,6 +126,8 @@ Focus: implementation of tests according to the test plan, sections:
|
||||
* end-date:
|
||||
|
||||
#### Description
|
||||
Moved to Q3! Gossipsub took longer than expected, but was done thoroughly.
|
||||
|
||||
Expand the pubsub test coverage by following the test plan,
|
||||
checking what’s not covered, and implementing new tests for those scenarios.
|
||||
|
||||
@@ -128,6 +143,8 @@ checking what’s not covered, and implementing new tests for those scenarios.
|
||||
* end-date:
|
||||
|
||||
#### Description
|
||||
Moved to Q3! Gossipsub took longer than expected, but was done thoroughly.
|
||||
|
||||
Expand the floodsub test coverage by following the test plan,
|
||||
checking what’s not covered, and implementing new tests for those scenarios.
|
||||
|
||||
@@ -138,13 +155,15 @@ checking what’s not covered, and implementing new tests for those scenarios.
|
||||
|
||||
* fully qualified name: `vac:qa:vac:2025q2-nim-libp2p-testing:test-plans`
|
||||
* owner: fbarbu15
|
||||
* status: in progress (20%)
|
||||
* status: done
|
||||
* start-date: 2025/04/01
|
||||
* end-date: 2025/06/30
|
||||
|
||||
#### Description
|
||||
Update part done, new test plan creation moved to Q3!
|
||||
|
||||
Update and add new test plans for identify / push identify, ping, mplex multiplexer,
|
||||
and others to be determined later.
|
||||
|
||||
#### Deliverables
|
||||
* Link with the Notion pages
|
||||
* [test plans](https://www.notion.so/Test-Plans-bd1d0eb57d334945a02a5f5dfc921c02)
|
||||
|
||||
130
content/qa/vac/2025q3-nim-libp2p-testing.md
Normal file
130
content/qa/vac/2025q3-nim-libp2p-testing.md
Normal file
@@ -0,0 +1,130 @@
|
||||
---
|
||||
|
||||
title: Nim Libp2p Testing
|
||||
tags:
|
||||
- "2025q3"
|
||||
- "qa"
|
||||
- "vac"
|
||||
draft: false
|
||||
description: Continue expanding nim-libp2p testing coverage with focus on pubsub, yamux, rendezvous and floodsub protocols.
|
||||
|
||||
---
|
||||
|
||||
`vac:qa:vac:2025q3-nim-libp2p-testing`
|
||||
|
||||
## Description
|
||||
Continue expanding nim-libp2p testing coverage, documentation, and tooling with focus on protocols beyond Gossipsub.
|
||||
|
||||
Complete any remaining Gossipsub testing tasks, expand pubsub testing coverage for scenarios not covered by Gossipsub tests, implement comprehensive testing for Yamux multiplexer and Rendezvous protocol, and add Floodsub testing if time permits.
|
||||
Improve tooling around nim libp2p testing and ensure all implemented modules have adequate test coverage.
|
||||
|
||||
**Alignment with VAC Narratives:**
|
||||
* Nim-libp2p is a key component of the VAC ecosystem,
|
||||
and improving its testing coverage and tooling strengthens our internal expertise
|
||||
and the overall reliability of the network.
|
||||
* By enhancing these tests, and creating test plans,
|
||||
we support the RFC culture by providing feedback to the specifications,
|
||||
ensuring they align with real-world implementation.
|
||||
* These efforts also contribute to scaling the project's capacity,
|
||||
as better testing tools empower the open-source community to participate effectively.
|
||||
|
||||
## Task List
|
||||
|
||||
### Gossipsub Extended - Completion
|
||||
|
||||
* fully qualified name: `vac:qa:vac:2025q3-nim-libp2p-testing:gossipsub-completion`
|
||||
* owner: radek
|
||||
* status: not started
|
||||
* start-date: 2025/07/01
|
||||
* end-date: 2025/07/15
|
||||
|
||||
#### Description
|
||||
Complete any remaining Gossipsub testing tasks from Q2 if not fully finished.
|
||||
Ensure all edge cases and advanced scenarios are properly covered.
|
||||
|
||||
#### Deliverables
|
||||
* PRs with links to added tests
|
||||
|
||||
### Pubsub Testing
|
||||
|
||||
* fully qualified name: `vac:qa:vac:2025q3-nim-libp2p-testing:pubsub`
|
||||
* owner: radek
|
||||
* status: not started
|
||||
* start-date: 2025/07/15
|
||||
* end-date: 2025/07/31
|
||||
|
||||
#### Description
|
||||
Investigate and implement pubsub tests that can be done in isolation and make sense
|
||||
beyond what is already covered by Gossipsub testing. Focus on core pubsub functionality,
|
||||
base protocol behaviors, subscription management, message validation, and pubsub router
|
||||
interactions that are protocol-agnostic.
|
||||
|
||||
#### Deliverables
|
||||
* PRs with links to added tests
|
||||
|
||||
### Yamux Multiplexer Testing
|
||||
|
||||
* fully qualified name: `vac:qa:vac:2025q3-nim-libp2p-testing:yamux`
|
||||
* owner: radek
|
||||
* status: not started
|
||||
* start-date: 2025/08/01
|
||||
* end-date: 2025/08/31
|
||||
|
||||
#### Description
|
||||
Implement testing for the Yamux multiplexer protocol in nim-libp2p.
|
||||
Yamux is a stream multiplexing protocol that allows multiple logical streams
|
||||
over a single connection. Testing should cover stream creation and management,
|
||||
flow control, backpressure handling, concurrent stream operations, error handling,
|
||||
and edge cases.
|
||||
|
||||
#### Deliverables
|
||||
* PRs with links to added tests
|
||||
|
||||
### Rendezvous Protocol Testing
|
||||
|
||||
* fully qualified name: `vac:qa:vac:2025q3-nim-libp2p-testing:rendezvous`
|
||||
* owner: radek
|
||||
* status: not started
|
||||
* start-date: 2025/09/01
|
||||
* end-date: 2025/09/30
|
||||
|
||||
#### Description
|
||||
Implement testing for the Rendezvous protocol, which provides a way for peers
|
||||
to discover each other through a rendezvous point. The protocol allows peers
|
||||
to register themselves at a rendezvous point and discover other peers with
|
||||
similar interests or capabilities.
|
||||
|
||||
#### Deliverables
|
||||
* PRs with links to added tests
|
||||
|
||||
### Floodsub Testing (If Time Permits)
|
||||
|
||||
* fully qualified name: `vac:qa:vac:2025q3-nim-libp2p-testing:floodsub`
|
||||
* owner: radek
|
||||
* status: not started
|
||||
* start-date: 2025/09/15
|
||||
* end-date: 2025/09/30
|
||||
|
||||
#### Description
|
||||
If previous tasks are completed ahead of schedule, implement comprehensive
|
||||
testing for the Floodsub protocol. Floodsub is a basic pubsub implementation
|
||||
that floods messages to all peers in the network, serving as a simpler
|
||||
alternative to Gossipsub.
|
||||
|
||||
#### Deliverables
|
||||
* PRs with links to added tests
|
||||
|
||||
### Test Plans and Documentation
|
||||
|
||||
* fully qualified name: `vac:qa:vac:2025q3-nim-libp2p-testing:test-plans`
|
||||
* owner: fbarbu15
|
||||
* status: not started
|
||||
* start-date: 2025/07/01
|
||||
* end-date: 2025/09/30
|
||||
|
||||
#### Description
|
||||
Update and add new test plans for identify / push identify, ping, mplex multiplexer,
|
||||
and others to be determined later.
|
||||
|
||||
#### Deliverables
|
||||
* Link with the Notion pages
|
||||
@@ -26,7 +26,7 @@ and performing minor improvements to keep the framework functional and effective
|
||||
|
||||
* fully qualified name: `vac:qa:waku:2025q2-interop-testing:maintenance`
|
||||
* owner: fbarbu15
|
||||
* status: in progress (40%)
|
||||
* status: done
|
||||
* start-date: 2025/04/01
|
||||
* end-date: 2025/06/30
|
||||
|
||||
@@ -41,7 +41,10 @@ investigating and resolving issues, and implementing minor improvements to the t
|
||||
- [chore: add reconciliation metrics](https://github.com/waku-org/waku-interop-tests/pull/113)
|
||||
- [test: Many tests fail on CI related to topics supscribtion](https://github.com/waku-org/nwaku/issues/3414)
|
||||
- [chore: Remove go-waku from workflows](https://github.com/waku-org/waku-interop-tests/pull/117)
|
||||
|
||||
- [bug: node won’t start with RLN in on-chain dynamic mode 2](https://github.com/waku-org/nwaku/issues/3208)
|
||||
- [bug: Raised issue related to relay fetch](https://github.com/waku-org/nwaku/issues/3444)
|
||||
- [chore: Fixed failing tests](https://github.com/waku-org/waku-interop-tests/pull/121)
|
||||
- [bug: node won't start with RLN in on-chain dynamic mode](https://github.com/waku-org/nwaku/issues/3208)
|
||||
|
||||
### js-waku filter hardening
|
||||
|
||||
@@ -52,6 +55,8 @@ investigating and resolving issues, and implementing minor improvements to the t
|
||||
* end-date: 2025/04/30
|
||||
|
||||
#### Description
|
||||
Moved to Q3! Could not be completed in Q2 because we were responsible for integrating status QA CCs into our team.
|
||||
|
||||
Harden js-waku filter protocol by adding more advanced tests like:
|
||||
- Longevity test focused on sending/receiving messages continuously over a long duration (e.g., 6 hours)
|
||||
- Sanity checks in terms of throughput of Waku messages of different sizes
|
||||
|
||||
@@ -62,7 +62,7 @@ PRs and issues
|
||||
|
||||
* fully qualified name: `vac:qa:waku:2025q2-waku-go-bindings-testing:maintenance`
|
||||
* owner: aya
|
||||
* status: in progress (50%)
|
||||
* status: done
|
||||
* start-date: 2025/04/01
|
||||
* end-date: 2025/06/30
|
||||
|
||||
@@ -81,7 +81,7 @@ investigating and resolving issues, and implementing minor improvements to the t
|
||||
- [bug: MsgChan still full after reading messages](https://github.com/waku-org/waku-go-bindings/issues/70)
|
||||
- [bug: Test failed with error ConnectionChangeChan is full](https://github.com/waku-org/waku-go-bindings/issues/71)
|
||||
- [Warning message about exception in pubsub handling](https://github.com/waku-org/waku-go-bindings/issues/72)
|
||||
|
||||
- Monitroring CI daily failures and update summary [report](https://discord.com/channels/@me/1338127019740889141/1387020605202759710) with failed tests & share with devs
|
||||
|
||||
### 12H Longevity
|
||||
|
||||
|
||||
@@ -29,7 +29,7 @@ and integration testing involving multi-peer synchronization, message archival,
|
||||
|
||||
* fully qualified name: `vac:qa:waku:2025q2-waku-sync-testing:unit`
|
||||
* owner: aya
|
||||
* status: in progress(40%)
|
||||
* status: done
|
||||
* start-date: 2025/04/08
|
||||
* end-date: 2025/04/28
|
||||
|
||||
@@ -48,12 +48,14 @@ These tests aim to validate internal mechanics such as:
|
||||
#### Deliverables
|
||||
- Prepared [sheet](https://docs.google.com/spreadsheets/d/1Qj5LMyWR-ILA2wqd4eGe7j_V311QonZJ0LqnaWAJxMM/edit?gid=293767216#gid=293767216) with missing coverage for unit tests
|
||||
- [test: Add comprehensive reconciliation unit-tests for Waku Store Sync](https://github.com/waku-org/nwaku/pull/3388)
|
||||
- [test: Waku sync tests part2](https://github.com/waku-org/nwaku/pull/3397)
|
||||
- [fix: fix failed sync test](https://github.com/waku-org/nwaku/pull/3464)
|
||||
|
||||
### Waku Sync Integration Testing
|
||||
|
||||
* fully qualified name: `vac:qa:waku:2025q2-waku-sync-testing:integration`
|
||||
* owner: aya
|
||||
* status: in progress(10%)
|
||||
* status: done
|
||||
* start-date: 2025/04/29
|
||||
* end-date: 2025/05/19
|
||||
|
||||
@@ -68,7 +70,5 @@ These tests will include real-world edge cases like:
|
||||
- Handling cluster and shard mismatches
|
||||
|
||||
#### Deliverables
|
||||
|
||||
PRs and issues
|
||||
|
||||
|
||||
- Issue [3471](https://github.com/waku-org/nwaku/issues/3471)
|
||||
- Issue [3479](https://github.com/waku-org/nwaku/issues/3479)
|
||||
|
||||
77
content/qa/waku/2025q3-waku-chat-sdk-testing.md
Normal file
77
content/qa/waku/2025q3-waku-chat-sdk-testing.md
Normal file
@@ -0,0 +1,77 @@
|
||||
---
|
||||
title: Chat SDK Testing
|
||||
tags:
|
||||
- "2025q3"
|
||||
- "qa"
|
||||
- "waku"
|
||||
draft: false
|
||||
description: Test and validate the reliability of the Waku Chat SDK
|
||||
---
|
||||
|
||||
`vac:qa:waku:2025q3-waku-chat-sdk-testing`
|
||||
|
||||
## Description
|
||||
Test and validate the reliability of the Waku Chat SDK
|
||||
in accordance to [Waku FURPS](https://github.com/waku-org/pm/blob/2025H2/2025H2-summary.md?plain=1#L76).
|
||||
Ensure the SDK performs consistently
|
||||
and meets the expected functional and reliability requirements.
|
||||
Note! This could be pushed to Q4 if the feature is not QA ready as planned.
|
||||
|
||||
**Alignment with VAC Narratives:**
|
||||
- By testing the Waku Chat SDK,
|
||||
VAC QA ensures robust and predictable behavior across diverse environments and tools.
|
||||
- This initiative supports VAC’s commitment to building reliable and scalable testing frameworks
|
||||
that foster collaboration and confidence in the Waku ecosystem.
|
||||
- Reliability-focused testing directly aligns with the strategic objective of ensuring resilience in communication protocols.
|
||||
|
||||
## Task List
|
||||
|
||||
### Integrate Functional Testing into Interop Framework
|
||||
|
||||
* fully qualified name: `vac:qa:waku:2025q3-waku-chat-sdk-testing:functional-interop`
|
||||
* owner: fbarbu15
|
||||
* status: not started
|
||||
* start-date:
|
||||
* end-date:
|
||||
|
||||
#### Description
|
||||
Implement functional tests for the new Waku Chat SDK within the interop testing framework.
|
||||
|
||||
#### Deliverables
|
||||
* PRs with functional tests integrated into the interop testing framework
|
||||
* CI integration for these functional tests
|
||||
* Documentation outlining tested scenarios
|
||||
|
||||
### Reliability Testing for nwaku
|
||||
|
||||
* fully qualified name: `vac:qa:waku:2025q3-waku-chat-sdk-testing:functional-nwaku`
|
||||
* owner: fbarbu15
|
||||
* status: not started
|
||||
* start-date:
|
||||
* end-date:
|
||||
|
||||
#### Description
|
||||
Test the core functionality of the Waku Chat SDK implemented in `nwaku`.
|
||||
Validate message reliability under various conditions, including network instability.
|
||||
|
||||
#### Deliverables
|
||||
* PRs with functional test cases for `nwaku`
|
||||
* CI pipelines for automated tests
|
||||
|
||||
### Long-Run Testing
|
||||
|
||||
* fully qualified name: `vac:qa:waku:2025q3-waku-chat-sdk-testing:long-run`
|
||||
* owner: fbarbu15
|
||||
* status: not started
|
||||
* start-date:
|
||||
* end-date:
|
||||
|
||||
#### Description
|
||||
Perform long-duration tests to validate the Waku Chat SDK’s reliability over extended periods.
|
||||
Focus on scenarios such as repeated reconnections, sustained message delivery,
|
||||
and node resilience under ongoing network challenges.
|
||||
|
||||
#### Deliverables
|
||||
* PRs with long-run test scenarios
|
||||
* Reliability metrics from extended tests
|
||||
* Recommendations for enhancements based on long-run test results
|
||||
85
content/qa/waku/2025q3-waku-interop-testing.md
Normal file
85
content/qa/waku/2025q3-waku-interop-testing.md
Normal file
@@ -0,0 +1,85 @@
|
||||
---
|
||||
title: Waku Interop Testing
|
||||
tags:
|
||||
- "2025q3"
|
||||
- "qa"
|
||||
- "waku"
|
||||
draft: false
|
||||
description: Maintain and ensure the reliability of Waku interop tests.
|
||||
---
|
||||
|
||||
`vac:qa:waku:2025q3-interop-testing`
|
||||
|
||||
## Description
|
||||
Maintain and ensure the continued reliability of the Waku interop testing framework.
|
||||
This includes addressing regressions, adapting to changes in `nwaku` and `gowaku`,
|
||||
and performing minor improvements to keep the framework functional and effective.
|
||||
|
||||
**Alignment with VAC Narratives:**
|
||||
|
||||
* The VAC QA team supports internal collaboration and efficiency
|
||||
by maintaining the quality and reliability of the Waku interop framework.
|
||||
|
||||
## Task List
|
||||
|
||||
### Maintenance
|
||||
|
||||
* fully qualified name: `vac:qa:waku:2025q3-interop-testing:maintenance`
|
||||
* owner: fbarbu15
|
||||
* status:
|
||||
* start-date:
|
||||
* end-date:
|
||||
|
||||
#### Description
|
||||
Ongoing maintenance of Waku interop tests.
|
||||
This includes updating tests for changes in `nwaku` or `js-waku`, addressing regressions,
|
||||
investigating and resolving issues, and implementing minor improvements to the testing framework as needed.
|
||||
|
||||
#### Deliverables
|
||||
- PRs or Issues
|
||||
|
||||
### js-waku filter hardening
|
||||
|
||||
* fully qualified name: `vac:qa:waku:2025q3-interop-testing:jswaku-filter-hardening`
|
||||
* owner: fbarbu15
|
||||
* status:
|
||||
* start-date:
|
||||
* end-date:
|
||||
|
||||
#### Description
|
||||
Harden js-waku filter protocol by adding more advanced tests like:
|
||||
- Sanity checks in terms of throughput of Waku messages of different sizes
|
||||
- Sending/receiving thousands of messages in a short period of time
|
||||
|
||||
#### Deliverables
|
||||
- PRs or Issues
|
||||
|
||||
### Lite protocol tester
|
||||
|
||||
* fully qualified name: `vac:qa:waku:2025q3-interop-testing:liteprotocoltester`
|
||||
* owner: fbarbu15
|
||||
* status:
|
||||
* start-date:
|
||||
* end-date:
|
||||
|
||||
#### Description
|
||||
Explore, fix and improve [waku lite protocol tester](https://github.com/waku-org/nwaku/tree/master/apps/liteprotocoltester)
|
||||
based on nwaku dev requirements
|
||||
|
||||
#### Deliverables
|
||||
- PRs or Issues
|
||||
|
||||
### Waku cannary tool
|
||||
|
||||
* fully qualified name: `vac:qa:waku:2025q3-interop-testing:wakucannary`
|
||||
* owner: fbarbu15
|
||||
* status:
|
||||
* start-date:
|
||||
* end-date:
|
||||
|
||||
#### Description
|
||||
Explore, fix and improve [waku canary tool](https://github.com/waku-org/nwaku/tree/master/apps/wakucanary)
|
||||
based on nwaku dev requirements
|
||||
|
||||
#### Deliverables
|
||||
- PRs or Issues
|
||||
47
content/qa/waku/2025q3-waku-sync-int-testing.md
Normal file
47
content/qa/waku/2025q3-waku-sync-int-testing.md
Normal file
@@ -0,0 +1,47 @@
|
||||
---
|
||||
title: Waku-sync Integration Testing
|
||||
tags:
|
||||
- "2025q3"
|
||||
- "qa"
|
||||
- "waku"
|
||||
draft: false
|
||||
description: Continue Waku Sync Integration testing
|
||||
---
|
||||
|
||||
`vac:qa:waku:2025q3-waku-sync-int-testing`
|
||||
|
||||
## Description
|
||||
|
||||
Continue Waku Sync Integration testing in `nwaku`.
|
||||
|
||||
**Alignment with VAC Narratives:**
|
||||
|
||||
* The VAC QA team contributes to the robustness of the Waku protocol suite
|
||||
by ensuring correctness and completeness of newer components such as Waku Sync.
|
||||
* By exposing edge cases and ensuring spec alignment,
|
||||
these tests enhance the RFC lifecycle and provide confidence to teams building on top of `nwaku`.
|
||||
|
||||
## Task List
|
||||
|
||||
|
||||
### Waku Sync Integration Testing
|
||||
|
||||
* fully qualified name: `vac:qa:waku:2025q3-waku-sync-int-testing:integration`
|
||||
* owner: aya
|
||||
* status: not started
|
||||
* start-date:
|
||||
* end-date:
|
||||
|
||||
#### Description
|
||||
|
||||
Develop integration tests that simulate full protocol interaction across multiple nodes.
|
||||
These tests will include real-world edge cases like:
|
||||
|
||||
- Multi-peer end-to-end synchronization
|
||||
- Archive-driven message reconciliation
|
||||
- Message transfer over delayed and lossy networks
|
||||
- Handling cluster and shard mismatches
|
||||
|
||||
#### Deliverables
|
||||
|
||||
PRs and issues
|
||||
@@ -51,7 +51,7 @@ in their projects, similar to [IETF](https://www.ietf.org/).
|
||||
- Fully qualified name:
|
||||
`vac:rfc:codex:2025q2-rfc-iteration:the-block-exchange'
|
||||
- Owner: cofson
|
||||
- Status: 0%
|
||||
- Status: 10%
|
||||
- Start date: 2025/06/01
|
||||
- End date: 2025/06/20
|
||||
|
||||
|
||||
@@ -43,7 +43,7 @@ similar to [IETF](https://www.ietf.org/).
|
||||
|
||||
- Fully qualified name: `vac:rfc:ift:2025q2-culture-establishment-team-communication`
|
||||
- Owner: cofson
|
||||
- Status: not started
|
||||
- Status: 100%
|
||||
- Start date: 2025/04/01
|
||||
- End date: 2025/06/30
|
||||
|
||||
|
||||
@@ -28,7 +28,7 @@ in accordance with the IFT standards.
|
||||
|
||||
- Fully qualified name: `vac:rfc:ift:2025q2-rfc-index-maintenance:maintenance`
|
||||
- Owner: Filip
|
||||
- Status: not started
|
||||
- Status: 100%
|
||||
- Start date: 2025/04/01
|
||||
- End date: 2025/06/30
|
||||
|
||||
@@ -46,7 +46,7 @@ note them properly.
|
||||
|
||||
- Fully qualified name: `vac:rfc:ift:2025q2-rfc-index-maintenance:maintenance-of-vac.dev`
|
||||
- Owner: Filip
|
||||
- Status: not started
|
||||
- Status: 100%
|
||||
- Start date: 2025/04/01
|
||||
- End date: 2025/06/30
|
||||
|
||||
|
||||
@@ -44,15 +44,15 @@ in their projects, similar to [IETF](https://www.ietf.org/).
|
||||
- Fully qualified name:
|
||||
`vac:rfc:nescience:2025q2-rfc-iteration:key-protocol-specification`
|
||||
- Owner: cofson
|
||||
- Status: not started
|
||||
- Start date: 2025/05/05
|
||||
- End date: 2025/05/31
|
||||
- Status: 99% (https://github.com/vacp2p/rfc-index/pull/162)
|
||||
- Start date: 2025/06/05
|
||||
- End date: 2025/06/31
|
||||
|
||||
### UTXO Specification
|
||||
|
||||
- Fully qualified name:
|
||||
`vac:rfc:nescience:2025q2-rfc-iteration:utxo-specification`
|
||||
- Owner: cofson
|
||||
- Status: not started
|
||||
- Start date: 2025/05/05
|
||||
- End date: 2025/05/31
|
||||
- Status: 99% (https://github.com/vacp2p/rfc-index/pull/164)
|
||||
- Start date: 2025/06/05
|
||||
- End date: 2025/06/31
|
||||
|
||||
@@ -42,7 +42,7 @@ in their projects, similar to [IETF](https://www.ietf.org/).
|
||||
Fully qualified name:
|
||||
`vac:rfc:nomos:2025q2-rfc-iteration-choosing-new-rfcs`
|
||||
- Owner: cofson
|
||||
- Status: 45%
|
||||
- Status: 100%
|
||||
- Start date: 2025/04/01
|
||||
- End date: 2025/06/30
|
||||
|
||||
@@ -57,16 +57,16 @@ and thus ready for being included in the rfc-index.
|
||||
- Fully qualified name:
|
||||
`vac:rfc:nomos:2025q2-rfc-iteration:30/adaptive-nodes`
|
||||
- Owner: cofson
|
||||
- Status: 45%
|
||||
- Status: 99% (https://github.com/vacp2p/rfc-index/pull/157)
|
||||
- Start date: 2025/05/04
|
||||
- End date: 2025/04/21
|
||||
- End date: 2025/05/21
|
||||
|
||||
### NomosDA Encoding
|
||||
|
||||
- Fully qualified name:
|
||||
`vac:rfc:nomos:2025q2-rfc-iteration:nomosda-encoding`
|
||||
- Owner: cofson
|
||||
- Status: 45%
|
||||
- Status: 99% (https://github.com/vacp2p/rfc-index/pull/156)
|
||||
- Start date: 2025/05/04
|
||||
- End date: 2025/04/21
|
||||
|
||||
@@ -75,6 +75,6 @@ and thus ready for being included in the rfc-index.
|
||||
- Fully qualified name:
|
||||
`vac:rfc:nomos:2025q2-rfc-iteration:nomosda-network`
|
||||
- Owner: cofson
|
||||
- Status: not started
|
||||
- Status: 99% (https://github.com/vacp2p/rfc-index/pull/160)
|
||||
- Start date: 2025/05/04
|
||||
- End date: 2025/04/21
|
||||
- End date: 2025/05/21
|
||||
@@ -99,7 +99,7 @@ as well as any other outdated parts of the specification.
|
||||
- Fully qualified name:
|
||||
`vac:rfc:waku:2025q1-rfc-iteration:53/waku2-x3dh`
|
||||
- Owner: cofson
|
||||
- Status: 95%
|
||||
- Status: 100% (https://github.com/vacp2p/rfc-index/pull/150)
|
||||
- Start date: 2025/04/20
|
||||
- End date: 2025/05/05
|
||||
|
||||
@@ -167,7 +167,7 @@ as well as any other outdated parts of the specification.
|
||||
- Fully qualified name:
|
||||
`vac:rfc:waku:2025q1-rfc-iteration:waku2-enr`
|
||||
- Owner: jimstir
|
||||
- Status: 0%
|
||||
- Status: 95% (https://github.com/waku-org/specs/pull/67)
|
||||
- Start date: 2025/05/15
|
||||
- End date: 2025/05/25
|
||||
|
||||
@@ -189,7 +189,7 @@ as well as any other outdated parts of the specification.
|
||||
- Fully qualified name:
|
||||
`vac:rfc:waku:2025q1-rfc-iteration:waku2-device-pairing`
|
||||
- Owner: jimstir
|
||||
- Status: 40%
|
||||
- Status: 100% (https://github.com/waku-org/specs/pull/63)
|
||||
- Start date: 2025/05/09
|
||||
- End date: 2025/05/20
|
||||
|
||||
|
||||
@@ -21,8 +21,8 @@ Codex aims to extract all funds related logic of the `MarketPlace` contract into
|
||||
### Review Vault contract
|
||||
|
||||
* fully qualified name: `2025q1-vault-integration:review-vault-contract`
|
||||
* owner:
|
||||
* status: 5%
|
||||
* owner: r4bbit
|
||||
* status: 100%
|
||||
* start-date: 2025/04/01
|
||||
* end-date: 2025/04/15
|
||||
|
||||
|
||||
@@ -1,14 +1,14 @@
|
||||
---
|
||||
title: Formal Verification Tools Research
|
||||
tags:
|
||||
- "2025q2"
|
||||
- "2025q3"
|
||||
- "sc"
|
||||
- "ift"
|
||||
draft: false
|
||||
description: Look into alternative formal verification tools and their integration with the existing smart contracts.
|
||||
---
|
||||
|
||||
`vac:sc:ift:2025q2-fv-tools-research`
|
||||
`vac:sc:ift:2025q3-fv-tools-research`
|
||||
|
||||
Look into alternative formal verification tools and their integration with the existing smart contracts.
|
||||
|
||||
@@ -20,7 +20,7 @@ Look into alternative formal verification tools and their integration with the e
|
||||
|
||||
### Research alternative tools
|
||||
|
||||
* fully qualified name: `2025q2-fv-tools-research:research-alternatives`
|
||||
* fully qualified name: `2025q3-fv-tools-research:research-alternatives`
|
||||
* owner: r4bbit
|
||||
* status: not started
|
||||
* start-date: 2025/04/01
|
||||
90
content/sc/ift/2025q3-sc-learnup-sessions.md
Normal file
90
content/sc/ift/2025q3-sc-learnup-sessions.md
Normal file
@@ -0,0 +1,90 @@
|
||||
---
|
||||
title: Smart Contracts LearnUp Sessions
|
||||
tags:
|
||||
- "2025q3"
|
||||
- "sc"
|
||||
- "ift"
|
||||
draft: false
|
||||
description: Monthly learn up sessions about anything smart contracts related.
|
||||
---
|
||||
|
||||
`vac:sc:ift:2025q3-sc-learnup-sessions`
|
||||
|
||||
Monthly learn up sessions about smart contract development, protocols, security and alike.
|
||||
|
||||
## Description
|
||||
|
||||
The smart contract service unit is running a monthly learn up session about protocols,
|
||||
Ethereum Improvement Proposals (EIPs) and similar topics related to smart contract development and security.
|
||||
The goal is to learn more about the Ethereum ecosystem and to discuss the presented topics with the team and anyone else who wants to join.
|
||||
|
||||
By organizing these presentations and having discussions that are open to the entire IFT organization,
|
||||
the smart contracts team fosters a culture of knowledge sharing and continuous learning across teams,
|
||||
improving cross-project collaboration.
|
||||
|
||||
## Task List
|
||||
|
||||
### Smart Contracts LearnUp Sessions 2025 Q3
|
||||
|
||||
* fully qualified name: `2025q3-sc-learnup-sessions:2025q3`
|
||||
* owner: r4bbit
|
||||
* status: not started
|
||||
* start-date: 2025/07/01
|
||||
* end-date: 2025/09/30
|
||||
|
||||
#### Description
|
||||
|
||||
Organize learn up session on a monthly basis and ensure meetings are recorded and provided to the IFT.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- [ ] Recording of the sessions
|
||||
|
||||
### SC LearnUp Session 2025/07
|
||||
|
||||
* fully qualified name: `2025q3-sc-learnup-sessions:2025-07`
|
||||
* owner: r4bbit
|
||||
* status: not started
|
||||
* start-date: 2025/07/01
|
||||
* end-date: 2025/07/31
|
||||
|
||||
#### Description
|
||||
|
||||
Run a learn up session about topic of choice related to smart contract development to present and discuss with the team.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- [ ] Recording of the session
|
||||
|
||||
### SC LearnUp Session 2025/08
|
||||
|
||||
* fully qualified name: `2025q3-sc-learnup-sessions:2025-08`
|
||||
* owner: r4bbit
|
||||
* status: not started
|
||||
* start-date: 2025/08/01
|
||||
* end-date: 2025/08/31
|
||||
|
||||
#### Description
|
||||
|
||||
Run a learn up session about topic of choice related to smart contract development to present and discuss with the team.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- [ ] Recording of the session
|
||||
|
||||
### SC LearnUp Session 2025/09
|
||||
|
||||
* fully qualified name: `2025q3-sc-learnup-sessions:2025-09`
|
||||
* owner: r4bbit
|
||||
* status: not started
|
||||
* start-date: 2025/09/01
|
||||
* end-date: 2025/09/30
|
||||
|
||||
#### Description
|
||||
|
||||
Run a learn up session about topic of choice related to smart contract development to present and discuss with the team.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- [ ] Recording of the session
|
||||
|
||||
29
content/sc/ift/2025q3-security-audits.md
Normal file
29
content/sc/ift/2025q3-security-audits.md
Normal file
@@ -0,0 +1,29 @@
|
||||
---
|
||||
title: Security Audits
|
||||
tags:
|
||||
- "2025q3"
|
||||
- "sc"
|
||||
- "ift"
|
||||
draft: false
|
||||
description: Participating in security audit contests to get better at building secure applications.
|
||||
---
|
||||
|
||||
`vac:sc:ift:2025q3-security-audits`
|
||||
|
||||
Participating in security audit contests to get better at building secure applications.
|
||||
|
||||
## Description
|
||||
|
||||
In the long-term,
|
||||
we want to be able to conduct security audits in-house for both,
|
||||
IFT projects and third-party projects.
|
||||
To get there,
|
||||
we need to practice and learn from the best.
|
||||
We aim for participating in one security audit contest this quarter,
|
||||
if the circumstances allow it.
|
||||
Urgent work related to IFT projects take precedence over this.
|
||||
|
||||
## Task List
|
||||
|
||||
List of security audits and contests the team participated in.
|
||||
|
||||
@@ -5,15 +5,44 @@ tags:
|
||||
- vac
|
||||
---
|
||||
|
||||
|
||||
## Possible commitments for Q4 and beyond
|
||||
|
||||
- Karma token airdrop via ENS name
|
||||
- EIP collaboration with finance (vaults with advanced access control)
|
||||
- SN L2 native bridge yield extension deployment on testnet/mainnet
|
||||
|
||||
|
||||
## 2025q3 `vac:sc:`
|
||||
---
|
||||
|
||||
### `ift:`
|
||||
|
||||
- [ ] [[sc/ift/2025q3-sc-learnup-sessions]]
|
||||
- [ ] [[sc/ift/2025q3-fv-tools-research]]
|
||||
- [ ] [[sc/ift/2025q3-security-audits]]
|
||||
|
||||
### `status:`
|
||||
|
||||
- [ ] [[sc/status/2025q3-consulting]]
|
||||
- [ ] [[sc/status/2025q3-maintaining-status-contracts]]
|
||||
|
||||
### `status-l2:`
|
||||
|
||||
- [ ] [[sc/status-l2/2025q3-native-bridge-eth-yield-management]]
|
||||
- [ ] [[sc/status-l2/2025q3-native-bridge-dai-yield-management]]
|
||||
|
||||
|
||||
## 2025q2 `vac:sc:`
|
||||
---
|
||||
|
||||
### `ift:`
|
||||
|
||||
- [ ] [[sc/ift/2025q2-sc-learnup-sessions]]
|
||||
- [ ] [[sc/ift/2025q2-security-audits]]
|
||||
- [ ] [[sc/ift/2025q2-fv-tools-research]]
|
||||
|
||||
### `status:`
|
||||
|
||||
- [ ] [[sc/status/2025q2-sn-native-bridge-yield-bearing-module]]
|
||||
- [ ] [[sc/status/2025q2-sn-native-dex]]
|
||||
- [ ] [[sc/status/2025q2-maintaining-status-contracts]]
|
||||
|
||||
@@ -0,0 +1,56 @@
|
||||
---
|
||||
title: SN L2 Bridge DAI Yield Management
|
||||
tags:
|
||||
- "2025q3"
|
||||
- "sc"
|
||||
- "status-l2"
|
||||
draft: false
|
||||
description: Implement yield generation in the Status Network native bridge for bridged DAI.
|
||||
---
|
||||
|
||||
`vac:sc:status-l2:2025q3-native-bridge-dai-yield-management`
|
||||
|
||||
Implement yield generation in the Status Network native bridge for bridged DAI.
|
||||
|
||||
## Description
|
||||
|
||||
Once ETH yield management is implemented and working,
|
||||
the next step is to implement yield generation for bridged DAI.
|
||||
This commitment is about implementing yield generation for bridged DAI using the DSR module of MakerDAO.
|
||||
|
||||
|
||||
## Task List
|
||||
|
||||
|
||||
### DSR integration
|
||||
* fully qualified name: `2025q3-native-bridge-eth-yield-management:dsr-integration`
|
||||
* owner:
|
||||
* status:
|
||||
* start-date: 2025/07/01
|
||||
* end-date: 2025/07/30
|
||||
|
||||
#### Description
|
||||
|
||||
We've implemented the necessary abstractions and proxies to allow for yield generation in the native bridge.
|
||||
The next step is to integrate the DSR protocol as a yield provider for the bridge.
|
||||
Part of this task is implementing deposits and withdrawals via the bridge.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- [ ] Commits/PRs that implement and integrate the DAI yield provider
|
||||
- [ ] Tests that verify the functionality of the DAI yield provider integration
|
||||
|
||||
### Yield distribution
|
||||
* fully qualified name: `2025q3-native-bridge-dai-yield-management:yield-distribution`
|
||||
* owner:
|
||||
* status:
|
||||
* start-date: 2025/07/01
|
||||
* end-date: 2025/07/30
|
||||
|
||||
#### Description
|
||||
|
||||
Implement the necessary changes to send and distribute the generated yield to the splitter contract on Status Network.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- [ ] Commits/PRs that implement the yield distribution logic
|
||||
@@ -0,0 +1,57 @@
|
||||
---
|
||||
title: SN L2 Bridge ETH Yield Management
|
||||
tags:
|
||||
- "2025q3"
|
||||
- "sc"
|
||||
- "status-l2"
|
||||
draft: false
|
||||
description: Implement yield generation in the Status Network native bridge for bridged ETH.
|
||||
---
|
||||
|
||||
`vac:sc:status-l2:2025q3-native-bridge-eth-yield-management`
|
||||
|
||||
Implement yield generation in the Status Network native bridge for bridged ETH.
|
||||
|
||||
## Description
|
||||
|
||||
After laying the groundwork for yield generation in the Status Network native bridge,
|
||||
the next step is to leverage the existing architecture to implement yield generation for bridged ETH.
|
||||
This commitment is about implementing yield generation for bridged ETH using the Lido protocol.
|
||||
|
||||
|
||||
## Task List
|
||||
|
||||
|
||||
### Lido integration
|
||||
* fully qualified name: `2025q3-native-bridge-eth-yield-management:lido-integration`
|
||||
* owner:
|
||||
* status:
|
||||
* start-date: 2025/07/01
|
||||
* end-date: 2025/07/30
|
||||
|
||||
#### Description
|
||||
|
||||
We've implemented the necessary abstractions and proxies to allow for yield generation in the native bridge.
|
||||
The next step is to integrate the Lido protocol as a yield provider for the bridge.
|
||||
Part of this task is implementing deposits and withdrawals via the bridge.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- [ ] Commits/PRs that implement and integrate the Lido yield provider
|
||||
- [ ] Tests that verify the functionality of the Lido yield provider integration
|
||||
|
||||
### Yield distribution
|
||||
* fully qualified name: `2025q3-native-bridge-eth-yield-management:yield-distribution`
|
||||
* owner:
|
||||
* status:
|
||||
* start-date: 2025/07/01
|
||||
* end-date: 2025/07/30
|
||||
|
||||
#### Description
|
||||
|
||||
Implement the necessary changes to send and distribute the generated yield to a splitter contract on Status Network.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- [ ] Commits/PRs that implement the yield distribution logic
|
||||
|
||||
@@ -31,7 +31,7 @@ another contract has to be deployed that provides the necessary data.
|
||||
|
||||
* fully qualified name: `2025q2-karma-rln:slash-karma`
|
||||
* owner: r4bbit
|
||||
* status: not started
|
||||
* status: done
|
||||
* start-date: 2025/05/21
|
||||
* end-date: 2025/06/31
|
||||
|
||||
@@ -73,7 +73,7 @@ It should also be possible to add new tiers.
|
||||
|
||||
* fully qualified name: `2025q2-karma-rln:implementation`
|
||||
* owner: Ricardo
|
||||
* status: not started
|
||||
* status: 80%
|
||||
* start-date: 2025/05/21
|
||||
* end-date: 2025/06/31
|
||||
|
||||
|
||||
@@ -8,7 +8,7 @@ draft: false
|
||||
description: Maintain and improve existing Status smart contracts as requested.
|
||||
---
|
||||
|
||||
`vac:sc:status:2025q2-sn-native-bridge-yield-bearing-module`
|
||||
`vac:sc:status:2025q2-maintaining-status-contracts`
|
||||
|
||||
Maintain and improve existing Status smart contracts as requested.
|
||||
|
||||
|
||||
@@ -5,18 +5,21 @@ tags:
|
||||
- "sc"
|
||||
- "status"
|
||||
draft: false
|
||||
description: Implementing a yield-bearing module for the Status Network Native Bridge.
|
||||
description: Design and implement architecture to enable yield generation in the Status Network native bridge.
|
||||
---
|
||||
|
||||
`vac:sc:status:2025q2-sn-native-bridge-yield-bearing-module`
|
||||
|
||||
Implementing a yield-bearing module for the Status Network Native Bridge.
|
||||
Design and implement architecture to enable yield generation in the Status Network native bridge.
|
||||
|
||||
## Description
|
||||
|
||||
The native bridge of Status Network needs to be extended by a module that allows for generating yield on the bridged assets.
|
||||
The general idea is that users lock their assets in the L1 bridge contract and the bridge module deposits them to yield-bearing protocols.
|
||||
The yield is regularly harvested and distributed on the L2.
|
||||
The native bridge of Status Network needs to be extended,
|
||||
such that it allows for generating yield on the bridged assets.
|
||||
The general idea is that users lock their assets in the L1 bridge contract and the bridge deposits them to yield-bearing protocols.
|
||||
The yield is then regularly harvested and distributed on the L2.
|
||||
This commitment is about laying the groundwork for this feature,
|
||||
by designing and implementing the necessary interfaces and base contracts.
|
||||
|
||||
## Task List
|
||||
|
||||
@@ -24,65 +27,51 @@ The yield is regularly harvested and distributed on the L2.
|
||||
### Research and Design
|
||||
* fully qualified name: `2025q2-sn-native-bridge-yield-bearing-module:research-design`
|
||||
* owner: r4bbit
|
||||
* status: 60%
|
||||
* status: done
|
||||
* start-date: 2025/04/01
|
||||
* end-date: 2025/04/30
|
||||
|
||||
#### Description
|
||||
|
||||
This task is about researching the existing bridge protocol to get a better understanding of how it works and how the yield-bearing module can be integrated.
|
||||
In addition, we need to discuss with Linea if they want to implement the "modularity" of the bridge themselves,
|
||||
or if that should also be done by us.
|
||||
The goal is to have a clear plan on how to implement the yield-bearing module.
|
||||
This task is about researching the existing bridge protocol to get a better understanding of how it works and how it can and should be extended to allow for yield generation.
|
||||
In addition,
|
||||
we need to collaborate with the Linea team to understand what their requirements are.
|
||||
The goal is to have a clear plan on how to implement the fundamental architecture.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- [ ] Design document explaining how the yield-bearing module will be integrated into the bridge protocol
|
||||
|
||||
### Module implementation
|
||||
### Fundamental Architecture Implementation
|
||||
|
||||
* fully qualified name: `2025q2-sn-native-bridge-yield-bearing-module:implementation`
|
||||
* owner:
|
||||
* status: not started
|
||||
* owner: andrea
|
||||
* status: done
|
||||
* start-date: 2025/05/01
|
||||
* end-date: 2025/05/30
|
||||
|
||||
#### Description
|
||||
|
||||
After we've created a proper plan on how to implement the module extension for the bridge,
|
||||
After we've created a proper plan on how to implement the basic architecture and interfaces,
|
||||
the next step is to actually implement it.
|
||||
Here it's important that the module will be implemented upstream in the linea mono repository.
|
||||
Testing and verification of its functionality is also part of this task and will happen in that repository as well.
|
||||
Testing and verification of its functionality is also part of this task and will happen as the fundamentals are implemented.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- [ ] Yield-bearing module implementation (link to PR in Linea mono repository)
|
||||
- [ ] Implementation of agreed architecture and interfaces for eth bridging
|
||||
|
||||
### Status Networtk Testnet Deployment
|
||||
* fully qualified name: `2025q2-sn-native-bridge-yield-bearing-module:testnet-deployment`
|
||||
* owner:
|
||||
* status: not started
|
||||
### Status Networtk Devnet Deployment
|
||||
* fully qualified name: `2025q2-sn-native-bridge-yield-bearing-module:devnet-deployment`
|
||||
* owner: andrea
|
||||
* status: done
|
||||
* start-date: 2025/06/01
|
||||
* end-date: 2025/06/31
|
||||
|
||||
#### Description
|
||||
|
||||
Once the module is implemented, we will deploy it on the Status Network testnet for further testing.
|
||||
Once the fundamental architecture is implemented, we will deploy it on the Status Network devnet for further testing.
|
||||
We should spend a significant amount of time testing the module with other team members to ensure that it works as expected.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- [ ] Deployment of the module on Status Network testnet
|
||||
|
||||
### Status Networtk Mainnet Deployment
|
||||
* fully qualified name: `2025q2-sn-native-bridge-yield-bearing-module:mainnet-deployment`
|
||||
* owner:
|
||||
* status: not started
|
||||
* start-date: 2025/06/31
|
||||
* end-date: 2025/06/31
|
||||
|
||||
#### Description
|
||||
|
||||
After successful testing on the testnet, we will deploy the yield-bearing module on the Status Network mainnet.
|
||||
|
||||
- [ ] Deployment of the module on Status Network mainnet
|
||||
- [ ] Deployment of base architecture on Status Network devnet
|
||||
|
||||
@@ -12,6 +12,9 @@ description: Implementing a native DEX for the Status Network.
|
||||
|
||||
Implementing a native DEX for the Status Network.
|
||||
|
||||
**This commitment has been removed. The Status Network team has decided to outsource the work to a 3rd party team.**
|
||||
|
||||
|
||||
## Description
|
||||
|
||||
The Status Network needs a decentralized exchange (DEX) to allow users to trade tokens in a trustless manner.
|
||||
|
||||
33
content/sc/status/2025q3-maintaining-status-contracts.md
Normal file
33
content/sc/status/2025q3-maintaining-status-contracts.md
Normal file
@@ -0,0 +1,33 @@
|
||||
---
|
||||
title: Maintainin existing Status smart contracts
|
||||
tags:
|
||||
- "2025q3"
|
||||
- "sc"
|
||||
- "status"
|
||||
draft: false
|
||||
description: Maintain and improve existing Status smart contracts as requested.
|
||||
---
|
||||
|
||||
`vac:sc:status:2025q3-maintaining-status-contracts`
|
||||
|
||||
Maintain and improve existing Status smart contracts as requested.
|
||||
|
||||
## Description
|
||||
|
||||
Smart contracts for Status that have already been implemented and deployed might still need maintenance.
|
||||
This includes upgrading systems or fixing bugs that might be discovered after the contracts have been deployed.
|
||||
|
||||
The Smart Contracts team commits to providing maintenance service for existing smart contracts,
|
||||
such as:
|
||||
|
||||
- Status ENS
|
||||
- Status Communities Contracts
|
||||
- Status Staking Protocol
|
||||
- Status Voting DApp
|
||||
|
||||
## Task List
|
||||
|
||||
There are no concrete tasks associated to this commitment.
|
||||
As requests come in,
|
||||
they will be addressed by our team.
|
||||
|
||||
22
content/sc/status/2025q3-status-consulting.md
Normal file
22
content/sc/status/2025q3-status-consulting.md
Normal file
@@ -0,0 +1,22 @@
|
||||
---
|
||||
title: Status Smart Contracts Consulting
|
||||
tags:
|
||||
- "2025q3"
|
||||
- "sc"
|
||||
- "status"
|
||||
draft: false
|
||||
description: Provide input and feedback related to smart contract solutions.
|
||||
---
|
||||
|
||||
`vac:sc:status:2025q3-status-consulting`
|
||||
|
||||
Provide input and feedback related to smart contract solutions.
|
||||
|
||||
## Description
|
||||
|
||||
The Smart Contracts team will provide consulting services to the Status team on various topics related to smart contract development.
|
||||
|
||||
## Task List
|
||||
|
||||
There are no concrete tasks associated to this commitment.
|
||||
|
||||
@@ -75,6 +75,34 @@ draft: false
|
||||
- 1 CC 1d off
|
||||
|
||||
### vac:tke:
|
||||
- `vac:tke:ift:support-to-ift-units::logos-basket`
|
||||
- reviewed other $LOGOS token proposals
|
||||
- addressed team feedback about current proposal
|
||||
- met with stakeholders and discuss proposals
|
||||
- Review the work of J&F and add own ideas/comments
|
||||
- work basket and joint value accrual
|
||||
- `vac:tke:ift:support-to-ift-units::tge`
|
||||
- reviewed and commented on the proposed documents
|
||||
- `vac:tke:codex:cdx-launch::preparations`
|
||||
- discussed our token model with Rahul
|
||||
- proposeed a token emission schedule based on a KPI
|
||||
- met with Codex team to discuss
|
||||
- Prepare a proposal/ideas for incentivized testnet for Thu call with Codex
|
||||
- help on token emission schedule based on a KPI
|
||||
- `vac:tke:nomos:macroeconomy::block-rewards`
|
||||
- implemented a dashboard that produces the token emission schedule given any number of KPIs
|
||||
- `vac:tke:nomos:macroeconomy::revision-economic-model`
|
||||
- addressed feedback in the Stake Estimation doc
|
||||
- `vac:tke:ift:tokenomics-research-forum:grantico`
|
||||
- Look into the grant schemes discussed at EthPrague
|
||||
- `vac:tke:status:karma-incentives:karma-params`
|
||||
- Catch up with the bridge progress
|
||||
- Start modeling Karma onboarding flow and leveling up
|
||||
- Work on getting data analysis of priority fees
|
||||
- `vac:tke:nomos:macroeconomy::tfms-primer`
|
||||
- Push on tasks related to nomos DA, TFMs and block rewards
|
||||
- `vac:tke:ift:tokenomics-research-forum::minting-control`
|
||||
- Keep refining work on optimal control and minting
|
||||
|
||||
### vac:qa:
|
||||
- `status:2025q2-status-qa:v2-34`
|
||||
@@ -257,4 +285,17 @@ draft: false
|
||||
- Removed users from Github, Discord and Notion
|
||||
|
||||
### vac:nes:
|
||||
- `state-separation-architecture-poc:hybrid`
|
||||
- Quick overview of Ethereum account model to fit within NSSA.
|
||||
- Continued [drafting ideas](https://www.notion.so/Brainstorming-adaptation-of-Solana-s-model-to-NSSA-2028f96fb65c80cbb99fe978c2957758) on how Solana's model could be adapted to support a companion private state and hybrid executions. Described potential ways to adapt the functions that would be needed for a private version of the hello world example.
|
||||
- Delved deeper into the Solana codebase to understand inner workings and where some consistency checks are performed.
|
||||
- `state-separation-architecture-poc:sc-utility`
|
||||
- PR reviews
|
||||
- Autogen template work [PR](https://github.com/vacp2p/nescience-testnet/pull/84)
|
||||
- Implemented autogeneration template. [Merge request](https://github.com/vacp2p/nescience-testnet/pull/83)
|
||||
- `acz:t2`
|
||||
- Delivered SE/DE optimization document.
|
||||
- `acz:t3`
|
||||
- Began work on [light user support analysis](https://www.notion.so/nes-2025q2-nescience-consulting-light-users-2068f96fb65c802db086d6981a50e71f). Outline security and privacy concerns, investigate light user support in other projects.
|
||||
- Detected an [inflation exploit](https://www.notion.so/Inflation-exploit-and-mitigation-20a8f96fb65c80fdbc77ff02b681f70f) in current UTXO
|
||||
|
||||
|
||||
266
content/updates/2025-06-16.md
Normal file
266
content/updates/2025-06-16.md
Normal file
@@ -0,0 +1,266 @@
|
||||
---
|
||||
title: "2025-06-16 Vac weekly"
|
||||
tags:
|
||||
- "vac-updates"
|
||||
date: 2025-06-16
|
||||
lastmod: 2025-06-16
|
||||
draft: false
|
||||
---
|
||||
|
||||
## Vac 2025/06/16
|
||||
|
||||
### highlights
|
||||
|
||||
### vac:p2p:
|
||||
- `ift:2025q1-gossipsub-perf-improvements`
|
||||
- Worked on performance comparison blogpost. Results are complete, doing writeup
|
||||
- Worked on GossipSub v1.4 production implementation.
|
||||
- Started working on Message rotation/Stream prioritization.
|
||||
- Did some study for possible proposals
|
||||
- Used some time for libp2p specs
|
||||
- `vac:p2p:ift:2025q2-nimlibp2p-kad-dht`
|
||||
- Splitted part of the current state of code into separate PRs for easy reviewal:
|
||||
- [nim-libp2p#1453](https://github.com/vacp2p/nim-libp2p/pull/1453) feat(kad-dht): protobuffers
|
||||
- [nim-libp2p#1454](https://github.com/vacp2p/nim-libp2p/pull/1454) feat(kad-dht): routing table
|
||||
- [nim-libp2p#1455](https://github.com/vacp2p/nim-libp2p/pull/1455) feat(kad-dht): handler
|
||||
- `vac:p2p:acz:2025q2-acz-consulting:libp2p-mix-consulting`
|
||||
- Troubleshoot with Akshaya reasons behind CI failing on [nim-libp2p#1420](https://github.com/vacp2p/nim-libp2p/pull/1420)
|
||||
- Discussed with Ben how to make his workflow more efficient, suggested to not use docker since it adds an unnecesary delay between writing code and running the code
|
||||
- Troubleshoot why there was a PeerID mismatch when running mix PoC
|
||||
- `vac:p2p:ift:2025q2-gossipsub-perf-improvements`
|
||||
- Discussed with Farooq work pending for Gossipsub 1.4
|
||||
- Fixed minor compilation problem on tests and applied formatting to PR to get CI to pass
|
||||
- Started working on calculating peer bandwidth and making the preamble sending depend on meeting a msg size condition.
|
||||
- `vac:p2p:ift:2025q2-nimlibp2p-maintenance:maintenance`
|
||||
- Investigated the reason behind this issue https://github.com/vacp2p/nim-libp2p/issues/1462 , with the problem being that we do not handle half open states correctly in yamux. Should we work on this?
|
||||
- finalizing nim perf benchamrking
|
||||
- feat(perf): add stats [nim-libp2p#1452](https://github.com/vacp2p/nim-libp2p/pull/1452)
|
||||
- updated perf benchamrking impl [test-plans#659](https://github.com/libp2p/test-plans/pull/659)
|
||||
- added intermediary stats
|
||||
- various improvments
|
||||
- `vac:p2p:ift:2025q2-nimlibp2p-autotls`
|
||||
- PeerIDAuthClient ([nim-libp2p#1445](https://github.com/vacp2p/nim-libp2p/pull/1445))
|
||||
- MockACMEApi ([nim-libp2p#1457](https://github.com/vacp2p/nim-libp2p/pull/1457))
|
||||
- Mock PeerIDAuthClient ([nim-libp2p#1458](https://github.com/vacp2p/nim-libp2p/pull/1458))
|
||||
|
||||
### vac:tke:
|
||||
- `admin`
|
||||
- 2 CC days off
|
||||
- discuss internally how we can plug in the community or do mentoring for them
|
||||
- reach out to interested community members
|
||||
- `vac:tke:codex:cdx-launch::preparations`
|
||||
- reviewed the incentivized testnet proposals
|
||||
- `vac:tke:nomos:macroeconomy::block-rewards`
|
||||
- implemented a generic dashboard for KPI-based token emissions
|
||||
- decided which KPIs and target values, if any, should feed the token emission schedule
|
||||
- implementd the proposed emission schedule and calibrate it
|
||||
- `vac:tke:ift:support-to-ift-units::logos-basket`
|
||||
- further study Helium model and explore new models
|
||||
- Further work basket and joint value accrual
|
||||
- `vac:tke:ift:tokenomics-research-forum:grantico`
|
||||
- Revisit the paper and the alignment formula
|
||||
- `vac:tke:status:karma-incentives:karma-params`
|
||||
- Monitoring the bridge progress
|
||||
- Continue modeling Karma onboarding flow and leveling up
|
||||
- `vac:tke:catsfishing:ad-hoc`
|
||||
- Worked on doc for metaplex
|
||||
- Revised of inheritance doc
|
||||
- Met with Matt and Ned to discuss Inheritance doc
|
||||
- Started working on follow-up tasks for it (simulations and mechanisms)
|
||||
- `vac:tke:nomos:macroeconomy::tfms-primer`
|
||||
- Finished initial nomos DA doc
|
||||
- Started working toward final specification of NomosDA and block rewards
|
||||
- `vac:tke:ift:tokenomics-research-forum::minting-control`
|
||||
- Kept refining work on optimal control and minting
|
||||
|
||||
### vac:qa:
|
||||
- `waku:2025q2-interop-testing:maintenance`
|
||||
- Raised issue related to [relay fetch](https://github.com/waku-org/nwaku/issues/3444)
|
||||
- Fixed failing [tests](https://github.com/waku-org/waku-interop-tests/pull/121)
|
||||
- bug: node won't start with RLN in on-chain dynamic mode 2
|
||||
[Issue 3208 - closed](https://github.com/waku-org/nwaku/issues/3208)
|
||||
- `ift:2025q2-qa-rfc-sync-waku:nwaku`
|
||||
- Started working on the store protocol
|
||||
- `nomos:2025q2-da-testing:dispersal-resilience`
|
||||
- chore: Nomos node with mutated DA transport
|
||||
[PR 2 - in progress](https://github.com/logos-co/nomos-security-tests/pull/2)
|
||||
- Test/dispersal resilience
|
||||
[PR 19 - in progress](https://github.com/logos-co/nomos-e2e-tests/pull/19) - using test bed from [nomos-security-tests](https://github.com/logos-co/nomos-security-tests)
|
||||
- `vac:2025q2-nim-libp2p-testing:gossipsub-extended-part3`
|
||||
- [test(gossipsub): flaky tests](https://github.com/vacp2p/nim-libp2p/pull/1451) - merged
|
||||
- [test: increase timeout](https://github.com/vacp2p/nim-libp2p/pull/1460) - merged
|
||||
- [test(gossipsub): refactor and unify scoring tests](https://github.com/vacp2p/nim-libp2p/pull/1461) - merged
|
||||
- [test(gossipsub): GossipThreshold and PublishThreshold tests](https://github.com/vacp2p/nim-libp2p/pull/1464) - in review
|
||||
- `status:2025q2-status-qa:v2-34`
|
||||
- Tested fix of 2 blockers
|
||||
- Tested new feature required for 2.34
|
||||
- Lambda emulators handoff initiated
|
||||
- Tested a fix for [https://github.com/status-im/status-desktop/issues/18063](https://github.com/status-im/status-desktop/issues/18063)
|
||||
- Continued Qt6 app tests [https://github.com/status-im/status-desktop/pull/18019](https://github.com/status-im/status-desktop/pull/18019)
|
||||
- Reviewed shell feature [PR 17916](https://github.com/status-im/status-desktop/pull/17916)
|
||||
- Worked on PR adding shell to Squish (resolved local Python issues)
|
||||
- Participated in Q3 strategy discussions and drafts
|
||||
- `admin/misc`
|
||||
- Prepared estimations for Keycard testing
|
||||
- Planned and drafted [Q3 commitments](https://github.com/vacp2p/roadmap/pull/184)
|
||||
- OOO: 9 CC days
|
||||
|
||||
### vac:dst:
|
||||
- `admin/misc`
|
||||
- Read new Waku FURPS and update Q3 commitments: [Github PR](https://github.com/vacp2p/roadmap/pull/175)
|
||||
- Started reading and building js-waku docker image to provide feedback to js-waku team
|
||||
- `vac:dst:vac:2025q2-libp2p-evaluation:mix-gossipsub`
|
||||
- Small issues with mix
|
||||
- Requested changes to ACZ since logging was not correct in last commit (Tuesday)
|
||||
- Assist ACZ with running mix locally, also explain the problem
|
||||
- New Issue reported by ACZ
|
||||
- `vac:dst:status:2025q2-status-go-evaluation:store-performance`
|
||||
- Reproduced same light-node/community issue with updated devel branch.
|
||||
- Run locally tests to try to reproduce issue
|
||||
- Call with QA, found bug in one test.
|
||||
- Were able to run locally tests, digging into what are the differences with K8s.
|
||||
- `vac:dst:vac:2025q2-libp2p-evaluation:regression-testing`
|
||||
- Started experiments for nimlibp2p 1.11.0
|
||||
- Issues with cephfs pvc (Monday) in the lab, changed to `moosefs-storage`.
|
||||
- Issues with Dockerhub credentials, docker images were ratelimited for big deployments (1K). Requested Friday 6th, applied Thusday.
|
||||
- Thursday night experiments were cancelled because of internet outage. Dockerhub was returning 500 error when pulling containers.
|
||||
- Issues with data scrapping in experiments. Debugged to check if it was a nimlibp2p issue, internet issue again, or lab issue.
|
||||
- Debugged and discussed. Lab was having inestabilities because of NVMes that were full.
|
||||
- Discussed changes that needed to be done in Sapphire. Will be done over the weekend and experiments will be re-deployed on Sunday.
|
||||
- Added namespace to Prometheus scraping, we can now filter by experiments namespace, so deployments data should not interfiere with others when scraping.
|
||||
- `vac:dst:ift:2025q2-dst-tooling:adapt-experiments`
|
||||
- [Draft Github PR #70](https://github.com/vacp2p/10ksim/pull/70)
|
||||
- Refactored and reorganized
|
||||
- Minimal working example of new refactor
|
||||
- Solved issue with bootstrap nodes [Notes](https://notes.status.im/s/uBCNOLmfs)
|
||||
- Fixed a lot of other template issues.
|
||||
|
||||
### vac:sc:
|
||||
- `status:2025q2-sn-native-bridge-yield-bearing-module:research-design`
|
||||
- created new PR adding L2YieldMessageService https://github.com/vacp2p/linea-monorepo/pull/21
|
||||
- started looking at the new changes on the main Linea repo to see what to change in our PRs
|
||||
- `status:2025q2-karma-rln:implementation`
|
||||
- Finalized 221/220 (became 223) https://github.com/vacp2p/staking-reward-streamer/pull/223
|
||||
|
||||
### vac:acz:
|
||||
- `ift:2025q2-libp2p-mix-testnet:update-rfc`
|
||||
- Added Section 5.4 and Section 8 to the [PR](https://github.com/vacp2p/rfc-index/pull/158) [WiP].
|
||||
- `ift:2025q2-libp2p-mix-testnet:solve-discrepancy`
|
||||
- Updated branches [dst-changes](https://github.com/vacp2p/dst-gossipsub-test-node/tree/dst-changes) and [tmp/benchmark-logging](https://github.com/vacp2p/mix/tree/tmp/benchmark-logging), both are now ready for benchmarking.
|
||||
- Participated in detailed syncs with Ben and DST (in group) to align on the exit discrepancy task; clarified next steps.
|
||||
- PR [PR #1420](https://github.com/vacp2p/nim-libp2p/pull/1420):
|
||||
- Fixed test issues related to custom connection logic.
|
||||
- Merged changes to master.
|
||||
- Reverted, feature-flagged logging system [PR 25](https://github.com/vacp2p/mix/pull/25) due to weirdness
|
||||
- Significant issues stemming from docker. [Resolved](https://github.com/vacp2p/mix/tree/de_docker) through running sims directly
|
||||
- Identified a key suspect in the source of the issue, detailed in [github comment](https://github.com/vacp2p/mix/issues/24#issuecomment-2975656725)
|
||||
- `ift:2025q2-de-mls-tesnet:commit-and-proposal`
|
||||
- Mostly finished splitting commit message [branch](https://github.com/vacp2p/de-mls/tree/feat_extract_proposal)
|
||||
|
||||
- `nes:2025q2-nescience-consulting:light-users`
|
||||
- Finished [light user support document](https://www.notion.so/nes-2025q2-nescience-consulting-light-users-2068f96fb65c802db086d6981a50e71f) for NSSA.
|
||||
- `nomos:2025q2-nomos-consulting:zk-consulting-nomos-2`
|
||||
- Finished review of [relative stake document](https://www.notion.so/nomos-tech/Preliminary-Research-Impact-of-the-Service-Declaration-Protocol-on-the-statistical-inference-of-rel-206261aa09df807bad8afccf8474c6c9#209261aa09df803d9e07f14c76435c45).
|
||||
- `nes:2025q2-nescience-consulting:viewing-keys`
|
||||
- Worked through the mathematical construction and design of [Zcash's viewing keys](https://zips.z.cash/protocol/protocol.pdf) for Sprout and Sapling.
|
||||
- Began compiling a list of ECs to investigate.
|
||||
- `ift:2025q2-rln-status-l2:rpc-node-modification`
|
||||
- Reviewed the implementation idea from Nadeem on the RPC modification task [(PR)](https://github.com/vacp2p/status-linea-besu/pull/2)
|
||||
- Built the Docker image for the end-to-end test
|
||||
|
||||
- `ift:2025q2-de-mls-tesnet:blogpost-de-mls-over-waku`
|
||||
- Address feedback on the [PR](https://github.com/vacp2p/vac.dev/pull/159).
|
||||
- `ift:2025q2-rln-status-l2:prover-service`
|
||||
- [Zerokit v0.8.0 integration](https://github.com/vacp2p/status-rln-prover/pull/6) - merged
|
||||
- [Smart contract reorg + Tier info SC integration](https://github.com/vacp2p/status-rln-prover/pull/7) - merged
|
||||
- [Prover + Docker](https://github.com/vacp2p/status-rln-prover/pull/8) - merged
|
||||
- [Unit tests fixes](https://github.com/vacp2p/status-rln-prover/pull/9)
|
||||
- `ift:2025q2-zerokit:zerokit-maintaining`
|
||||
- Keygen + BE functions for Zerokit base on this discussion
|
||||
- [PR](https://github.com/vacp2p/zerokit/pull/318)
|
||||
- Zeroize for functions compute_id_secret & keygen functions
|
||||
- [PR](https://github.com/vacp2p/zerokit/pull/319)
|
||||
- `ift:2025q2-libp2p-mix-testnet:solve-discrepancy`
|
||||
- Reverted, feature-flagged logging system [PR 25](https://github.com/vacp2p/mix/pull/25) due to weirdness
|
||||
- Significant issues stemming from docker. Resolved through running sims directly [issues](https://github.com/nim-lang/nimble/issues/1403)
|
||||
- `ift:2025q2-zerokit:perfomance-updates-blogpost`
|
||||
- Recieved input from [Issue 314](https://github.com/vacp2p/zerokit/issues/314)
|
||||
|
||||
- `admin/misc`
|
||||
- 1 cc was ooo for 2 days (bank holiday)
|
||||
- Reopened a new [issue](https://github.com/RReverser/wasm-bindgen-rayon/issues/26) regarding the multithread test in wasm-bindgen-rayon repo
|
||||
|
||||
### vac:nim:
|
||||
- `ift:2025q1-nimble`
|
||||
- (VNext supports develop) vNext develop CI green https://github.com/nim-lang/nimble/pull/1402
|
||||
- WIP vnext default to pass CI https://github.com/nim-lang/nimble/pull/1406
|
||||
- Fix regression
|
||||
- Removes unused import
|
||||
- develop progress: handles reverse deps for develop
|
||||
- Fixes an issue where babel root packages failed to install. `uninstall ci` green
|
||||
- tlocal green
|
||||
- Declarative parser by default (enables vnext)
|
||||
- Fixes a rebas- `state-separation-architecture-poc:hybrid`
|
||||
- Continued working on adapting Ethereum account based model into NSSA. Beside adding related specifications about Ethereum, worked on providing ways to integrate private, SE, and DE executions process.
|
||||
- Presented some ideas for Q3 research tasks at the NSSA Research <> ACZ brainstorming meeting ([slides](https://docs.google.com/presentation/d/1QPo7oXnHaDW_4zsvWCmF-5mVITxnRzcqJBQYJUKQ3hw/edit?slide=id.g360faad10fd_0_6#slide=id.g360faad10fd_0_6)).
|
||||
- Presented a lean dev approach proposal for Q3 (and Q4) at the team planning ([slides](https://docs.google.com/presentation/d/1xam3iBaOdiRFZdIlXRVo5adEga0ab-B5sG1RiT2_bHM/edit?slide=id.g360faad10fd_0_6#slide=id.g360faad10fd_0_6)).
|
||||
- Worked with Moudy on concrete research tasks for Q3 (see [here](https://www.notion.so/Q3-complete-tasks-20e8f96fb65c803c91ddfa15fccd8bc1?source=copy_link#2108f96fb65c80719f68d3e5414f4594)).
|
||||
- Continued working on adapting Solana's model to NSSA ([here](https://www.notion.so/Brainstorming-adaptation-of-Solana-s-model-to-NSSA-2028f96fb65c80cbb99fe978c2957758)). Drafted a possible workaround for the team's concerns about runtime selective privacy. Cleaned up the doc and went over what I'd written so far to check it makes sense.
|
||||
- Finished light user support [document](https://www.notion.so/Light-user-support-in-NSSA-2108f96fb65c8031b2f8d651721f7c84). Provided a list of additional work that needs to be done for private and DE transactions to determine feasibility of the two possibilities. Due to lack of documentation and benchmarks targeting mobile devices, proof generation has to be tested.
|
||||
- Delivered [T3](https://www.notion.so/nes-2025q2-nescience-consulting-light-users-2068f96fb65c802db086d6981a50e71f)
|
||||
|
||||
- `state-separation-architecture-poc:node-stability`
|
||||
- Reviewed the new changes to PR #82 and left some [additional comments](https://github.com/vacp2p/nescience-testnet/pull/82#pullrequestreview-2926774114) on it.
|
||||
|
||||
- `state-separation-architecture-poc:sc-utility`
|
||||
- Added testing and serialization bug fix for PR#82
|
||||
- Prepared question for research on selective privacy model [link](https://www.notion.so/Presentation-document-engineering-questions-and-comments-20e8f96fb65c807baa13cca59f5e647f?source=copy_link)e issue and disables vnext
|
||||
- Removes unusued import. Adds debug logging
|
||||
- Enables vnext
|
||||
- Only MacOs tests
|
||||
- Fix develop regression
|
||||
- Fixes test
|
||||
- Prompt to refresh the package list in vnext when it cant found a package
|
||||
- Fixes tlocal. Disables lock and issues to remove noise
|
||||
- Disables lock and issues
|
||||
- FIxes an issue with develop
|
||||
- picks #head when looking for packages
|
||||
- Adds support for `noRebuild`
|
||||
- Adds support for submodules in vnext
|
||||
|
||||
### vac:rfc:
|
||||
- `vac:rfc:nomos:2025q2-rfc-iteration`
|
||||
- Pushed changes to all 3 Nomos open PRs and made them "Ready for Review".
|
||||
|
||||
### vac:sec:
|
||||
- `ift:2025q2-signatory-registry-implementation:signatory-vault-deployment`
|
||||
- Started adding verified signatory data into the secure vault
|
||||
- `ift:2025q2-signatory-registry-implementation:signatory-data-verification`
|
||||
- Continued the collection of signatory information
|
||||
- `ift:2025q2-audit-plan-refinement:smart-contract-testing`
|
||||
- Collaborated with the Codex engineering team to review recent Vault optimizations for hidden risks.
|
||||
- `ift:2025q2-security-automation: POC for app catalogue update from Expensify`
|
||||
- Fixed list of fields for App Catalogue, considering incoming data from Expensify
|
||||
- `ift:2025q2-iam-operations:remove-unnecessary-users`
|
||||
- Continued the validation of access to critical applications (offboarding)
|
||||
- Investigated and explored how to remove access in GH, Google and Discord via API
|
||||
- `ift:2025q2-security-automation: POC for app catalogue update from Expensify`
|
||||
- Finalized production version of App Catalogue update process
|
||||
|
||||
### vac:nes:
|
||||
- `state-separation-architecture-poc:hybrid`
|
||||
- Continued working on adapting Ethereum account based model into NSSA. Beside adding related specifications about Ethereum, worked on providing ways to integrate private, SE, and DE executions process.
|
||||
- Presented some ideas for Q3 research tasks at the NSSA Research <> ACZ brainstorming meeting ([slides](https://docs.google.com/presentation/d/1QPo7oXnHaDW_4zsvWCmF-5mVITxnRzcqJBQYJUKQ3hw/edit?slide=id.g360faad10fd_0_6#slide=id.g360faad10fd_0_6)).
|
||||
- Presented a lean dev approach proposal for Q3 (and Q4) at the team planning ([slides](https://docs.google.com/presentation/d/1xam3iBaOdiRFZdIlXRVo5adEga0ab-B5sG1RiT2_bHM/edit?slide=id.g360faad10fd_0_6#slide=id.g360faad10fd_0_6)).
|
||||
- Worked with Moudy on concrete research tasks for Q3 (see [here](https://www.notion.so/Q3-complete-tasks-20e8f96fb65c803c91ddfa15fccd8bc1?source=copy_link#2108f96fb65c80719f68d3e5414f4594)).
|
||||
- Continued working on adapting Solana's model to NSSA ([here](https://www.notion.so/Brainstorming-adaptation-of-Solana-s-model-to-NSSA-2028f96fb65c80cbb99fe978c2957758)). Drafted a possible workaround for the team's concerns about runtime selective privacy. Cleaned up the doc and went over what I'd written so far to check it makes sense.
|
||||
- Finished light user support [document](https://www.notion.so/Light-user-support-in-NSSA-2108f96fb65c8031b2f8d651721f7c84). Provided a list of additional work that needs to be done for private and DE transactions to determine feasibility of the two possibilities. Due to lack of documentation and benchmarks targeting mobile devices, proof generation has to be tested.
|
||||
- Delivered [T3](https://www.notion.so/nes-2025q2-nescience-consulting-light-users-2068f96fb65c802db086d6981a50e71f)
|
||||
|
||||
- `state-separation-architecture-poc:node-stability`
|
||||
- Reviewed the new changes to PR #82 and left some [additional comments](https://github.com/vacp2p/nescience-testnet/pull/82#pullrequestreview-2926774114) on it.
|
||||
|
||||
- `state-separation-architecture-poc:sc-utility`
|
||||
- Added testing and serialization bug fix for PR#82
|
||||
- Prepared question for research on selective privacy model [link](https://www.notion.so/Presentation-document-engineering-questions-and-comments-20e8f96fb65c807baa13cca59f5e647f?source=copy_link)
|
||||
|
||||
295
content/updates/2025-06-23.md
Normal file
295
content/updates/2025-06-23.md
Normal file
@@ -0,0 +1,295 @@
|
||||
---
|
||||
title: "2025-06-23 Vac weekly"
|
||||
tags:
|
||||
- "vac-updates"
|
||||
date: 2025-06-23
|
||||
lastmod: 2025-06-23
|
||||
draft: false
|
||||
---
|
||||
|
||||
## Vac 2025/06/23
|
||||
|
||||
### highlights
|
||||
- nim-libp2p: Fixed yamux session close so streams are closed instead of reset
|
||||
- dst: Reproduced bug in mix implementation, notified developers
|
||||
- dst: confirmed IDONTWANT fixes have no negative effect on nimlibp2p performance
|
||||
- Rebased our work on the Status Network Yield Bridge contracts on top of the latest changes of the upstream the Linea repo.
|
||||
|
||||
### vac:p2p:
|
||||
- `ift:2025q1-gossipsub-perf-improvements`
|
||||
- Worked on performance comparison blogpost. Will try to complete the first draft today
|
||||
- [nim-libp2p#1488](https://github.com/vacp2p/nim-libp2p/pull/1448) feat: GossipSub 1.4
|
||||
- Worked on production implementation:
|
||||
- Added logic to store the preambles both in a table and a minheap to make it easier to retrieve expired preambles
|
||||
- Keep track of list of peers who could receive an IWANT to query for missing messages
|
||||
- Fixed some TODOs
|
||||
- Worked on Message rotation/Stream prioritization.
|
||||
- `vac:p2p:ift:2025q2-nimlibp2p-maintenance:maintenance`
|
||||
- Session with DST to help with the setup to be able to use the lab for quic tests as well as giving a walkthrough on how to prepare tese tests.
|
||||
- [nim-libp2p#1466](https://github.com/vacp2p/nim-libp2p/pull/1466) fix(yamux): force close of streams instead of reset when closing connections
|
||||
- Prepared release v1.11.0 of nim-libp2p (requires approval from @Ksr to publish)
|
||||
- `vac:p2p:acz:2025q2-acz-consulting:libp2p-mix-consulting`
|
||||
- Answered queries related to how Libp2p / Gossipsub works
|
||||
- Technical discussion with ACZ CC regarding modifying Mix / Gossipsub with the idea of decoupling it more from mix by having new functions that could be used to obtain the serialized RPC `Message` and another function that could be used by an exit node to broadcast the serialized message.
|
||||
- Went over mix repository and gave suggestions to ACZ on things that could be improved in code
|
||||
- `vac:p2p:ift:2025q2-nimlibp2p-autotls
|
||||
- `vac:p2p:ift:2025q2-nimlibp2p-autotls:notify-challenge-completion`, `vac:p2p:ift:2025q2-nimlibp2p-autotls:finalize-cert`
|
||||
- ACME Client [nim-libp2p#1470](https://github.com/vacp2p/nim-libp2p/pull/1470)
|
||||
- `vac:p2p:ift:2025q2-nimlibp2p-autotls:notify-autotls-broker`, `vac:p2p:ift:2025q2-nimlibp2p-autotls:cert-renewal`
|
||||
- AutoTLS Manager [nim-libp2p#1472](https://github.com/vacp2p/nim-libp2p/pull/1472) (relies on ACME Client so we can only merge that after ACME Client)
|
||||
- `misc/admin`
|
||||
- [roadmap#191](https://github.com/vacp2p/roadmap/pull/191) Described P2P commitments for Q3
|
||||
- 8 CC days off
|
||||
|
||||
### vac:tke:
|
||||
- `admin`
|
||||
- 1 day off
|
||||
- prepared for the TKE Retrospective Q2
|
||||
- `vac:tke:ift:support-to-ift-units::logos-basket`
|
||||
- reviewed Martin's proposal
|
||||
- simplified the proposal of a single token
|
||||
- reviewed all options, researching new and preparing for the meeting
|
||||
- further work basket and joint value accrual
|
||||
- `vac:tke:codex:cdx-launch::preparations`
|
||||
- Read proposals
|
||||
- met the Codex team to discuss the incentivized testnet
|
||||
- `vac:tke:nomos:macroeconomy::block-rewards`
|
||||
- analysed the block rewards work as sketched in the spec
|
||||
- met with Nomos to discuss tx fee mechanisms
|
||||
- `vac:tke:status:karma-incentives:karma-params`
|
||||
- calculations and system design based on anchored tier shortcuts
|
||||
- `vac:tke:catsfishing:ad-hoc`
|
||||
- Work on follow-up tasks for it (simulations and mechanisms)
|
||||
- Meet with Ned and Matt to disucss above
|
||||
- Meet with Ned re: tasks for Ghosts
|
||||
- `vac:tke:nomos:macroeconomy::tfms-primer`
|
||||
- reviewed Juan's docs
|
||||
- Keep working toward final specification of NomosDA and block rewards
|
||||
- Meeting with Nomos team to set goals
|
||||
- `vac:tke:ift:tokenomics-research-forum::token-valuation`
|
||||
- advanced the analysis of the token valuation metrics
|
||||
- `vac:tke:ift:tokenomics-research-forum:grantico`
|
||||
- worked on proofs for specific properties of the mechanism
|
||||
- `vac:tke:ift:tokenomics-research-forum::minting-control`
|
||||
- Kept refining work on optimal control and minting
|
||||
|
||||
|
||||
### vac:qa:
|
||||
- `ift:2025q2-qa-rfc-sync-waku:nwaku`
|
||||
- Store protocol [investigation](https://www.notion.so/Nwaku-Store-2188f96fb65c80e78d08d3199aa103d6)
|
||||
- Reported issue with [mismatches found](https://github.com/waku-org/nwaku/issues/3462)
|
||||
- `status:2025q2-status-go-functional-testing:light-mode`
|
||||
- Created dedicated README for the status-backend reliability [test suite](https://github.com/status-im/status-go/pull/6700)
|
||||
- `status:2025q2-status-go-functional-testing:critical-flows`
|
||||
- Created 5 automation tasks
|
||||
- [RecoverAndLogin critical flow test](https://github.com/status-im/status-go/pull/6688)
|
||||
- [Enhanced pytest logging](https://github.com/status-im/status-go/pull/6697)
|
||||
- Reported flaking tests to status-go devs
|
||||
- `nomos:2025q2-da-testing:dispersal-resilience`
|
||||
- chore: Nomos node with mutated DA layer
|
||||
[PR 2](https://github.com/logos-co/nomos-security-tests/pull/2) -> cleanup into [PR 3](https://github.com/logos-co/nomos-security-tests/pull/3) in progress
|
||||
- Test/dispersal resilience
|
||||
[PR 19 - in progress](https://github.com/logos-co/nomos-e2e-tests/pull/19)
|
||||
- Found issue: dispersal not prevented for blob with tampered data
|
||||
[Issue 1369 - open](https://github.com/logos-co/nomos/issues/1369)
|
||||
- Found issue: error "blob sampling timed out" is too generic
|
||||
[Issue 1383 - open](https://github.com/logos-co/nomos/issues/1383)
|
||||
- `nomos:2025q2-e2e-testing:maintenance`
|
||||
- Retest Nomos testnet updates
|
||||
- `waku:2025q2-waku-sync-testing:Integration-test`
|
||||
- Reviewed specs and documentation from Hanno
|
||||
- Added [PR 125](https://github.com/waku-org/waku-interop-tests/pull/125)
|
||||
- Successfully used store-sync tags with reconciliation & transfer
|
||||
- `waku:2025q2-waku-sync-testing:unit-test`
|
||||
- Added [PR 3464](https://github.com/waku-org/nwaku/pull/3464) – more delay for macOS
|
||||
- [PR 3397](https://github.com/waku-org/nwaku/pull/3397) – merged
|
||||
- [PR 3388](https://github.com/waku-org/nwaku/pull/3388) – merged
|
||||
- `waku:2025q2-waku-go-bindings-testing:maintenance`
|
||||
- Retested current issue after Gabriel's fix
|
||||
- Identified 3 failing CI tests; investigating and reporting
|
||||
- `vac:2025q2-nim-libp2p-testing:gossipsub-extended-part3`
|
||||
- [GossipThreshold and PublishThreshold tests](https://github.com/vacp2p/nim-libp2p/pull/1464) – merged
|
||||
- [Split unit and integration tests](https://github.com/vacp2p/nim-libp2p/pull/1465) – merged
|
||||
- [rpcHandler tests](https://github.com/vacp2p/nim-libp2p/pull/1467) – in review
|
||||
- [Organise Behavior tests](https://github.com/vacp2p/nim-libp2p/pull/1468) – in review
|
||||
- [BehaviourPenalty tests](https://github.com/vacp2p/nim-libp2p/pull/1469) – in review
|
||||
- [updateScores tests](https://github.com/vacp2p/nim-libp2p/pull/1471) – in review
|
||||
- `status:2025q2-status-qa:v2-34`
|
||||
- Rechecked News feed fix on Mobile – bug still exists but approved for release
|
||||
- Started and completed builds for release
|
||||
- Signed off final build
|
||||
- Reviewed [PR 18172](https://github.com/status-im/status-desktop/pull/18172), left comments
|
||||
- Continued Qt6 migration support
|
||||
- Debugged failing tests with dev for [PR 18014](https://github.com/status-im/status-desktop/pull/18014)
|
||||
- Created test plan for Shell
|
||||
- Added basic Shell support to e2e [PR 18172](https://github.com/status-im/status-desktop/pull/18172)
|
||||
- Completed fixes for existing critical tests
|
||||
- `admin/misc`
|
||||
- Created PR with [Q3 commitments](https://github.com/vacp2p/roadmap/pull/184)
|
||||
- Q2 [Retro](https://www.notion.so/QA-retro-2025q2-2148f96fb65c80fba5c6c5e8f32b8863)
|
||||
- Synced on Q3 commitments for Status
|
||||
- OOO: 1 CC Day
|
||||
|
||||
### vac:dst:
|
||||
- `admin/misc`
|
||||
- [Notion: DST Q2 Retrospective](https://www.notion.so/DST-retro-2025q2-2168f96fb65c8025b5d3f9e2ddb5ec61)
|
||||
- [Github: Lookahead PR](https://github.com/vacp2p/roadmap/pull/192)
|
||||
- First template of EF grant proposal
|
||||
- Call with P2P CC to set up lab and explain how to launch experiments
|
||||
- Talked with Waku to do nwaku `v0.36.0-rc.0` regression
|
||||
- Created template repository for using jswaku
|
||||
- `vac:dst:vac:2025q2-libp2p-evaluation:regression-testing`
|
||||
- Repeated several high payload experiments due to lab inestability
|
||||
- Confirm IDONTWANT changes have no negative effect
|
||||
- There is a 2~% bandwidth reduction, not confirmed yet because of aforementioned inestabilities.
|
||||
- [Notion: Report](https://www.notion.so/Nim-libp2p-v1-11-0-regression-testing-June-2025-2118f96fb65c802ca1b7c4233271ca26)
|
||||
- `vac:dst:vac:2025q2-libp2p-evaluation:mix-gossipsub`
|
||||
- Reconfirmed bug with new provided logs
|
||||
- Message is sent from the publisher with Mix and Gossipsub at the same time
|
||||
- [Github: PR](https://github.com/vacp2p/10ksim/pull/71)
|
||||
- [Notion: Report](https://www.notion.so/Nim-libp2p-Mix-May-2025-1f38f96fb65c800a8466f68472e799db?source=copy_link#2188f96fb65c8096a18ceba3d1c3fea8)
|
||||
- `vac:dst:status:2025q2-status-go-evaluation:store-performance`
|
||||
- Analyzing if issues can be caused between discrepancies between nwaku `v0.35` (local) and `v0.34` (CI)
|
||||
- `vac:dst:ift:2025q2-dst-tooling:adapt-experiments`
|
||||
- Fixed issues with nodes.yaml template with store nodes
|
||||
- Adapted nimlibp2p experiment
|
||||
- Generated templates for some other experiments
|
||||
- `vac:dst:vac:2025q2-libp2p-evaluation:idontwant-statistical-analysis`
|
||||
- Refactored existing code [Github PR #204](https://github.com/vacp2p/research/pull/204)
|
||||
- Added case for DONTWANT without other gossip [Github PR #205](https://github.com/vacp2p/research/pull/205)
|
||||
|
||||
|
||||
### vac:sc:
|
||||
- `status:2025q2-sn-native-bridge-yield-bearing-module:research-design`
|
||||
- updated our bridge changes on top of the latest changes from upstream https://github.com/vacp2p/linea-monorepo/compare/linea-upstream...vacp2p:linea-monorepo:main
|
||||
- patched the latest Linea's changes rolling back the verifiers updates
|
||||
- started working on the withdrawal with our L1/L2 ETH bridges
|
||||
- `status:2025q2-karma-rln:karma-tiers`
|
||||
- Implemented KarmaTiers contract
|
||||
- https://github.com/vacp2p/staking-reward-streamer/pull/224
|
||||
- Added ability to get tiers by karma balance
|
||||
- `admin/misc`
|
||||
- Reviewed staking protocol spec
|
||||
- https://github.com/vacp2p/rfc-index/pull/161#pullrequestreview-29204
|
||||
|
||||
### vac:acz:
|
||||
- `ift:2025q2-de-mls-tesnet:commit-and-proposal`
|
||||
- Found issue regarding usage of MLS in our purpose, mostly related to how we see consensus application and requires further research. Add page on [notion](https://www.notion.so/de-mls-consensus-issue-2178f96fb65c80fa9942de5956c083c2) and related [PR](https://github.com/vacp2p/de-mls/pull/36)
|
||||
- `ift:2025q2-libp2p-mix-testnet:update-rfc`
|
||||
- Continued [RFC](https://github.com/vacp2p/rfc-index/pull/158) refactor — Section 8 in progress.
|
||||
- `ift:2025q2-libp2p-mix-testnet:solve-discrepancy`
|
||||
- Identified logging order issue: exit logs must precede handler invocation.
|
||||
- Added message ID tracking in GossipSub handler for better traceability.
|
||||
- Ran multiple experiments (with trace mode + minimal logging); results documented here.
|
||||
- `nes:2025q2-nescience-consulting:viewing-keys`
|
||||
- Finished document on [outgoing viewing keys](https://www.notion.so/Outgoing-viewing-keys-and-time-specific-viewing-keys-2178f96fb65c80e793e8dcd8c9d311db): adds outgoing viewing key support to NSSA. Additionally, examined timed-specific viewing keys: time-specific outgoing is possible, but unclear for time-specific incoming.
|
||||
- Finished document [EC recommendation](https://www.notion.so/Notes-on-elliptic-curves-in-NSSA-2188f96fb65c8075912bd85566121973); focused on UTXO generation testing.
|
||||
- `ift:2025q2-rln-status-l2:prover-service`
|
||||
- Persistent storage investigation
|
||||
- Heed: https://github.com/meilisearch/heed
|
||||
- RocksDb: https://docs.rs/rocksdb/latest/rocksdb/
|
||||
- [Persistent storage PR](https://github.com/vacp2p/status-rln-prover/pull/10) - WIP
|
||||
- Review [PR](https://github.com/vacp2p/status-rln-prover/pull/11)
|
||||
- Added test cases for TierLimits and TierMatch enums in the prover service [(PR)](https://github.com/vacp2p/status-rln-prover/pull/11)
|
||||
- `ift:2025q2-zerokit:zerokit-maintaining`
|
||||
- [Zeroize 2nd attempt](https://github.com/vacp2p/zerokit/pull/320) - in review
|
||||
- Investigate optimisation for bytes_le_to_vec_fr & serialization
|
||||
- Reviewed this [PR](https://github.com/vacp2p/zerokit/pull/320) in zerokit
|
||||
- Code review for [PR](https://github.com/vacp2p/zerokit/pull/320)
|
||||
|
||||
- `ift:2025q2-zerokit:perfomance-updates-blogpost`
|
||||
- Got more input from team for the [issue](https://github.com/vacp2p/zerokit/issues/314).
|
||||
- `ift:2025q2-libp2p-mix-testnet:surb-implementation`
|
||||
- Identified repository cohesion as significant obstacle to effective implementation. Made [sub-task](https://github.com/vacp2p/mix/issues/34)
|
||||
- made `main-stage` as the staging ground to get `mix-waku-integ` and `puc/gossipsub` in a state of cohesion
|
||||
- made [draft PR](https://github.com/vacp2p/mix/pull/33) of `mix-waku-integ` to `main-stage` as a reference point for discussions and collaboration
|
||||
- [Updated](https://github.com/vacp2p/mix/commit/78cca77195d5bbd257cdd3a74c2dd79e2bafe7cf) `mix-waku-integ` branch
|
||||
- Made `waku-SURB` off updated `mix-waku-integ`
|
||||
- Identified a [section of code](https://github.com/vacp2p/mix/blob/mix-waku-integ/mix/mix_protocol.nim#L251-L289) suspected to be central to embedding SURB into the SPHINX packet
|
||||
- [Entered discussion](https://github.com/vacp2p/mix/issues/32#issuecomment-2995140226) about mix/client integration details w.r.t. dependencies and impl details
|
||||
- `admin/misc`
|
||||
- 2 CC prepared and took a part in IFT research call
|
||||
- `ift:2025q2-de-mls-tesnet:multi-admin-rfc`
|
||||
- Review the de-MLS architecture [issue](https://www.notion.so/de-mls-consensus-issue-2178f96fb65c80fa9942de5956c083c2)
|
||||
- Update the minorly [RFC](https://www.notion.so/Draft-de-MLS-RFC-temporary-2068f96fb65c804094a5ec624abcf2df)
|
||||
- `ift:2025q2-de-mls-tesnet:blogpost-de-mls-over-waku`
|
||||
- Adressed some feedback to the [PR](https://github.com/vacp2p/vac.dev/pull/159/file
|
||||
|
||||
### vac:nim:
|
||||
- `ift:2025q1-nimble`
|
||||
- WIP vnext default to pass CI
|
||||
https://github.com/nim-lang/nimble/pull/1406
|
||||
- tmisc green except 1
|
||||
- Fixes last test from tmisc
|
||||
- clean up
|
||||
- Adds log to debug one failing test that only fails in the CI
|
||||
- tlocaldeps green
|
||||
- Dont reinstall pkgs. tmulti green
|
||||
- tnimscript green
|
||||
- Implements to run deps binaries in vnext
|
||||
- Pass compiler flags for actionRun and others
|
||||
- truncommand green
|
||||
- fixes flawed test
|
||||
- Fixes an issue with binaries not being properly updated. ttwobinaryversions green
|
||||
- tuninstall green
|
||||
- Declarative parser fails when taskRequires is detected
|
||||
- Skips one test. Fixes "Develop file is used"
|
||||
- Fixes a regression in local dev. Comments a task deps test
|
||||
- Removes unnecessary logging
|
||||
- For build action: Only the root package is built (fixes tforgeinstall, although the declarative parser doesnt support it yet)
|
||||
- Tests if package already exists before installing
|
||||
- Improves TNimInstall test
|
||||
- Since the installation process changed, we need to adds srcDir to the paths as well
|
||||
- Comment failing taskdeps tests
|
||||
- Removes unused import. Fixes test
|
||||
- fixes "should fallback to a previous version of a dependency when is unsatisfable"
|
||||
- comments unused vars
|
||||
- Reenables lin and win CI
|
||||
- comments out develop suite for lin
|
||||
- reeanbles tdevelop. Disables lin and win
|
||||
- green: Task dependencies from lock file are used
|
||||
- Suite green: Task level dependencies
|
||||
- Adjust tests
|
||||
- Remove unused vars
|
||||
- Removes unused var
|
||||
|
||||
|
||||
### vac:rfc:
|
||||
- `vac:rfc:nomos:2025q2-rfc-iteration`
|
||||
- Started reviewing open Nomos specs
|
||||
- Started draft for Nomos Signature RFC
|
||||
- `vac:rfc:waku:2025q2-rfc-iteration:waku2-enr`
|
||||
- Completed waku-ENR update, ready for feedback - https://github.com/waku-org/specs/pull/67
|
||||
- `vac:rfc:nescience:2025q2-rfc-iteration:key-protocol`
|
||||
- Updated the NSSA key protocol spec (almost ready for review): https://github.com/vacp2p/rfc-index/pull/162
|
||||
- `vac:rfc:nescience:2025q2-rfc-iteration:utxo-specification`
|
||||
- Updating the UTXO spec: https://github.com/vacp2p/rfc-index/pull/164
|
||||
- `vac:rfc:codex:2025q2-rfc-iteration`
|
||||
- Reading the documentation (and trying out locally) - https://github.com/codex-storage/codex-docs/blob/master/README.md
|
||||
- `admin/misc`
|
||||
- Reviewed feedback from Staking RFC, should make changes by EOD - https://github.com/vacp2p/rfc-index/pull/161
|
||||
- Retrospective - sharing doc on Monday
|
||||
- Research call blog post: https://forum.vac.dev/t/ift-research-call-june-18th-2025-zerokit-v0-8-and-its-applications/513
|
||||
|
||||
### vac:sec:
|
||||
- `ift:2025q2-migration-to-element:instance-hardening-review`
|
||||
- Reviewed security and privacy setup in free.technology server
|
||||
- `ift:2025q2-cicd-security-review:status-design-reviews`
|
||||
- Finished design review of the role/model MVP implementation for Status team
|
||||
- `ift:2025q2-vulma-and-ir:remediation-tracking`
|
||||
- Triage recent Dependabot and CodeQL alerts and prioritize high and medium findings.
|
||||
- `ift:2025q2-vulma-and-ir:incidents`
|
||||
- Keycard incidents involving HR and Keycard members
|
||||
- `ift:2025q2-security-automation: POC for app catalogue update from Expensify`
|
||||
- Testing HTTP nodes instead of n8n Notion - for more accurate matching
|
||||
- `ift:2025q2-finance-automation`
|
||||
- Expense amount conversion based on expense date and CC currency
|
||||
- `ift:2025q2-iam-operations:remove-unnecessary-users`
|
||||
- Concept flows for GitHub, Google, Discord
|
||||
- `admin/misc`
|
||||
- Drafted Q3 NCTs
|
||||
- Reviewed the need of KnowBe4 for the org and the team
|
||||
|
||||
### vac:nes:
|
||||
|
||||
|
||||
Reference in New Issue
Block a user