AtHeartEngineer/roadmap
1
0
Fork 0
mirror of https://github.com/vacp2p/roadmap.git synced 2026-01-07 23:04:01 -05:00
Code Issues Packages Projects Releases Wiki Activity

Chore/logos renamings 2026 (#368)

Browse Source
This commit is contained in:
fbarbu15
2026-01-04 15:14:57 +02:00
committed by GitHub
parent 40f2e596c6
commit 2a65491473
63 changed files with 453 additions and 517 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
content/bi/finance/2026q1-finance-reporting-helper.md
View File

@@ -8,7 +8,7 @@ draft: false
description: Improve Finance reporting
---
`vac:bi:finance:2026q1-finance-reporting-helper`
`ift-ts:bi:finance:2026q1-finance-reporting-helper`
## Description
@@ -18,7 +18,7 @@ Continue to help finance in the automation of reporting.
### Improve reporting
* fully qualified name: `vac:bi:finance:2026q1-finance-reporting-helper:impovement`
* fully qualified name: `ift-ts:bi:finance:2026q1-finance-reporting-helper:impovement`
* owner: nikolay
* status: not started
* start-date: 2026/01/01

8
content/bi/ift/2026q1-ift-smart-contract-monitoring.md
View File

@@ -8,7 +8,7 @@ draft: false
description: Monitore Smart Contract for different IFT teams
---
`vac:bi:ift:2026q1-ift-smart-contract-monitoring`
`ift-ts:bi:ift:2026q1-ift-smart-contract-monitoring`
## Description
@@ -18,7 +18,7 @@ Monitore Smart contract used by IFT teams.
### Status Network Vault
* fully qualified name: `vac:bi:ift:2026q1-ift-smart-contract-monitoring:status-network-vault`
* fully qualified name: `ift-ts:bi:ift:2026q1-ift-smart-contract-monitoring:status-network-vault`
* owner: claire
* status: not started
* start-date: 2026/01/01
@@ -36,7 +36,7 @@ Monitore Vault for Status network (incoming / outgoing flow, ...).
### Lido V3 Vault
* fully qualified name: `vac:bi:ift:2026q1-ift-smart-contract-monitoring:lido-v3-vault`
* fully qualified name: `ift-ts:bi:ift:2026q1-ift-smart-contract-monitoring:lido-v3-vault`
* owner: tbd
* status: not started
* start-date: 2026/01/01
@@ -55,7 +55,7 @@ Monitore Lido v3 vault since Develp team is participating in the setup.
### SNT Uniswap Pool
* fully qualified name: `vac:bi:ift:2026q1-ift-smart-contract-monitoring:snt-uniswap-pool`
* fully qualified name: `ift-ts:bi:ift:2026q1-ift-smart-contract-monitoring:snt-uniswap-pool`
* owner: tdb
* status: not started
* start-date: 2026/01/01

6
content/bi/index.md
View File

@@ -2,10 +2,10 @@
title: BI Service Unit
tags:
- bi
- vac
- ift-ts
---
## `vac:bi:`
## `ift-ts:bi:`
---
@@ -13,7 +13,7 @@ The BI Service unit is responsible for providing Data to the various IFT Project
The teams extracts, transform and create visualization according to the request of each team.
Additionally, it handle the RAG CaaS to ingest map the internal knowledge of IFTs teams.
## 2026q1 `vac:bi:`
## 2026q1 `ift-ts:bi:`
---
### `finance`

6
content/bi/logos/2026q1-logos-circle-monitoring.md
View File

@@ -8,7 +8,7 @@ draft: false
description: Improve monitoring of Logos Circle event.
---
`vac:bi:logos:2026q1-logos-circle-monitoring`
`ift-ts:bi:logos:2026q1-logos-circle-monitoring`
## Description
@@ -18,7 +18,7 @@ Improve monitoring of the Logos Circle.
### Telegram monitoring
* fully qualified name: `vac:bi:logos:2026q1-logos-circle-monitoring:telegram-monitoring`
* fully qualified name: `ift-ts:bi:logos:2026q1-logos-circle-monitoring:telegram-monitoring`
* owner: claire
* status: not started
* start-date: 2026/01/01
@@ -35,7 +35,7 @@ The Circles have migrated to Telegram for communication. Add an monitoring mecan
### Improve dashboards
* fully qualified name: `vac:bi:logos:2026q1-logos-circle-monitoring:dashboard-improvement`
* fully qualified name: `ift-ts:bi:logos:2026q1-logos-circle-monitoring:dashboard-improvement`
* owner: claire
* status: not started
* start-date: 2026/01/01

4
content/bi/logos/2026q1-logos-github-monitoring.md
View File

@@ -8,7 +8,7 @@ draft: false
description: Update and improve Github Monitoring
---
`vac:bi:logos:2026q1-logos-github-monitoring`
`ift-ts:bi:logos:2026q1-logos-github-monitoring`
## Description
@@ -18,7 +18,7 @@ Improve monitoring of the Github Repository.
### Github Monitoring
* fully qualified name: `vac:bi:logos:2026q1-logos-github-monitoring:impovement`
* fully qualified name: `ift-ts:bi:logos:2026q1-logos-github-monitoring:impovement`
* owner: claire
* status: not started
* start-date: 2026/01/01

10
content/bi/logos/2026q1-logos-public-rag.md
View File

@@ -8,7 +8,7 @@ draft: false
description: Create a Public RAG for the Logos Stack
---
`vac:bi:logos:2026q1-logos-public-rag`
`ift-ts:bi:logos:2026q1-logos-public-rag`
## Description
@@ -20,7 +20,7 @@ Principal github issue: https://github.com/status-im/data-docs/issues/122
### Update existing RAG Pipeline for public repository
* fully qualified name: `vac:bi:logos:2026q1-logos-public-rag:update-rag-pipelines`
* fully qualified name: `ift-ts:bi:logos:2026q1-logos-public-rag:update-rag-pipelines`
* owner: nickninov
* status: not started
* start-date: 2026/01/01
@@ -38,7 +38,7 @@ Adapt the ETL Pipeline to make a public RAG according to the new repository orga
### MCP tooling for Logos Stack
* fully qualified name: `vac:bi:logos:2026q1-logos-public-rag:mcp-tooling`
* fully qualified name: `ift-ts:bi:logos:2026q1-logos-public-rag:mcp-tooling`
* owner: alexis and claire
* status: not started
* start-date: 2026/01/01
@@ -55,7 +55,7 @@ Prepare MCP tools to make the RAG data accessible in dev enviroment (Claude desk
### Messaging bot for RAG interaction
* fully qualified name: `vac:bi:logos:2026q1-logos-public-rag:messaging-bot`
* fully qualified name: `ift-ts:bi:logos:2026q1-logos-public-rag:messaging-bot`
* owner: tdb
* status: not started
* start-date: 2026/01/01
@@ -73,7 +73,7 @@ Make a discord bot to interract with the Logos RAG in Discord Server (and Status
### Response Evaluation
* fully qualified name: `vac:bi:logos:2026q1-logos-public-rag:response-evaluation`
* fully qualified name: `ift-ts:bi:logos:2026q1-logos-public-rag:response-evaluation`
* owner: tdb
* status: not started
* start-date: 2026/01/01

16
content/dr/index.md
View File

@@ -1,16 +0,0 @@
---
title: Deep Research Service Unit
tags:
- dr
- vac
---
## `vac:dr:`
---
## `ift:`
## `codex:`
## `nes:`

6
content/dst/anoncomms/2026q1-anoncomms-evaluation.md
View File

@@ -11,7 +11,7 @@ and look for regressions,
learn scaling properties and run scaling studies."
---
`vac:dst:anoncomms:2026q1-anoncomms-evaluation`
`ift-ts:dst:anoncomms:2026q1-anoncomms-evaluation`
## Description
Test Anoncomms protocols on each new version or requested feature
@@ -26,7 +26,7 @@ Do this monthly, reliably, with documentation of findings.
### Mix
> *Note*: This needs more input from project
* fully qualified name: `vac:dst:anoncomms:2026q1-anoncomms-evaluation:mix`
* fully qualified name: `ift-ts:dst:anoncomms:2026q1-anoncomms-evaluation:mix`
* owner: TBD
* status: not started
* start-date: 2026/01/01
@@ -42,7 +42,7 @@ TBD
### KAD-DHT
> *Note*: This needs more input from project
* fully qualified name: `vac:dst:anoncomms:2026q1-anoncomms-evaluation:kad-dht`
* fully qualified name: `ift-ts:dst:anoncomms:2026q1-anoncomms-evaluation:kad-dht`
* owner: TBD
* status: not started
* start-date: 2026/01/01

30
content/dst/nomos/2026q1-nomos-evaluation.md → content/dst/blockchain/2026q1-blockchain-evaluation.md
View File

@@ -1,16 +1,16 @@
---
title: Nomos Evaluation
title: Blockchain Evaluation
tags:
- "2026q1"
- "dst"
- "nomos"
- "blockchain"
draft: false
description: "Test Nomos on each new version or requested feature
description: "Test Blockchain on each new version or requested feature
and look for regressions,
learn scaling properties and run scaling studies."
---
`vac:dst:nomos:2026q1-nomos-evaluation`
`ift-ts:dst:blockchain:2026q1-blockchain-evaluation`
## Description
@@ -19,14 +19,14 @@ learn scaling properties and run scaling studies."
Use real world testing,
theoretical analysis
and simulation
to determine and improve Nomos's scaling properties.
Find the limits of Nomos's capabilities
to determine and improve Blockchain's scaling properties.
Find the limits of Blockchain's capabilities
and measure them in different scenarios.
We will measure the real world speeds and latency of Nomos' mixnet,
We will measure the real world speeds and latency of Blockchain' mixnet,
and what use cases it is therefore able to support.
The scope of this commitment depends on the Nomos team
The scope of this commitment depends on the Blockchain team
work and improvements, and it is subjected to change.
## Task List
@@ -34,7 +34,7 @@ work and improvements, and it is subjected to change.
### Blend benchmarking
> *Note*: This was moved from previous quarter
* fully qualified name: `vac:dst:nomos:2026q1-nomos-evaluation:blendnet-benchmarking`
* fully qualified name: `ift-ts:dst:blockchain:2026q1-blockchain-evaluation:blendnet-benchmarking`
* owner: Alberto
* status: not started
* start-date: 2026/01/01
@@ -42,7 +42,7 @@ work and improvements, and it is subjected to change.
#### Description
Measure the speed and reliability of Nomos's blendnet.
Measure the speed and reliability of Blockchain's blendnet.
Schedule note: Dates reflect quarter bounds; update when actual timing is known.
#### Deliverables
@@ -53,7 +53,7 @@ Schedule note: Dates reflect quarter bounds; update when actual timing is known.
### DA benchmarking
> *Note*: This was moved from previous quarter
* fully qualified name: `vac:dst:nomos:2026q1-nomos-evaluation:da-benchmarking`
* fully qualified name: `ift-ts:dst:blockchain:2026q1-blockchain-evaluation:da-benchmarking`
* owner: TBD
* status: not started
* start-date: 2026/01/01
@@ -61,7 +61,7 @@ Schedule note: Dates reflect quarter bounds; update when actual timing is known.
#### Description
Measure Nomos bandwidth usage in DA per node and entire network.
Measure Blockchain bandwidth usage in DA per node and entire network.
Schedule note: Dates reflect quarter bounds; update when actual timing is known.
#### Deliverables
@@ -69,10 +69,10 @@ Schedule note: Dates reflect quarter bounds; update when actual timing is known.
* Documents:
### Nomos consumption
### Blockchain consumption
> *Note*: This was moved from previous quarter
* fully qualified name: `vac:dst:nomos:2026q1-nomos-evaluation:consumption`
* fully qualified name: `ift-ts:dst:blockchain:2026q1-blockchain-evaluation:consumption`
* owner: TBD
* status: not started
* start-date: 2026/01/01
@@ -80,7 +80,7 @@ Schedule note: Dates reflect quarter bounds; update when actual timing is known.
#### Description
Measure Nomos resource consumption (CPU/RAM) usage in different scenarios.
Measure Blockchain resource consumption (CPU/RAM) usage in different scenarios.
Schedule note: Dates reflect quarter bounds; update when actual timing is known.
#### Deliverables

8
content/dst/ift/2026q1-dst-lab.md
View File

@@ -10,7 +10,7 @@ Anticipate untapped use cases and needs from other teams.
Improve the usage of the lab by optimizing resources and time allocation."
---
`vac:dst:ift:2026q1-dst-lab`
`ift-ts:dst:ift:2026q1-dst-lab`
## Description
@@ -28,7 +28,7 @@ while allow provisioning to other teams dedicated machines if they are needed.
### Analyze current stack
* fully qualified name: `vac:dst:ift:2026q1-dst-lab:analyze-current-stack`
* fully qualified name: `ift-ts:dst:ift:2026q1-dst-lab:analyze-current-stack`
* owner: Mamoutou
* status: not started
* start-date: 2026/01/01
@@ -46,7 +46,7 @@ Report findings with analysis and benchmarks of the results.
### Optimize data scrapping
* fully qualified name: `vac:dst:ift:2026q1-dst-lab:optimize-data-scrapping`
* fully qualified name: `ift-ts:dst:ift:2026q1-dst-lab:optimize-data-scrapping`
* owner: Mamoutou
* status: not started
* start-date: 2026/01/01
@@ -64,7 +64,7 @@ Optimize the storage to reduce used space if data is older than a certain period
### Lab health monitoring
* fully qualified name: `vac:dst:ift:2026q1-dst-lab:lab-health-monitoring`
* fully qualified name: `ift-ts:dst:ift:2026q1-dst-lab:lab-health-monitoring`
* owner: Mamoutou
* status: not started
* start-date: 2026/01/01

14
content/dst/ift/2026q1-dst-tooling.md
View File

@@ -11,7 +11,7 @@ This includes functionalities such as deployments,
monitoring, analysis, and control of aforementioned software's."
---
`vac:dst:ift:2026q1-dst-tooling`
`ift-ts:dst:ift:2026q1-dst-tooling`
## Description
@@ -34,7 +34,7 @@ adversarial conditions and control message behavior.
### General tooling (recurring)
* fully qualified name: `vac:dst:ift:2026q1-dst-tooling:general-tooling`
* fully qualified name: `ift-ts:dst:ift:2026q1-dst-tooling:general-tooling`
* owner: TBD
* status: not started
* start-date: 2026/01/01
@@ -50,7 +50,7 @@ Should be made general when possible.
### Expand deployment - Waku
* fully qualified name: `vac:dst:ift:2026q1-dst-tooling:expand-deployment-waku`
* fully qualified name: `ift-ts:dst:ift:2026q1-dst-tooling:expand-deployment-waku`
* owner: TBD
* status: not started
* start-date: 2026/01/01
@@ -67,7 +67,7 @@ specific experiments with them.
### Expand deployment - nim-libp2p
* fully qualified name: `vac:dst:ift:2026q1-dst-tooling:expand-deployment-nim-libp2p`
* fully qualified name: `ift-ts:dst:ift:2026q1-dst-tooling:expand-deployment-nim-libp2p`
* owner: TBD
* status: not started
* start-date: 2026/01/01
@@ -82,7 +82,7 @@ Adjust deployment builders to support nim-libp2p.
### Expand deployment - codex
* fully qualified name: `vac:dst:ift:2026q1-dst-tooling:expand-deployment-codex`
* fully qualified name: `ift-ts:dst:ift:2026q1-dst-tooling:expand-deployment-codex`
* owner: TBD
* status: not started
* start-date: 2026/01/01
@@ -97,7 +97,7 @@ Adjust deployment builders to support codex.
### Expand deployment - nomos
* fully qualified name: `vac:dst:ift:2026q1-dst-tooling:expand-deployment-nomos`
* fully qualified name: `ift-ts:dst:ift:2026q1-dst-tooling:expand-deployment-nomos`
* owner: TBD
* status: not started
* start-date: 2026/01/01
@@ -112,7 +112,7 @@ Adjust deployment builders to support nomos.
### Expand deployment - anoncomms
* fully qualified name: `vac:dst:ift:2026q1-dst-tooling:expand-deployment-anoncomms`
* fully qualified name: `ift-ts:dst:ift:2026q1-dst-tooling:expand-deployment-anoncomms`
* owner: TBD
* status: not started
* start-date: 2026/01/01

12
content/dst/vac/2026q1-libp2p-evaluation.md → content/dst/ift/2026q1-libp2p-evaluation.md
View File

@@ -3,14 +3,14 @@ title: Libp2p Evaluation
tags:
- "2026q1"
- "dst"
- "vac"
- "ift"
draft: false
description: "Test libp2p on each new version or feature
and look for regressions,
learn scaling properties and run scaling studies."
---
`vac:dst:vac:2026q1-libp2p-evaluation`
`ift-ts:dst:ift:2026q1-libp2p-evaluation`
## Description
@@ -30,7 +30,7 @@ work and improvements, and it is subjected to change.
### Regression testing (recurring)
* fully qualified name: `vac:dst:vac:2026q1-libp2p-evaluation:regression-testing`
* fully qualified name: `ift-ts:dst:ift:2026q1-libp2p-evaluation:regression-testing`
* owner: TBD
* status: not started
* start-date: 2026/01/01
@@ -50,7 +50,7 @@ and ensure they don't happen again.
### ls-quic
* fully qualified name: `vac:dst:vac:2026q1-libp2p-evaluation:ls-quic`
* fully qualified name: `ift-ts:dst:ift:2026q1-libp2p-evaluation:ls-quic`
* owner: TBD
* status: not started
* start-date: 2026/01/01
@@ -70,7 +70,7 @@ between different commits.
### Quic-vs-tcp
> *Note*: This was moved from previous quarter
* fully qualified name: `vac:dst:vac:2026q1-libp2p-evaluation:quic-vs-tcp`
* fully qualified name: `ift-ts:dst:ift:2026q1-libp2p-evaluation:quic-vs-tcp`
* owner: TBD
* status: not started
* start-date: 2026/01/01
@@ -86,7 +86,7 @@ Perform a comparison between nim-libp2p using quic and waku using mplex and yamu
### ls-quic
* fully qualified name: `vac:dst:vac:2026q1-libp2p-evaluation:ls-quic`
* fully qualified name: `ift-ts:dst:ift:2026q1-libp2p-evaluation:ls-quic`
* owner: TBD
* status: not started
* start-date: 2026/01/01

24
content/dst/index.md
View File

@@ -2,11 +2,11 @@
title: Distributed Systems Testing Service Unit
tags:
- dst
- vac
- ift-ts
---
## `vac:dst:`
## `ift-ts:dst:`
---
@@ -20,30 +20,28 @@ are not only effective but also maintain or improve system performance and scala
[[dst/preview|Roadmap Preview]]
## 2026q1 `vac:dst:`
## 2026q1 `ift-ts:dst:`
---
### `anoncomms`
* [[dst/anoncomms/2026q1-anoncomms-evaluation|anoncomms-evaluation]]
### `codex`
* [[dst/codex/2026q1-codex-evaluation|codex-evaluation]]
### `storage`
* [[dst/storage/2026q1-storage-evaluation|storage-evaluation]]
### `ift`
* [[dst/ift/2026q1-dst-lab|dst-lab]]
* [[dst/ift/2026q1-dst-tooling|dst-tooling]]
* [[dst/ift/2026q1-libp2p-evaluation|libp2p-evaluation]]
### `logos-core`
* [[dst/logos-core/2026q1-logos-core-evaluation|logos-core-evaluation]]
### `nomos`
* [[dst/nomos/2026q1-nomos-evaluation|nomos-evaluation]]
### `blockchain`
* [[dst/blockchain/2026q1-blockchain-evaluation|blockchain-evaluation]]
### `vac`
* [[dst/vac/2026q1-libp2p-evaluation|libp2p-evaluation]]
### `waku`
* [[dst/waku/2026q1-waku-evaluation|waku-evaluation]]
* [[dst/waku/2026q1-waku-scaling|waku-scaling]]
### `messaging`
* [[dst/messaging/2026q1-messaging-evaluation|messaging-evaluation]]
* [[dst/messaging/2026q1-messaging-scaling|messaging-scaling]]
---
## 2025q4 `vac:dst:`

12
content/dst/logos-core/2026q1-logos-core-evaluation.md
View File

@@ -9,7 +9,7 @@ description: "Perform integration scenarios in logos core
with different components and evaluate their behaviour."
---
`vac:dst:logos-core:2026q1-logos-core-evaluation`
`ift-ts:dst:logos-core:2026q1-logos-core-evaluation`
## Description
@@ -26,7 +26,7 @@ These componentes are logos-messaging, logos-storage and logos-blockchain.
### logos-core evaluation
* fully qualified name: `vac:dst:logos-core:2026q1-logos-core-evaluation:evaluation`
* fully qualified name: `ift-ts:dst:logos-core:2026q1-logos-core-evaluation:evaluation`
* owner: TBD
* status: not started
* start-date: 2026/01/01
@@ -42,7 +42,7 @@ issues if they are found.
### logos-messaging
* fully qualified name: `vac:dst:logos-core:2026q1-logos-core-evaluation:logos-messaging`
* fully qualified name: `ift-ts:dst:logos-core:2026q1-logos-core-evaluation:logos-messaging`
* owner: TBD
* status: not started
* start-date: 2026/01/01
@@ -58,7 +58,7 @@ Realize the same scenarios and reports as in `evaluation` task.
- Related PRs if apply:
### logos-storage
* fully qualified name: `vac:dst:logos-core:2026q1-logos-core-evaluation:logos-storage`
* fully qualified name: `ift-ts:dst:logos-core:2026q1-logos-core-evaluation:logos-storage`
* owner: TBD
* status: not started
* start-date: 2026/01/01
@@ -76,7 +76,7 @@ Realize the same scenarios and reports as in `evaluation` task.
### logos-blockchain
* fully qualified name: `vac:dst:logos-core:2026q1-logos-core-evaluation:logos-blockchain`
* fully qualified name: `ift-ts:dst:logos-core:2026q1-logos-core-evaluation:logos-blockchain`
* owner: TBD
* status: not started
* start-date: 2026/01/01
@@ -94,7 +94,7 @@ Realize the same scenarios and reports as in `evaluation` task.
### full stack
* fully qualified name: `vac:dst:logos-core:2026q1-logos-core-evaluation:full-stack`
* fully qualified name: `ift-ts:dst:logos-core:2026q1-logos-core-evaluation:full-stack`
* owner: TBD
* status: not started
* start-date: 2026/01/01

16
content/dst/waku/2026q1-waku-evaluation.md → content/dst/messaging/2026q1-messaging-evaluation.md
View File

@@ -1,22 +1,22 @@
---
title: Waku Evaluation
title: Messaging Evaluation
tags:
- "2026q1"
- "dst"
- "waku"
- "messaging"
draft: false
description: "Test Waku on each new version or requested feature
description: "Test Messaging on each new version or requested feature
and look for regressions,
learn scaling properties and run scaling studies."
---
`vac:dst:waku:2026q1-waku-evaluation`
`ift-ts:dst:messaging:2026q1-messaging-evaluation`
## Description
Test Waku on each new version or requested feature
Test Messaging 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.
understand the limits of Messaging and its behaviour.
Deliver reports and actionable insights.
Do this monthly, reliably, with documentation of findings.
@@ -24,7 +24,7 @@ Do this monthly, reliably, with documentation of findings.
### Regression testing (recurring)
* fully qualified name: `vac:dst:waku:2026q1-waku-evaluation:regression-testing`
* fully qualified name: `ift-ts:dst:messaging:2026q1-messaging-evaluation:regression-testing`
* owner: TBD
* status: not started
* start-date: 2026/01/01
@@ -33,7 +33,7 @@ Do this monthly, reliably, with documentation of findings.
#### Description
Run different scenarios
and collect evidence and data
of Waku's behaviour.
of Messaging's behaviour.
Test for known regressions
that have occurred in the past

34
content/dst/waku/2026q1-waku-scaling.md → content/dst/messaging/2026q1-messaging-scaling.md
View File

@@ -1,36 +1,36 @@
---
title: Waku Scaling
title: Messaging Scaling
tags:
- "2026q1"
- "dst"
- "waku"
- "messaging"
draft: false
description: "Use experiments determine and
improve Waku's scaling properties.
Find the limits of Waku's capabilities
improve Messaging's scaling properties.
Find the limits of Messaging's capabilities
and measure them in different scenarios.
Deliver hard numbers and actionable insights.
Confirm or reject our ideas or presented ones."
---
`vac:dst:waku:2026q1-waku-scaling`
`ift-ts:dst:messaging:2026q1-messaging-scaling`
## Description
We will use realistic Waku node experiments to evaluate
and improve Waku's scalability by conducting
We will use realistic Messaging node experiments to evaluate
and improve Messaging'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,
integrate nmessaging in Status Desktop for seamless relay functionality,
and implement the SDS protocol for group messaging reliability and recovery.
## Task list
### scalable data sync
* fully qualified name: `vac:dst:waku:2026q1-waku-scaling:scalable-data-sync`
* fully qualified name: `ift-ts:dst:messaging:2026q1-messaging-scaling:scalable-data-sync`
* owner: TBD
* status: not started
* start-date: 2026/01/01
@@ -50,7 +50,7 @@ consistency within `6*S` seconds **(Vac-DST)**.
### Status communities
* fully qualified name: `vac:dst:waku:2026q1-waku-scaling:status-communities`
* fully qualified name: `ift-ts:dst:messaging:2026q1-messaging-scaling:status-communities`
* owner: TBD
* status: not started
* start-date: 2026/01/01
@@ -69,7 +69,7 @@ Logos-messaging specific FURPS, before Chat SDK integration.
### Status private chats
* fully qualified name: `vac:dst:waku:2026q1-waku-scaling:status-private-chats`
* fully qualified name: `ift-ts:dst:messaging:2026q1-messaging-scaling:status-private-chats`
* owner: TBD
* status: not started
* start-date: 2026/01/01
@@ -85,7 +85,7 @@ Logos-messaging specific FURPS, before Chat SDK integration.
### Incentivisation
* fully qualified name: `vac:dst:waku:2026q1-waku-scaling:incentivisation`
* fully qualified name: `ift-ts:dst:messaging:2026q1-messaging-scaling:incentivisation`
* owner: TBD
* status: not started
* start-date: 2026/01/01
@@ -108,7 +108,7 @@ Performance:
### Rendezvous
* fully qualified name: `vac:dst:waku:2026q1-waku-scaling:rendezvous`
* fully qualified name: `ift-ts:dst:messaging:2026q1-messaging-scaling:rendezvous`
* owner: TBD
* status: not started
* start-date: 2026/01/01
@@ -116,7 +116,7 @@ Performance:
#### Description
1. In an established network of 1k relay nodes on 10 shards with 1 bootstrap node,
100 new relay nodes (relay + discv5 + Waku PX + rendezvous)
100 new relay nodes (relay + discv5 + Messaging PX + rendezvous)
can connect to 20 relay peers in the right shard within 1 minute (**Vac-DST**)
; run simulation without rendezvous to see the difference
@@ -126,7 +126,7 @@ Performance:
### RLN Relay
* fully qualified name: `vac:dst:waku:2026q1-waku-scaling:rln-relay`
* fully qualified name: `ift-ts:dst:messaging:2026q1-messaging-scaling:rln-relay`
* owner: TBD
* status: not started
* start-date: 2026/01/01
@@ -144,7 +144,7 @@ Performance:
### Store
* fully qualified name: `vac:dst:waku:2026q1-waku-scaling:store`
* fully qualified name: `ift-ts:dst:messaging:2026q1-messaging-scaling:store`
* owner: TBD
* status: not started
* start-date: 2026/01/01
@@ -163,7 +163,7 @@ and average message size under 500KiB **(Vac-DST)**.
### Store sync
* fully qualified name: `vac:dst:waku:2026q1-waku-scaling:store-sync`
* fully qualified name: `ift-ts:dst:messaging:2026q1-messaging-scaling:store-sync`
* owner: TBD
* status: not started
* start-date: 2026/01/01

22
content/dst/codex/2026q1-codex-evaluation.md → content/dst/storage/2026q1-storage-evaluation.md
View File

@@ -1,27 +1,27 @@
---
title: Codex Evaluation
title: Storage Evaluation
tags:
- "2026q1"
- "dst"
- "codex"
- "storage"
draft: false
description: "Test Codex on each new version or requested feature
description: "Test Storage on each new version or requested feature
and look for regressions,
learn scaling properties and run scaling studies."
---
`vac:dst:codex:2026q1-codex-evaluation`
`ift-ts:dst:storage:2026q1-storage-evaluation`
## Description
Test Codex on each new version or requested feature
Test Storage on each new version or requested feature
and look for regressions if this is required.
Help Codex with testing and benchmarking new features.
Help Storage with testing and benchmarking new features.
### Background
We want to learn specific, actionable information
about Codex's behaviour
about Storage'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.
@@ -33,7 +33,7 @@ theoretical analysis and experiments.
### Filehsharing client
* fully qualified name: `vac:dst:codex:2026q1-codex-evaluation:filesharing-client`
* fully qualified name: `ift-ts:dst:storage:2026q1-storage-evaluation:filesharing-client`
* owner: TBD
* status: not started
* start-date: 2026/01/01
@@ -41,7 +41,7 @@ theoretical analysis and experiments.
#### Description
Assist the Codex team to check the functionality of the
Assist the Storage team to check the functionality of the
filesharing client implementation under heavy/big workloads.
#### Deliverables
@@ -50,7 +50,7 @@ filesharing client implementation under heavy/big workloads.
### Filehsharing client + mix
* fully qualified name: `vac:dst:codex:2026q1-codex-evaluation:filesharing-client-mix`
* fully qualified name: `ift-ts:dst:storage:2026q1-storage-evaluation:filesharing-client-mix`
* owner: TBD
* status: not started
* start-date: 2026/01/01
@@ -58,7 +58,7 @@ filesharing client implementation under heavy/big workloads.
#### Description
Assist the Codex team to check the functionality of the
Assist the Storage team to check the functionality of the
filesharing client implementation under heavy/big workloads using mix protocol.
#### Deliverables

41
content/index.md
View File

@@ -1,8 +1,8 @@
---
title: Vac Roadmap
title: IFT-TS Roadmap
---
## Vac R&D Service Units
## IFT Technical Services Units
- `p2p:` [[p2p|Peer-to-peer]]
- `tke:` [[tke|Token Economics]]
@@ -24,44 +24,15 @@ title: Vac Roadmap
- [Weekly updates](tags/vac-updates)
- [Monthly reports](tags/vac-monthly)
## Vac Narratives
### 1 Conduit of Expertise [internally]
First, the strategic objective of scaling project capacity and legitimacy via community co-creation is captured in the annual goal of increasing user-generated content,
code and participation by 50% over the course of 2025.
The preceding step is to set up all projects to accept open-source contributions via an RFC culture.
Second, we have the distinct advantage that we are an actor in our own ecosystem, resulting in the unfair advantage of being our own first community.
Collaboration within our family of projects not only yield efficiencies, but also doubles as a competitive advantage.
VAC contributes to both these goals as an internal conduit of expertise, as well as an RFC culture carrier.
Viable strategies for a conduit of expertise and culture carrier seem to include: VAC to maintain a repository on internal knowledge creation (via ie the IFT research calls),
RFC culture (to lay the foundation for external contributions), and to identify and facilitate IFT project synergies (collaboration between projects must be seen as a way to become more efficient).
### 2 Premier Research destination [externally]
IFT builds public goods to safeguard civil liberties in the digital age. Ownerless public goods are maintained by movements,
therefore community building is a strategic priority, where VAC plays a technical role.
If only IFT maintains IFT incubated projects a year from now, that would be a failure; if a diverse community maintains projects, that would be a success.
Ultimately, VAC has the potential to become the equivalent to Ethereum Research.
First, via VAC, IFT already has substantial ties to the Libp2p, Ethereum, and Nim ecosystems. Second, the IFT ecosystem of projects is the first community of contributors.
Viable strategies for a community platform seem to include: To link VAC contributions within other communities back to VAC,
to externalise IFT research call digests, to build trust in projects by open sourcing internal audits/QA/roadmap discussions.
What to watch out for: A process without a use (ie improvement processes); build value first, community second, and processes last.
## Task Tag Structure
The following descibes a fully qualified task tag
`vac:<unit>:<for_project>:<quarter-cname>:<tname>`
- `vac` indicates it is a vac commitment
- `unit` indicates the vac unit `p2p`, `dst`, `qa` ,`tke`, `acz`, `sc`, `nes`, `rfc`
- `for_project` indicates which Logos project the commitment is mainly for `nomos`, `waku`, `codex`, `nimbus`, `status`; or `ift` (meaning it is not project specific)
`ift-ts:<unit>:<for_project>:<quarter-cname>:<tname>`
- `ift-ts` indicates it is a ift-ts commitment
- `unit` indicates the ift-ts unit `p2p`, `dst`, `qa` ,`tke`, `acz`, `sc`, `nes`, `rfc`
- `for_project` indicates which Logos project the commitment is mainly for `blockchain`, `messaging`, `storage`, `nimbus`, `status`; or `ift` (meaning it is not project specific)
- `quarter` the quarter of the commitment, e.g. `2024q4`
- `cname` the name of the commitment the task is part ofs
- `tname` the name of the task

16
content/nes/index.md
View File

@@ -1,16 +0,0 @@
---
title: Nescience Incubation Project
description: Nescience Zero-knowledge State Separation Architecture
tags:
- nes
- vac
---
## `vac:nes:`
---
Nescience commitments are listed in Notion.

12
content/nim/ift/2026q1-nim-core-libs.md
View File

@@ -8,7 +8,7 @@ draft: false
description: Continue evolving Nim core libraries.
---
`vac:nim:ift:2026q1-nim-core-libs`
`ift-ts:nim:ift:2026q1-nim-core-libs`
## Description
Maintain and extend the foundational Nim libraries required by IFT teams.
@@ -17,7 +17,7 @@ Maintain and extend the foundational Nim libraries required by IFT teams.
### Json RPC
* fully qualified name: `vac:nim:ift:2026q1-nim-core-libs:json-rpc`
* fully qualified name: `ift-ts:nim:ift:2026q1-nim-core-libs:json-rpc`
* owner: Nitely
* status: not started
* start-date: 2026/01/01
@@ -33,7 +33,7 @@ These enhancements will enable JSON-RPC to be used efficiently for cross-thread
### Integrate nim-intops into nim-bncurve and nim-stint
* fully qualified name: `vac:nim:ift:2026q1-nim-core-libs:intops-integration-bncurve-stint`
* fully qualified name: `ift-ts:nim:ift:2026q1-nim-core-libs:intops-integration-bncurve-stint`
* owner: Constantine
* status: not started
* start-date: 2026/01/01
@@ -47,7 +47,7 @@ These enhancements will enable JSON-RPC to be used efficiently for cross-thread
### Protobuf Serialization in libp2p
* fully qualified name: `vac:nim:ift:2026q1-nim-core-libs:libp2p-protobuf-serialization`
* fully qualified name: `ift-ts:nim:ift:2026q1-nim-core-libs:libp2p-protobuf-serialization`
* owner: Nitely
* status: not started
* start-date: 2026/02/15
@@ -61,7 +61,7 @@ These enhancements will enable JSON-RPC to be used efficiently for cross-thread
### Language Server and Editor Integration
* fully qualified name: `vac:nim:ift:2026q1-nim-core-libs:language-server-editor-integration`
* fully qualified name: `ift-ts:nim:ift:2026q1-nim-core-libs:language-server-editor-integration`
* owner: Constantine
* status: not started
* start-date: 2026/02/14
@@ -75,7 +75,7 @@ These enhancements will enable JSON-RPC to be used efficiently for cross-thread
### Documentation
* fully qualified name: `vac:nim:ift:2026q1-nim-core-libs:docs`
* fully qualified name: `ift-ts:nim:ift:2026q1-nim-core-libs:docs`
* owner: Constantine
* status: not started
* start-date: 2026/01/01

4
content/nim/ift/2026q1-nimble.md
View File

@@ -8,7 +8,7 @@ draft: false
description: Nimble development.
---
`vac:nim:ift:2026q1-nimble`
`ift-ts:nim:ift:2026q1-nimble`
## Description
@@ -29,7 +29,7 @@ By the end of this quarter, we aim to have made significant progress on these fr
### Nimble 1.0.0
* fully qualified name: `vac:nim:ift:2026q1-nimble:nimble-1.0.0`
* fully qualified name: `ift-ts:nim:ift:2026q1-nimble:nimble-1.0.0`
* owner: jmgomez
* status: not started
* start-date: 2026/01/01

7
content/nim/index.md
View File

@@ -2,10 +2,10 @@
title: Nim Unit
tags:
- nim
- vac
- ift-ts
---
## `vac:nim:`
## `ift-ts:nim:`
---
@@ -14,8 +14,6 @@ tags:
## 2026q1
### `waku:`
* [[nim/waku/2026q1-waku-nimble-integration|waku-nimble-integration]]
### `nimbus:`
* [[nim/nimbus/2026q1-nimbus-nimble-integration|nimbus-nimble-integration]]
### `ift:`
@@ -23,6 +21,7 @@ tags:
* [[nim/ift/2026q1-nimble|nimble]]
### `logos:`
* [[nim/logos/2026q1-storage-nimble-integration|storage-nimble-integration]]
* [[nim/logos/2026q1-messaging-nimble-integration|messaging-nimble-integration]]
## 2025q4

44
content/nim/logos/2026q1-messaging-nimble-integration.md Normal file
View File

@@ -0,0 +1,44 @@
---
title: Messaging Nimble Integration
tags:
- "2026q1"
- "nim"
- "logos"
draft: false
description: Support the messaging team as they integrate Nimble into nim-messaging.
---
`ift-ts:nim:logos:2026q1-messaging-nimble-integration`
## Description
Support the messaging team as they integrate Nimble into nim-messaging, troubleshoot and fix integration mismatches, and document gaps for follow-up.
## Task List
### Messaging Nimble integration Support
* fully qualified name: `ift-ts:nim:logos:2026q1-messaging-nimble-integration:integration-support`
* owner: TBD
* status: not started
* start-date: 2026/01/01
* end-date: 2026/02/10
#### Description
Support the messaging team with fixing issues that come up during their Nimble -> messaging integration efforts.
#### Deliverables
- PRs/Issues/Docs/Reports
### Complete messaging Nimble integration
* fully qualified name: `ift-ts:nim:logos:2026q1-messaging-nimble-integration:complete-integration`
* owner: TBD
* status: not started
* start-date: 2026/02/10
* end-date: 2026/03/31
#### Description
Complete the integration of Nimble into messaging, if any tasks remain outstanding the messaging team did not complete yet.
#### Deliverables
- PRs/Issues/Docs/Reports

6
content/nim/logos/2026q1-storage-nimble-integration.md
View File

@@ -8,7 +8,7 @@ draft: false
description: Support the Logos team as they integrate Nimble into Logos Storage.
---
`vac:nim:logos:2026q1-storage-nimble-integration`
`ift-ts:nim:logos:2026q1-storage-nimble-integration`
## Description
Support the Logos Storage team as they integrate Nimble into Logos Storage, troubleshoot and fix integration mismatches, and document gaps for follow-up.
@@ -17,7 +17,7 @@ Support the Logos Storage team as they integrate Nimble into Logos Storage, trou
### Logos Storage Nimble integration Support
* fully qualified name: `vac:nim:logos:2026q1-storage-nimble-integration:integration-support`
* fully qualified name: `ift-ts:nim:logos:2026q1-storage-nimble-integration:integration-support`
* owner: TBD
* status: not started
* start-date: 2026/01/01
@@ -31,7 +31,7 @@ Support the Logos Storage team with fixing issues that come up during their Nimb
### Complete Logos Storage Nimble integration
* fully qualified name: `vac:nim:logos:2026q1-storage-nimble-integration:complete-integration`
* fully qualified name: `ift-ts:nim:logos:2026q1-storage-nimble-integration:complete-integration`
* owner: TBD
* status: not started
* start-date: 2026/02/10

4
content/nim/nimbus/2026q1-nimbus-nimble-integration.md
View File

@@ -8,7 +8,7 @@ draft: false
description: Support the Nimbus team as they integrate Nimble into Nimbus.
---
`vac:nim:nimbus:2026q1-nimbus-nimble-integration`
`ift-ts:nim:nimbus:2026q1-nimbus-nimble-integration`
## Description
Support the Nimbus team as they integrate Nimble into Nimbus, troubleshoot and fix integration mismatches, and document gaps for follow-up.
@@ -17,7 +17,7 @@ Support the Nimbus team as they integrate Nimble into Nimbus, troubleshoot and f
### Nimbus Nimble integration
* fully qualified name: `vac:nim:nimbus:2026q1-nimbus-nimble-integration:integration`
* fully qualified name: `ift-ts:nim:nimbus:2026q1-nimbus-nimble-integration:integration`
* owner: TBD
* status: not started
* start-date: 2026/01/01

44
content/nim/waku/2026q1-waku-nimble-integration.md
View File

@@ -1,44 +0,0 @@
---
title: Waku Nimble Integration
tags:
- "2026q1"
- "nim"
- "waku"
draft: false
description: Support the Waku team as they integrate Nimble into Nwaku.
---
`vac:nim:waku:2026q1-waku-nimble-integration`
## Description
Support the Waku team as they integrate Nimble into Nwaku, troubleshoot and fix integration mismatches, and document gaps for follow-up.
## Task List
### Waku Nimble integration Support
* fully qualified name: `vac:nim:waku:2026q1-waku-nimble-integration:integration-support`
* owner: TBD
* status: not started
* start-date: 2026/01/01
* end-date: 2026/02/10
#### Description
Support the Waku team with fixing issues that come up during their Nimble -> Waku integration efforts.
#### Deliverables
- PRs/Issues/Docs/Reports
### Complete Waku Nimble integration
* fully qualified name: `vac:nim:waku:2026q1-waku-nimble-integration:complete-integration`
* owner: TBD
* status: not started
* start-date: 2026/02/10
* end-date: 2026/03/31
#### Description
Complete the integration of Nimble into Waku, if any tasks remain outstanding the Waku team did not complete yet.
#### Deliverables
- PRs/Issues/Docs/Reports

8
content/p2p/ift/2026q1-nimlibp2p-cbindings.md
View File

@@ -10,12 +10,12 @@ description: Provide c-bindings for nim-libp2p
---
`vac:p2p:ift:2026q1-nimlibp2p-cbindings`
`ift-ts:p2p:ift:2026q1-nimlibp2p-cbindings`
Continue exposing key nim-libp2p functionality via c-bindings to enables downstream projects like logoscore to embed libp2p functionality directly.
## Description
Continue the work started in `vac:p2p:ift:2026q1-nimlibp2p-cbindings` by exposing nim-libp2p functionality via a c static library, enabling external projects to integrate without depending on nim toolchains. Develop a logos core module that uses these bindings
Continue the work started in `ift-ts:p2p:ift:2026q1-nimlibp2p-cbindings` by exposing nim-libp2p functionality via a c static library, enabling external projects to integrate without depending on nim toolchains. Develop a logos core module that uses these bindings
## Task List
@@ -24,7 +24,7 @@ TODO: move tasks that were not completed in 2026q1 here
### mix
* fully qualified name: `vac:p2p:ift:2026q1-nimlibp2p-cbindings:mix`
* fully qualified name: `ift-ts:p2p:ift:2026q1-nimlibp2p-cbindings:mix`
* owner: not assigned yet
* status: not started
* start-date: 2026/01/01
@@ -35,7 +35,7 @@ Extend c-bindings to expose Mix functionality.
Exported functions must include:
- Setting up nodes to be used for the Mix Path
- Choose whether exit node is destination or not
This task depends on `vac:p2p:ift:2026q1-nimlibp2p-cbindings:core` being implemented (interaction with streams)
This task depends on `ift-ts:p2p:ift:2026q1-nimlibp2p-cbindings:core` being implemented (interaction with streams)
#### Deliverables
- Updated c header + library with mix api

8
content/p2p/ift/2026q1-nimlibp2p-connection-management.md
View File

@@ -10,7 +10,7 @@ description: Improved connection management in nim-libp2p
---
`vac:p2p:ift:2026q1-nimlibp2p-connection-management`
`ift-ts:p2p:ift:2026q1-nimlibp2p-connection-management`
Improve nim-libp2p’s connection manager to provide hi/lo watermarks, score-driven pruning, decaying tags, and protected connections
@@ -22,7 +22,7 @@ The current connection manager is limited to cap total connections but doesn’t
## Task List
### Hi/Lo limits
* fully qualified name: `vac:p2p:ift:2026q1-nimlibp2p-connection-management:limits`
* fully qualified name: `ift-ts:p2p:ift:2026q1-nimlibp2p-connection-management:limits`
* owner: not assigned yet
* status: not started
* start-date: 2026/01/01
@@ -35,7 +35,7 @@ Implement a hi/lo watermark subsystem. When connections exceed the higher limit,
Hi-Lo watermark behavior for managing number of connections
### Connection score
* fully qualified name: `vac:p2p:ift:2026q1-nimlibp2p-connection-management:score`
* fully qualified name: `ift-ts:p2p:ift:2026q1-nimlibp2p-connection-management:score`
* owner: not assigned yet
* status: not started
* start-date: 2026/01/01
@@ -49,7 +49,7 @@ Implement a per-connection scoring system with static and ephemeral tags. Epheme
- Protected-peer mechanism with hard guarantees
### AutoPrune
* fully qualified name: `vac:p2p:ift:2026q1-nimlibp2p-connection-management:autoprune`
* fully qualified name: `ift-ts:p2p:ift:2026q1-nimlibp2p-connection-management:autoprune`
* owner: not assigned yet
* status: not started
* start-date: 2026/01/01

8
content/p2p/ift/2026q1-nimlibp2p-gossipsub-extensions.md
View File

@@ -10,7 +10,7 @@ description: GossipSub Extensions and Partial Messages
---
`vac:p2p:ift:2026q1-nimlibp2p-gossipsub-extensions`
`ift-ts:p2p:ift:2026q1-nimlibp2p-gossipsub-extensions`
## Description
@@ -19,7 +19,7 @@ This commitment focuses on implementing [Gossipsub v1.3 - Extensions control mes
## Task List
### Implement Gossipsub Extensions support
* fully qualified name: `vac:p2p:ift:2026q1-nimlibp2p-gossipsub-extensions:extensions`
* fully qualified name: `ift-ts:p2p:ift:2026q1-nimlibp2p-gossipsub-extensions:extensions`
* owner: not assigned yet
* status: not started
* start-date: 2026/01/01
@@ -35,7 +35,7 @@ This commitment focuses on implementing [Gossipsub v1.3 - Extensions control mes
- Test Extension implemented (optionally enabled via compile time flag)
### Implement Gossipsub Partial Messages Extension
* fully qualified name: `vac:p2p:ift:2026q1-nimlibp2p-gossipsub-extensions:partial-messages`
* fully qualified name: `ift-ts:p2p:ift:2026q1-nimlibp2p-gossipsub-extensions:partial-messages`
* owner: not assigned yet
* status: not started
* start-date: 2026/01/01
@@ -51,7 +51,7 @@ This commitment focuses on implementing [Gossipsub v1.3 - Extensions control mes
### Change Gossipsub 1.4 to an extension
* fully qualified name: `vac:p2p:ift:2026q1-nimlibp2p-gossipsub-extensions:1-4-extension`
* fully qualified name: `ift-ts:p2p:ift:2026q1-nimlibp2p-gossipsub-extensions:1-4-extension`
* owner: not assigned yet
* status: not started
* start-date: 2026/01/01

4
content/p2p/ift/2026q1-nimlibp2p-logos-core.md
View File

@@ -10,7 +10,7 @@ description: Logos Core module for libp2p
---
`vac:p2p:ift:2026q1-nimlibp2p-logos-core`
`ift-ts:p2p:ift:2026q1-nimlibp2p-logos-core`
Continue exposing key nim-libp2p functionality via c-bindings to enables downstream projects like logoscore to embed libp2p functionality directly.
@@ -21,7 +21,7 @@ Using nim-libp2p's c-bindings develop logos-core modules that would let libp2p f
### logos module
* fully qualified name: `vac:p2p:ift:2026q1-nimlibp2p-logos-core:core`
* fully qualified name: `ift-ts:p2p:ift:2026q1-nimlibp2p-logos-core:core`
* owner: not assigned yet
* status: not started
* start-date: 2026/01/01

6
content/p2p/ift/2026q1-nimlibp2p-maintenance.md
View File

@@ -10,7 +10,7 @@ description: Maintain nim-libp2p through improvements, bug fixes, and user suppo
---
`vac:p2p:ift:2026q1-nimlibp2p-maintenance`
`ift-ts:p2p:ift:2026q1-nimlibp2p-maintenance`
Maintain nim-libp2p through improvements, bug fixes, and user support
@@ -26,7 +26,7 @@ ensuring that nim-libp2p remains functional and usable for its primary users —
### Maintenance
* fully qualified name: `vac:p2p:ift:2026q1-nimlibp2p-maintenance:maintenance`
* fully qualified name: `ift-ts:p2p:ift:2026q1-nimlibp2p-maintenance:maintenance`
* owner: rramos
* status: not started
* start-date: 2026/01/01
@@ -40,7 +40,7 @@ Maintain [nim-libp2p](https://github.com/vacp2p/nim-libp2p) repository via impro
### Kademlia Interop tests
* fully qualified name: `vac:p2p:ift:2026q1-nimlibp2p-maintenance:kademlia-interop-tests`
* fully qualified name: `ift-ts:p2p:ift:2026q1-nimlibp2p-maintenance:kademlia-interop-tests`
* owner: rramos
* status: not started
* start-date: 2026/01/01

4
content/p2p/ift/2026q1-nimlibp2p-universal-connectivity-app.md
View File

@@ -10,7 +10,7 @@ description: Universal connectivity app
---
`vac:p2p:ift:2026q1-nimlibp2p-universal-connectivity-app`
`ift-ts:p2p:ift:2026q1-nimlibp2p-universal-connectivity-app`
Extend universal connectivity app features
@@ -21,7 +21,7 @@ Extend the universal connectivity app by adding quic support and kademlia dht to
## Task List
### Kad-DHT
* fully qualified name: `vac:p2p:ift:2026q1-nimlibp2p-universal-connectivity-app:kad-dht`
* fully qualified name: `ift-ts:p2p:ift:2026q1-nimlibp2p-universal-connectivity-app:kad-dht`
* owner: gabe
* status: not started
* start-date: 2026/01/01

12
content/p2p/ift/2026q1-nimlibp2p-webtransport.md
View File

@@ -10,7 +10,7 @@ description: Add webtransport support to nim-libp2p
---
`vac:p2p:ift:2026q1-nimlibp2p-webtransport`
`ift-ts:p2p:ift:2026q1-nimlibp2p-webtransport`
Implement WebTransport support in nim-libp2p, enabling browser/server bidirectional streams via h3+quic. built atop nim-lsquic, extending its current quic-only integration.
@@ -23,7 +23,7 @@ This is done by using ls-quic which nim-libp2p already uses for quic transport
## Task List
### Http3 engine
* fully qualified name: `vac:p2p:ift:2026q1-nimlibp2p-webtransport:http3-engine`
* fully qualified name: `ift-ts:p2p:ift:2026q1-nimlibp2p-webtransport:http3-engine`
* owner: not assigned yet
* status: not started
* start-date: 2026/01/01
@@ -36,7 +36,7 @@ Extend nim-lsquic bindings to support acting as a proper http3 engine. enable co
- New h3-capable initialization api in nim-lsquic.
### Client
* fully qualified name: `vac:p2p:ift:2026q1-nimlibp2p-webtransport:client`
* fully qualified name: `ift-ts:p2p:ift:2026q1-nimlibp2p-webtransport:client`
* owner: not assigned yet
* status: not started
* start-date: 2026/01/01
@@ -49,7 +49,7 @@ Implement client-side webtransport session establishment
Client side functionality that allows establishing a connection via webtransport
### Server
* fully qualified name: `vac:p2p:ift:2026q1-nimlibp2p-webtransport:server`
* fully qualified name: `ift-ts:p2p:ift:2026q1-nimlibp2p-webtransport:server`
* owner: not assigned yet
* status: not started
* start-date: 2026/01/01
@@ -63,7 +63,7 @@ Server side functionality that allows accepting connections via webtransport
### Transport
* fully qualified name: `vac:p2p:ift:2026q1-nimlibp2p-webtransport:transport`
* fully qualified name: `ift-ts:p2p:ift:2026q1-nimlibp2p-webtransport:transport`
* owner: not assigned yet
* status: not started
* start-date: 2026/01/01
@@ -78,7 +78,7 @@ webtransport sessions and streams.
A libp2p transport that allows web clients to communicate with nim-libp2p nodes via WebTransport
### Interop
* fully qualified name: `vac:p2p:ift:2026q1-nimlibp2p-webtransport:interop`
* fully qualified name: `ift-ts:p2p:ift:2026q1-nimlibp2p-webtransport:interop`
* owner: not assigned yet
* status: not started
* start-date: 2026/01/01

4
content/p2p/index.md
View File

@@ -2,7 +2,7 @@
title: P2P Service Unit
tags:
- p2p
- vac
- ift-ts
---
@@ -14,7 +14,7 @@ Major future work items on nim-libp2p (also beyond this reporting period are cap
[[p2p/preview|Roadmap Preview]]
## 2026q1 `vac:p2p:`
## 2026q1 `ift-ts:p2p:`
### `ift:`
* [[p2p/ift/2026q1-nimlibp2p-cbindings|nimlibp2p-cbindings]]

8
content/qa/anoncomms/2026q1-anoncomms-testing.md
View File

@@ -8,7 +8,7 @@ draft: false
description: Expand QA coverage for anoncomms crypto and consensus components with negative-path and error-handling tests.
---
`vac:qa:anoncomms:2026q1-anoncomms-testing`
`ift-ts:qa:anoncomms:2026q1-anoncomms-testing`
## Description
@@ -24,7 +24,7 @@ Baseline test suites and file entry points for onboarding:
### Zerokit RLN negative-path hardening
* fully qualified name: `vac:qa:anoncomms:2026q1-anoncomms-testing:rln-negative-paths`
* fully qualified name: `ift-ts:qa:anoncomms:2026q1-anoncomms-testing:rln-negative-paths`
* owner: TBD
* status: not started
* start-date: 2026/01/01
@@ -49,7 +49,7 @@ Baseline test suites and file entry points for onboarding:
### Zerokit serialization and FFI error handling
* fully qualified name: `vac:qa:anoncomms:2026q1-anoncomms-testing:serialization-ffi-errors`
* fully qualified name: `ift-ts:qa:anoncomms:2026q1-anoncomms-testing:serialization-ffi-errors`
* owner: TBD
* status: not started
* start-date: 2026/02/01
@@ -71,7 +71,7 @@ Baseline test suites and file entry points for onboarding:
### Hashgraph-like consensus negative tests
* fully qualified name: `vac:qa:anoncomms:2026q1-anoncomms-testing:hashgraph-negative-tests`
* fully qualified name: `ift-ts:qa:anoncomms:2026q1-anoncomms-testing:hashgraph-negative-tests`
* owner: TBD
* status: not started
* start-date: 2026/02/15

18
content/qa/vac/2026q1-nim-libp2p-testing.md → content/qa/ift/2026q1-nim-libp2p-testing.md
View File

@@ -3,13 +3,13 @@ title: Nim Libp2p Testing
tags:
- "2026q1"
- "qa"
- "vac"
- "ift"
draft: false
description: Expand nim-libp2p testing coverage with focus on new protocols, test plans, and stability improvements.
---
`vac:qa:vac:2026q1-nim-libp2p-testing`
`ift-ts:qa:ift:2026q1-nim-libp2p-testing`
## Description
Expand nim-libp2p testing coverage, documentation, and tooling with focus on new features under development.
@@ -20,7 +20,7 @@ Extend coverage for Mix, Kad DHT, Autotls, Identify/Push and Connectivity protoc
### Test Plans
* fully qualified name: `vac:qa:vac:2026q1-nim-libp2p-testing:test-plans`
* fully qualified name: `ift-ts:qa:ift:2026q1-nim-libp2p-testing:test-plans`
* owner: radek
* status: not started
* start-date: 2026/01/01
@@ -37,7 +37,7 @@ Develop test plans for features currently under development:
### Mix Protocol Testing
* fully qualified name: `vac:qa:vac:2026q1-nim-libp2p-testing:mix`
* fully qualified name: `ift-ts:qa:ift:2026q1-nim-libp2p-testing:mix`
* owner: radek
* status: not started
* start-date: 2026/01/01
@@ -51,7 +51,7 @@ Implement unit and integration tests for the Mix protocol.
### Kad DHT Protocol Testing
* fully qualified name: `vac:qa:vac:2026q1-nim-libp2p-testing:kad-dht`
* fully qualified name: `ift-ts:qa:ift:2026q1-nim-libp2p-testing:kad-dht`
* owner: radek
* status: not started
* start-date: 2026/01/25
@@ -65,7 +65,7 @@ Implement unit and integration tests for the Kad DHT protocol.
### Autotls Protocol Testing
* fully qualified name: `vac:qa:vac:2026q1-nim-libp2p-testing:autotls`
* fully qualified name: `ift-ts:qa:ift:2026q1-nim-libp2p-testing:autotls`
* owner: radek
* status: not started
* start-date: 2026/02/15
@@ -79,7 +79,7 @@ Implement unit and integration tests for the Autotls protocol.
### Identify/Push Protocol Testing
* fully qualified name: `vac:qa:vac:2026q1-nim-libp2p-testing:identify-push`
* fully qualified name: `ift-ts:qa:ift:2026q1-nim-libp2p-testing:identify-push`
* owner: radek
* status: not started
* start-date: 2026/03/01
@@ -94,7 +94,7 @@ covering peer identification, metadata exchange, push updates, and error handlin
### Connectivity Protocol Testing
* fully qualified name: `vac:qa:vac:2026q1-nim-libp2p-testing:connectivity`
* fully qualified name: `ift-ts:qa:ift:2026q1-nim-libp2p-testing:connectivity`
* owner: radek
* status: not started
* start-date: 2026/03/15
@@ -109,7 +109,7 @@ connection limits, peer lifecycle handling, and resilience under different netwo
### Interop Test Plans
* fully qualified name: `vac:qa:vac:2026q1-nim-libp2p-testing:interop-test-plans`
* fully qualified name: `ift-ts:qa:ift:2026q1-nim-libp2p-testing:interop-test-plans`
* owner: radek
* status: not started
* start-date: 2026/02/01

12
content/qa/index.md
View File

@@ -2,20 +2,20 @@
title: QA Service Unit
tags:
- qa
- vac
- ift-ts
---
[[qa/preview|Roadmap Preview]]
## 2026q1 `vac:qa:`
## 2026q1 `ift-ts:qa:`
---
### `vac:`
* [[qa/vac/2026q1-nim-libp2p-testing|nim-libp2p-testing ]]
### `ift`
* [[qa/ift/2026q1-nim-libp2p-testing|nim-libp2p-testing ]]
### `waku:`
* [[qa/waku/2026q1-waku-testing|waku-testing ]]
### `messaging:`
* [[qa/messaging/2026q1-messaging-testing|messaging-testing ]]
### `status:`
* [[qa/status/2026q1-status-go-functional-testing|status-go-functional-testing ]]

4
content/qa/keycard/2026q1-keycard-testing.md
View File

@@ -8,7 +8,7 @@ draft: false
description: Ensure quality of Keycard applications.
---
`vac:qa:keycard:2026q1-keycard-testing`
`ift-ts:qa:keycard:2026q1-keycard-testing`
## Description
Ensure quality of Keycard applications, in particular Keycard shell.
@@ -17,7 +17,7 @@ Ensure quality of Keycard applications, in particular Keycard shell.
### Keycard Shell Tests
* fully qualified name: `vac:qa:keycard:2026q1-keycard-testing:wallet-compatibilty`
* fully qualified name: `ift-ts:qa:keycard:2026q1-keycard-testing:wallet-compatibilty`
* owner: romanzac
* status: not started
* start-date: 2026/01/01

6
content/qa/logos/2026q1-logos-core.md
View File

@@ -10,7 +10,7 @@ description: Validate the first Logos Core iteration and stand up automated test
---
`vac:qa:logos:2026q1-logos-core`
`ift-ts:qa:logos:2026q1-logos-core`
## Description
@@ -20,7 +20,7 @@ Exercise the first iteration of Logos Core to understand stability, feature comp
### Evaluate and test first iteration of Logos Core
* fully qualified name: `vac:qa:logos:2026q1-logos-core:evaluate`
* fully qualified name: `ift-ts:qa:logos:2026q1-logos-core:evaluate`
* owner: egor
* status: not started
* start-date: 2026/03/01
@@ -38,7 +38,7 @@ Exercise the first iteration of Logos Core to understand stability, feature comp
### Establish automated testing framework
* fully qualified name: `vac:qa:logos:2026q1-logos-core:automation-framework`
* fully qualified name: `ift-ts:qa:logos:2026q1-logos-core:automation-framework`
* owner: egor
* status: not started
* start-date: 2026/03/15

61
content/qa/messaging/2026q1-messaging-testing.md Normal file
View File

@@ -0,0 +1,61 @@
---
title: Messaging Testing
tags:
- "2026q1"
- "qa"
- "messaging"
draft: false
description: Maintain and ensure the reliability of messaging tests.
---
`ift-ts:qa:messaging:2026q1-messaging-testing`
## Description
Ensure the ongoing reliability of the messaging by enhancing and maintaining existing testing frameworks.
This includes addressing regressions, adapting to changes in messaging components,
and applying minor improvements to keep the frameworks functional and effective.
## Task List
### Messaging Extended E2E Network Conditions Tests
* fully qualified name: `ift-ts:qa:messaging:2026q1-messaging-testing:network-conditions`
* owner: aya
* status: not started
* start date: 2026/01/01
* end date: 2026/02/15
#### Description
Extend messaging end-to-end tests with network condition scenarios (high latency, low bandwidth, packet loss) for up to 7 nodes.
#### Deliverables
- PRs and issues
### Maintenance
* fully qualified name: `ift-ts:qa:messaging:2026q1-messaging-testing:maintenance`
* owner: aya
* status: not started
* start-date: 2026/01/01
* end-date: 2026/03/31
#### Description
Ongoing maintenance of messaging testing frameworks.
#### Deliverables
- PRs and issues
### Messaging Sonda Tool extension
* fully qualified name: `ift-ts:qa:messaging:2026q1-messaging-testing:sonda-extension`
* owner: aya
* status: not started
* start date: 2026/02/15
* end date: 2026/03/31
#### Description
Extend Sonda tool to allow more advanced testing scenarios for the Store protocol, then add new advanced tests.
#### Deliverables
- PRs and issues

40
content/qa/status/2026q1-status-go-functional-testing.md
View File

@@ -8,7 +8,7 @@ draft: false
description: Enhance functional and e2e testing for status-go features by implementing tests using status-backend.
---
`vac:qa:status:2026q1-status-go-functional-testing`
`ift-ts:qa:status:2026q1-status-go-functional-testing`
## Description
Modernize the functional/e2e testing stack for status-go by cleaning up fixtures,
@@ -18,7 +18,7 @@ improving the Python SDK, and expanding test coverage as defined [here](https://
### Remove direct usage of Anvil pre-generated accounts
* fully qualified name: `vac:qa:status:2026q1-status-go-functional-testing:7086`
* fully qualified name: `ift-ts:qa:status:2026q1-status-go-functional-testing:7086`
* owner: egor
* status: not started
* start-date: 2026/01/19
@@ -32,7 +32,7 @@ Eliminate hardcoded Anvil accounts and switch to dynamically managed identities.
### Deploy contracts as part of `docker compose` pre-requisite
* fully qualified name: `vac:qa:status:2026q1-status-go-functional-testing:7087`
* fully qualified name: `ift-ts:qa:status:2026q1-status-go-functional-testing:7087`
* owner: egor
* status: not started
* start-date: 2026/02/02
@@ -46,7 +46,7 @@ Bundle contract deployment into the compose bootstrap to simplify test setup.
### Remove usage of `setup_backends` fixture approach
* fully qualified name: `vac:qa:status:2026q1-status-go-functional-testing:7088`
* fully qualified name: `ift-ts:qa:status:2026q1-status-go-functional-testing:7088`
* owner: egor
* status: not started
* start-date: 2026/02/16
@@ -60,7 +60,7 @@ Refactor tests to drop legacy `setup_backends` fixtures in favor of the new flow
### Extract `scan_waku_fleet.py` to a separate container, run as part of waku fleet compose
* fully qualified name: `vac:qa:status:2026q1-status-go-functional-testing:7089`
* fully qualified name: `ift-ts:qa:status:2026q1-status-go-functional-testing:7089`
* owner: egor
* status: not started
* start-date: 2026/03/02
@@ -74,7 +74,7 @@ Containerize the fleet scanner and integrate it into the compose workflow.
### Introduce `asyncio` into Python SDK
* fully qualified name: `vac:qa:status:2026q1-status-go-functional-testing:7090`
* fully qualified name: `ift-ts:qa:status:2026q1-status-go-functional-testing:7090`
* owner: roman
* status: not started
* start-date: 2026/01/05
@@ -88,7 +88,7 @@ Add asyncio primitives to the Python SDK to enable async test flows.
### Simplify `SignalClient`
* fully qualified name: `vac:qa:status:2026q1-status-go-functional-testing:7091`
* fully qualified name: `ift-ts:qa:status:2026q1-status-go-functional-testing:7091`
* owner: roman
* status: not started
* start-date: 2026/01/19
@@ -102,7 +102,7 @@ Reduce complexity in `SignalClient` to improve reliability and readability.
### Remove test classes inheritance to MessengerSteps
* fully qualified name: `vac:qa:status:2026q1-status-go-functional-testing:7098`
* fully qualified name: `ift-ts:qa:status:2026q1-status-go-functional-testing:7098`
* owner: roman
* status: not started
* start-date: 2026/02/02
@@ -116,7 +116,7 @@ Uncouple tests from MessengerSteps inheritance to simplify fixtures and setup.
### Cleanup and simplify Python SDK
* fully qualified name: `vac:qa:status:2026q1-status-go-functional-testing:7084`
* fully qualified name: `ift-ts:qa:status:2026q1-status-go-functional-testing:7084`
* owner: roman
* status: not started
* start-date: 2026/02/16
@@ -130,7 +130,7 @@ Perform broader cleanup of the Python SDK to reduce flakiness and maintenance ov
### Community Owner Token Functional Test
* fully qualified name: `vac:qa:status:2026q1-status-go-functional-testing:7128`
* fully qualified name: `ift-ts:qa:status:2026q1-status-go-functional-testing:7128`
* owner: egor
* status: not started
* start-date: 2026/01/19
@@ -144,7 +144,7 @@ Validate ownership flows for community owner tokens.
### Community Token Master Functional Test
* fully qualified name: `vac:qa:status:2026q1-status-go-functional-testing:7129`
* fully qualified name: `ift-ts:qa:status:2026q1-status-go-functional-testing:7129`
* owner: egor
* status: not started
* start-date: 2026/02/02
@@ -158,7 +158,7 @@ Cover token master responsibilities and guardrails.
### Community Admin Functional Test
* fully qualified name: `vac:qa:status:2026q1-status-go-functional-testing:7130`
* fully qualified name: `ift-ts:qa:status:2026q1-status-go-functional-testing:7130`
* owner: egor
* status: not started
* start-date: 2026/02/16
@@ -172,7 +172,7 @@ Ensure admin-level permissions behave as expected in communities.
### Community Ownership Transfer Functional Test
* fully qualified name: `vac:qa:status:2026q1-status-go-functional-testing:7131`
* fully qualified name: `ift-ts:qa:status:2026q1-status-go-functional-testing:7131`
* owner: egor
* status: not started
* start-date: 2026/03/02
@@ -186,7 +186,7 @@ Test community ownership transfer workflows and state transitions.
### Community Control Node Transfer Functional Test
* fully qualified name: `vac:qa:status:2026q1-status-go-functional-testing:7132`
* fully qualified name: `ift-ts:qa:status:2026q1-status-go-functional-testing:7132`
* owner: egor
* status: not started
* start-date: 2026/03/16
@@ -200,7 +200,7 @@ Verify control node transfer procedures for communities.
### Community-Level Permissions Functional Test
* fully qualified name: `vac:qa:status:2026q1-status-go-functional-testing:7133`
* fully qualified name: `ift-ts:qa:status:2026q1-status-go-functional-testing:7133`
* owner: egor
* status: not started
* start-date: 2026/03/09
@@ -214,7 +214,7 @@ Validate community-level permission rules and enforcement.
### Community Channel-Level Permissions Functional Test
* fully qualified name: `vac:qa:status:2026q1-status-go-functional-testing:7134`
* fully qualified name: `ift-ts:qa:status:2026q1-status-go-functional-testing:7134`
* owner: egor
* status: not started
* start-date: 2026/03/18
@@ -228,7 +228,7 @@ Test permissions at the channel level within communities.
### Implement ENS functional tests
* fully qualified name: `vac:qa:status:2026q1-status-go-functional-testing:7093`
* fully qualified name: `ift-ts:qa:status:2026q1-status-go-functional-testing:7093`
* owner: egor
* status: not started
* start-date: 2026/01/12
@@ -242,7 +242,7 @@ Create functional coverage for ENS integration paths.
### Expand nightly benchmarks
* fully qualified name: `vac:qa:status:2026q1-status-go-functional-testing:7094`
* fully qualified name: `ift-ts:qa:status:2026q1-status-go-functional-testing:7094`
* owner: egor
* status: not started
* start-date: 2026/02/02
@@ -256,7 +256,7 @@ Broaden nightly benchmark scenarios to track performance and regressions.
### Implement local notifications functional tests
* fully qualified name: `vac:qa:status:2026q1-status-go-functional-testing:7095`
* fully qualified name: `ift-ts:qa:status:2026q1-status-go-functional-testing:7095`
* owner: egor
* status: not started
* start-date: 2026/02/23
@@ -270,7 +270,7 @@ Add functional tests for local notification flows.
### Maintenance
* fully qualified name: `vac:qa:status:2026q1-status-go-functional-testing:maintenance`
* fully qualified name: `ift-ts:qa:status:2026q1-status-go-functional-testing:maintenance`
* owner: egor
* status: in progress (30%)
* start-date: 2026/01/01

16
content/qa/status/2026q1-status-qa-desktop.md
View File

@@ -8,7 +8,7 @@ draft: false
description: Status QA Desktop
---
`vac:qa:status:2026q1-status-qa-desktop`
`ift-ts:qa:status:2026q1-status-qa-desktop`
## Description
Collaborate with Status team to ensure that the Status Desktop app behaves as expected.
@@ -19,7 +19,7 @@ Oversee testing strategy around releases.
### Maintenance
* fully qualified name: `vac:qa:status:2026q1-status-qa-desktop:maintenance`
* fully qualified name: `ift-ts:qa:status:2026q1-status-qa-desktop:maintenance`
* owner: nastya
* status: not started
* start-date: 2026/01/01
@@ -36,7 +36,7 @@ Oversee testing strategy around releases.
### Release Testing
* fully qualified name: `vac:qa:status:2026q1-status-qa-desktop:release-testing`
* fully qualified name: `ift-ts:qa:status:2026q1-status-qa-desktop:release-testing`
* owner: nastya
* status: not started
* start-date: 2026/01/01
@@ -50,7 +50,7 @@ Oversee testing strategy around releases.
### Privacy Mode
* fully qualified name: `vac:qa:status:2026q1-status-qa-desktop:privacy-mode`
* fully qualified name: `ift-ts:qa:status:2026q1-status-qa-desktop:privacy-mode`
* owner: nastya
* status: not started
* start-date: 2026/01/01
@@ -65,7 +65,7 @@ Oversee testing strategy around releases.
### Dapp Browser
* fully qualified name: `vac:qa:status:2026q1-status-qa-desktop:dapp-browser`
* fully qualified name: `ift-ts:qa:status:2026q1-status-qa-desktop:dapp-browser`
* owner: nastya
* status: not started
* start-date: 2026/01/01
@@ -80,7 +80,7 @@ Oversee testing strategy around releases.
### Local Backup Opt-in
* fully qualified name: `vac:qa:status:2026q1-status-qa-desktop:local-backup-opt-in`
* fully qualified name: `ift-ts:qa:status:2026q1-status-qa-desktop:local-backup-opt-in`
* owner: nastya
* status: not started
* start-date: 2026/01/01
@@ -94,7 +94,7 @@ Oversee testing strategy around releases.
### External Activity
* fully qualified name: `vac:qa:status:2026q1-status-qa-desktop:external-activity`
* fully qualified name: `ift-ts:qa:status:2026q1-status-qa-desktop:external-activity`
* owner: nastya
* status: not started
* start-date: 2026/01/01
@@ -108,7 +108,7 @@ Oversee testing strategy around releases.
### Emoji Reactions
* fully qualified name: `vac:qa:status:2026q1-status-qa-desktop:emoji-reactions`
* fully qualified name: `ift-ts:qa:status:2026q1-status-qa-desktop:emoji-reactions`
* owner: nastya
* status: not started
* start-date: 2026/01/01

16
content/qa/status/2026q1-status-qa-mobile.md
View File

@@ -10,7 +10,7 @@ description: Status QA Mobile
---
`vac:qa:status:2026q1-status-qa-mobile`
`ift-ts:qa:status:2026q1-status-qa-mobile`
## Description
@@ -32,7 +32,7 @@ Continue building mobile/tablet test automation coverage for the Status app.
### Wallet test expansion
- fully qualified name: `vac:qa:status:2026q1-status-qa-mobile:test-wallet`
- fully qualified name: `ift-ts:qa:status:2026q1-status-qa-mobile:test-wallet`
- owner: magnus
- status: not started
- start-date: 2026/01/01
@@ -50,7 +50,7 @@ Round out wallet automation to cover account edit, restart, receive, and setting
### iOS testing pilot
- fully qualified name: `vac:qa:status:2026q1-status-qa-mobile:ios-pilot`
- fully qualified name: `ift-ts:qa:status:2026q1-status-qa-mobile:ios-pilot`
- owner: magnus
- status: not started
- start-date: 2026/01/20
@@ -66,7 +66,7 @@ Investigate feasibility of adding iOS coverage to framework.
### Messaging 1x1 additional features
- fully qualified name: `vac:qa:status:2026q1-status-qa-mobile:test-messaging-1x1`
- fully qualified name: `ift-ts:qa:status:2026q1-status-qa-mobile:test-messaging-1x1`
- owner: magnus
- status: not started
- start-date: 2026/02/01
@@ -84,7 +84,7 @@ Bring the 1x1 messaging test to desktop parity, including edit/reply/react, medi
### Messaging group chat
- fully qualified name: `vac:qa:status:2026q1-status-qa-mobile:test-messaging-group`
- fully qualified name: `ift-ts:qa:status:2026q1-status-qa-mobile:test-messaging-group`
- owner: magnus
- status: not started
- start-date: 2026/02/15
@@ -102,7 +102,7 @@ Stand up the first 3-device group chat test covering Activity Center acceptance,
### Communities foundation
- fully qualified name: `vac:qa:status:2026q1-status-qa-mobile:test-communities`
- fully qualified name: `ift-ts:qa:status:2026q1-status-qa-mobile:test-communities`
- owner: magnus
- status: not started
- start-date: 2026/03/01
@@ -120,7 +120,7 @@ Lay the groundwork for communities tests with page objects and a basic create/in
### Maintenance
- fully qualified name: `vac:qa:status:2026q1-status-qa-mobile:maintenance`
- fully qualified name: `ift-ts:qa:status:2026q1-status-qa-mobile:maintenance`
- owner: magnus
- status: not started
- start-date: 2026/01/01
@@ -137,7 +137,7 @@ Keep the framework healthy while the app changes.
### Release testing
- fully qualified name: `vac:qa:status:2026q1-status-qa-mobile:release-testing`
- fully qualified name: `ift-ts:qa:status:2026q1-status-qa-mobile:release-testing`
- owner: magnus
- status: not started
- start-date: 2026/01/01

61
content/qa/waku/2026q1-waku-testing.md
View File

@@ -1,61 +0,0 @@
---
title: Waku Testing
tags:
- "2026q1"
- "qa"
- "waku"
draft: false
description: Maintain and ensure the reliability of Waku tests.
---
`vac:qa:waku:2026q1-waku-testing`
## Description
Ensure the ongoing reliability of the Waku by enhancing and maintaining existing testing frameworks.
This includes addressing regressions, adapting to changes in waku components,
and applying minor improvements to keep the frameworks functional and effective.
## Task List
### Waku Extended E2E Network Conditions Tests
* fully qualified name: `vac:qa:waku:2026q1-waku-testing:network-conditions`
* owner: aya
* status: not started
* start date: 2026/01/01
* end date: 2026/02/15
#### Description
Extend Waku end-to-end tests with network condition scenarios (high latency, low bandwidth, packet loss) for up to 7 nodes.
#### Deliverables
- PRs and issues
### Maintenance
* fully qualified name: `vac:qa:waku:2026q1-waku-testing:maintenance`
* owner: aya
* status: not started
* start-date: 2026/01/01
* end-date: 2026/03/31
#### Description
Ongoing maintenance of Waku testing frameworks.
#### Deliverables
- PRs and issues
### Waku Sonda Tool extension
* fully qualified name: `vac:qa:waku:2026q1-waku-testing:sonda-extension`
* owner: aya
* status: not started
* start date: 2026/02/15
* end date: 2026/03/31
#### Description
Extend Sonda tool to allow more advanced testing scenarios for the Store protocol, then add new advanced tests.
#### Deliverables
- PRs and issues

4
content/rfc/anoncomms/2026q1-rfc-iteration.md
View File

@@ -8,7 +8,7 @@ draft: false
description: "Iteration commitments generally comprise: through discussion and curation, support the process of auditing raw, draft, mature selected RFCs."
---
`vac:rfc:anoncomms:2026q1-rfc-iteration`
`ift-ts:rfc:anoncomms:2026q1-rfc-iteration`
Iteration commitments generally comprise:
through discussion and curation,
@@ -39,7 +39,7 @@ editorial work through previous and future RFCs to improve them
### WIP (new RFCs/Specs)
- fully qualified name: `vac:rfc:anoncomms:2026q1-rfc-iteration:wip`
- fully qualified name: `ift-ts:rfc:anoncomms:2026q1-rfc-iteration:wip`
- owner: cofson
- status: not started
- start-date: 2026/01/01

44
content/rfc/nomos/2026q1-rfc-iteration.md → content/rfc/blockchain/2026q1-rfc-iteration.md
View File

@@ -3,21 +3,21 @@ title: RFC Iteration
tags:
- 2026q1
- rfc
- nomos
- blockchain
draft: false
description: "Iteration commitments generally comprise: through discussion and curation, support the process of auditing raw, draft, mature selected Nomos RFCs."
description: "Iteration commitments generally comprise: through discussion and curation, support the process of auditing raw, draft, mature selected Blockchain RFCs."
---
`vac:rfc:nomos:2026q1-rfc-iteration`
`ift-ts:rfc:blockchain:2026q1-rfc-iteration`
Iteration commitments generally comprise:
through discussion and curation,
support the process of auditing raw, draft, mature selected Nomos RFCs.
support the process of auditing raw, draft, mature selected Blockchain RFCs.
## Description
This commitment supports the process of the writing raw RFCs,
from the existing documentation and specifications in Nomos team Notion.
from the existing documentation and specifications in Blockchain team Notion.
We will also include specification validation -
editorial work through previous and future RFCs to improve them
(identify edge cases for example)
@@ -39,119 +39,119 @@ The specifications in pipeline:
### Mantle
- fully qualified name: `vac:rfc:nomos:2026q1-rfc-iteration:mantle`
- fully qualified name: `ift-ts:rfc:blockchain:2026q1-rfc-iteration:mantle`
- owner: cofson
- status: not started
- start-date: 2026/01/16
- end-date: 2026/01/31
#### Description
Create the RFC for Mantle based on the Nomos raw spec that applies 1/COSS.
Create the RFC for Mantle based on the Blockchain raw spec that applies 1/COSS.
#### Deliverables
- PRs/Issues/Docs/Reports
### Proof of Leadership
- fully qualified name: `vac:rfc:nomos:2026q1-rfc-iteration:proof-of-leadership`
- fully qualified name: `ift-ts:rfc:blockchain:2026q1-rfc-iteration:proof-of-leadership`
- owner: cofson
- status: not started
- start-date: 2026/01/16
- end-date: 2026/01/31
#### Description
Create the RFC for the Proof of Leadership based on the Nomos raw spec that applies 1/COSS.
Create the RFC for the Proof of Leadership based on the Blockchain raw spec that applies 1/COSS.
#### Deliverables
- PRs/Issues/Docs/Reports
### Bedrock Genesis Block
- fully qualified name: `vac:rfc:nomos:2026q1-rfc-iteration:bedrock-genesis-block`
- fully qualified name: `ift-ts:rfc:blockchain:2026q1-rfc-iteration:bedrock-genesis-block`
- owner: cofson
- status: not started
- start-date: 2026/02/01
- end-date: 2026/02/15
#### Description
Create the RFC for the Bedrock Genesis Block based on the Nomos raw spec that applies 1/COSS.
Create the RFC for the Bedrock Genesis Block based on the Blockchain raw spec that applies 1/COSS.
#### Deliverables
- PRs/Issues/Docs/Reports
### Service Reward Distribution Protocol
- fully qualified name: `vac:rfc:nomos:2026q1-rfc-iteration:service-reward-distribution-protocol`
- fully qualified name: `ift-ts:rfc:blockchain:2026q1-rfc-iteration:service-reward-distribution-protocol`
- owner: cofson
- status: not started
- start-date: 2026/02/16
- end-date: 2026/02/28
#### Description
Create the RFC for the Service Reward Distribution Protocol based on the Nomos raw spec that applies 1/COSS.
Create the RFC for the Service Reward Distribution Protocol based on the Blockchain raw spec that applies 1/COSS.
#### Deliverables
- PRs/Issues/Docs/Reports
### Anonymous Leaders Reward Protocol
- fully qualified name: `vac:rfc:nomos:2026q1-rfc-iteration:anonymous-leaders-reward-protocol`
- fully qualified name: `ift-ts:rfc:blockchain:2026q1-rfc-iteration:anonymous-leaders-reward-protocol`
- owner: cofson
- status: not started
- start-date: 2026/03/01
- end-date: 2026/03/15
#### Description
Create the RFC for the Anonymous Leaders Reward Protocol based on the Nomos raw spec that applies 1/COSS.
Create the RFC for the Anonymous Leaders Reward Protocol based on the Blockchain raw spec that applies 1/COSS.
#### Deliverables
- PRs/Issues/Docs/Reports
### Wallet Technical Standard
- fully qualified name: `vac:rfc:nomos:2026q1-rfc-iteration:wallet-technical-standard`
- fully qualified name: `ift-ts:rfc:blockchain:2026q1-rfc-iteration:wallet-technical-standard`
- owner: cofson
- status: not started
- start-date: 2026/03/16
- end-date: 2026/03/31
#### Description
Create the RFC for the Anonymous Leaders Reward Protocol based on the Nomos raw spec that applies 1/COSS.
Create the RFC for the Anonymous Leaders Reward Protocol based on the Blockchain raw spec that applies 1/COSS.
#### Deliverables
- PRs/Issues/Docs/Reports
### Payload Formatting
- fully qualified name: `vac:rfc:nomos:2026q1-rfc-iteration:payload-formatting`
- fully qualified name: `ift-ts:rfc:blockchain:2026q1-rfc-iteration:payload-formatting`
- owner: cofson
- status: not started
- start-date: 2026/03/16
- end-date: 2026/03/31
#### Description
Create the RFC for the Payload Formatting based on the Nomos raw spec that applies 1/COSS.
Create the RFC for the Payload Formatting based on the Blockchain raw spec that applies 1/COSS.
#### Deliverables
- PRs/Issues/Docs/Reports
### Block Construction, Validation and Execution
- fully qualified name: `vac:rfc:nomos:2026q1-rfc-iteration:block-construction-validation-and-execution`
- fully qualified name: `ift-ts:rfc:blockchain:2026q1-rfc-iteration:block-construction-validation-and-execution`
- owner: cofson
- status: not started
- start-date: 2026/03/16
- end-date: 2026/03/31
#### Description
Create the RFC for the Block Construction, Validation and Execution based on the Nomos raw spec that applies 1/COSS.
Create the RFC for the Block Construction, Validation and Execution based on the Blockchain raw spec that applies 1/COSS.
#### Deliverables
- PRs/Issues/Docs/Reports
### Merge Open PRs
- fully qualified name: `vac:rfc:nomos:2026q1-rfc-iteration:merge-open-prs`
- fully qualified name: `ift-ts:rfc:blockchain:2026q1-rfc-iteration:merge-open-prs`
- owner: cofson
- status: not started
- start-date: 2026/01/01

16
content/rfc/index.md
View File

@@ -2,12 +2,12 @@
title: RFC Specifications Service Unit
tags:
- rfc
- vac
- ift-ts
---
[[rfc/preview|Roadmap Preview]]
## 2026q1 `vac:rfc:`
## 2026q1 `ift-ts:rfc:`
### `logos:`
@@ -16,14 +16,14 @@ tags:
### `anoncomms:`
* [[rfc/anoncomms/2026q1-rfc-iteration|rfc-iteration]]
### `waku:`
* [[rfc/waku/2026q1-rfc-iteration|rfc-iteration]]
### `messaging:`
* [[rfc/messaging/2026q1-rfc-iteration|rfc-iteration]]
### `nomos:`
* [[rfc/nomos/2026q1-rfc-iteration|rfc-iteration]]
### `blockchain:`
* [[rfc/blockchain/2026q1-rfc-iteration|rfc-iteration]]
### `codex:`
* [[rfc/codex/2026q1-rfc-iteration|rfc-iteration]]
### `storage:`
* [[rfc/storage/2026q1-rfc-iteration|rfc-iteration]]
## 2025q4 `vac:rfc:`

4
content/rfc/logos/2026q1-rfc-iteration.md
View File

@@ -8,7 +8,7 @@ draft: false
description: "Iteration commitments generally comprise: through discussion and curation, support the process of auditing raw, draft, mature selected Logos RFCs as well as upskilling efforts of our and other project teams."
---
`vac:rfc:logos:2026q1-rfc-iteration`
`ift-ts:rfc:logos:2026q1-rfc-iteration`
Iteration commitments generally comprise:
through discussion and curation,
@@ -32,7 +32,7 @@ This commitment also involves the upskilling of the RFC team,
### Upskilling the Team
- fully qualified name: `vac:rfc:logos:2026q1-rfc-iteration:upskilling-the-team`
- fully qualified name: `ift-ts:rfc:logos:2026q1-rfc-iteration:upskilling-the-team`
- owner: cofson
- status: not started
- start-date: 2026/01/01

34
content/rfc/waku/2026q1-rfc-iteration.md → content/rfc/messaging/2026q1-rfc-iteration.md
View File

@@ -3,16 +3,16 @@ title: RFC Iteration
tags:
- 2026q1
- rfc
- waku
- messaging
draft: false
description: "Iteration commitments generally comprise: through discussion and curation, support the process of auditing raw, draft, mature selected Waku RFCs."
description: "Iteration commitments generally comprise: through discussion and curation, support the process of auditing raw, draft, mature selected Messaging RFCs."
---
`vac:rfc:waku:2026q1-rfc-iteration`
`ift-ts:rfc:messaging:2026q1-rfc-iteration`
Iteration commitments generally comprise:
through discussion and curation,
support the process of auditing raw, draft, mature selected Waku RFCs.
support the process of auditing raw, draft, mature selected Messaging RFCs.
## Description
@@ -44,7 +44,7 @@ editorial work through previous and future RFCs to improve them
### 10/WAKU2
- Fully qualified name: `vac:rfc:waku:2026q1-rfc-iteration:10/WAKU2`
- Fully qualified name: `ift-ts:rfc:messaging:2026q1-rfc-iteration:10/WAKU2`
- Owner: jimstir
- Status: not started
- Start date: 2026/01/01
@@ -52,7 +52,7 @@ editorial work through previous and future RFCs to improve them
#### Description
Waku v2 is a family of modular peer-to-peer protocols for secure communication.
Messaging v2 is a family of modular peer-to-peer protocols for secure communication.
#### Deliverables
@@ -60,7 +60,7 @@ Waku v2 is a family of modular peer-to-peer protocols for secure communication.
### 12/WAKU2-FILTER
- Fully qualified name: `vac:rfc:waku:2026q1-rfc-iteration:12/WAKU2-FILTER`
- Fully qualified name: `ift-ts:rfc:messaging:2026q1-rfc-iteration:12/WAKU2-FILTER`
- Owner: jimstir
- Status: not started
- Start date: 2026/01/16
@@ -68,7 +68,7 @@ Waku v2 is a family of modular peer-to-peer protocols for secure communication.
#### Description
`WakuFilter` is a protocol that enables subscribing to messages that a peer
`MessagingFilter` is a protocol that enables subscribing to messages that a peer
receives.
#### Deliverables
@@ -77,7 +77,7 @@ receives.
### 13/WAKU2-STORE
- Fully qualified name: `vac:rfc:waku:2026q1-rfc-iteration:13/WAKU2-STORE`
- Fully qualified name: `ift-ts:rfc:messaging:2026q1-rfc-iteration:13/WAKU2-STORE`
- Owner: jimstir
- Status: not started
- Start date: 2026/02/01
@@ -94,7 +94,7 @@ querying messages received through the relay protocol and stored by other nodes.
### 14/WAKU2-MESSAGE
- Fully qualified name: `vac:rfc:waku:2026q1-rfc-iteration:14/WAKU2-MESSAGE`
- Fully qualified name: `ift-ts:rfc:messaging:2026q1-rfc-iteration:14/WAKU2-MESSAGE`
- Owner: jimstir
- Status: not started
- Start date: 2026/02/16
@@ -102,8 +102,8 @@ querying messages received through the relay protocol and stored by other nodes.
#### Description
Specification of the Waku v2 message format, used to encapsulate messages with
specific security goals and provide Whisper/Waku v1 backward compatibility.
Specification of the Messaging v2 message format, used to encapsulate messages with
specific security goals and provide Whisper/Messaging v1 backward compatibility.
#### Deliverables
@@ -111,7 +111,7 @@ specific security goals and provide Whisper/Waku v1 backward compatibility.
### 19/WAKU2-LIGHTPUSH
- Fully qualified name: `vac:rfc:waku:2026q1-rfc-iteration:19/WAKU2-LIGHTPUSH`
- Fully qualified name: `ift-ts:rfc:messaging:2026q1-rfc-iteration:19/WAKU2-LIGHTPUSH`
- Owner: jimstir
- Status: not started
- Start date: 2026/03/01
@@ -120,7 +120,7 @@ specific security goals and provide Whisper/Waku v1 backward compatibility.
#### Description
`WAKU2-LIGHTPUSH` is a protocol for light nodes with limited resources to
publish messages in the Waku network and receive confirmation of delivery.
publish messages in the Messaging network and receive confirmation of delivery.
#### Deliverables
@@ -128,7 +128,7 @@ publish messages in the Waku network and receive confirmation of delivery.
### 34/WAKU2-PEER-EXCHANGE
- Fully qualified name: `vac:rfc:waku:2026q1-rfc-iteration:34/WAKU2-PEER-EXCHANGE`
- Fully qualified name: `ift-ts:rfc:messaging:2026q1-rfc-iteration:34/WAKU2-PEER-EXCHANGE`
- Owner: jimstir
- Status: not started
- Start date: 2026/03/16
@@ -144,7 +144,7 @@ A peer discovery protocol for resource-restricted devices.
### 15/WAKU-BRIDGE
- Fully qualified name: `vac:rfc:waku:2026q1-rfc-iteration:15/WAKU-BRIDGE`
- Fully qualified name: `ift-ts:rfc:messaging:2026q1-rfc-iteration:15/WAKU-BRIDGE`
- Owner: jimstir
- Status: not started
- Start date: 2026/03/16
@@ -152,7 +152,7 @@ A peer discovery protocol for resource-restricted devices.
#### Description
A bridge between Waku v1 and Waku v2.
A bridge between Messaging v1 and Messaging v2.
#### Deliverables

20
content/rfc/codex/2026q1-rfc-iteration.md → content/rfc/storage/2026q1-rfc-iteration.md
View File

@@ -3,18 +3,18 @@ title: RFC Iteration
tags:
- 2026q1
- rfc
- codex
- storage
draft: false
description: "Iteration commitments generally comprise: through discussion and curation, support the process of auditing raw, draft, mature selected RFCs."
---
`vac:rfc:codex:2026q1-rfc-iteration`
`ift-ts:rfc:storage:2026q1-rfc-iteration`
Iteration commitments generally comprise:
through discussion and curation,
support the process of auditing raw, draft, mature selected RFCs.
This commitment covers this process for the following Codex RFCs:
This commitment covers this process for the following Storage RFCs:
Block Exchange, Slot builder, Prover, Community history,
DHT, Store, Merkle tree, Erasure Coding, Manifest.
@@ -36,19 +36,19 @@ editorial work through previous and future RFCs to improve them
### WIP (new RFCs/Specs)
- fully qualified name: `vac:rfc:codex:2026q1-rfc-iteration:wip`
- fully qualified name: `ift-ts:rfc:storage:2026q1-rfc-iteration:wip`
- owner: cofson
- status: not started
- start-date: 2026/01/01
- end-date: 2026/03/31
#### Description
Adding new Codex PRs - or Logos Storage - to work in the pipeline.
Adding new Storage PRs - or Logos Storage - to work in the pipeline.
#### Deliverables
- New specs (WIP)
### Merge Open PRs
- fully qualified name: `vac:rfc:codex:2026q1-rfc-iteration:merge-open-prs`
- fully qualified name: `ift-ts:rfc:storage:2026q1-rfc-iteration:merge-open-prs`
- owner: cofson
- status: not started
- start-date: 2026/01/01
@@ -65,9 +65,9 @@ Current pipeline:
- Community History: https://github.com/vacp2p/rfc-index/pull/214
- DHT: https://github.com/vacp2p/rfc-index/pull/210
- Slot Builder: https://github.com/vacp2p/rfc-index/pull/209
- Codex Store: https://github.com/vacp2p/rfc-index/pull/207
- Codex Prover: https://github.com/vacp2p/rfc-index/pull/205
- Codex Merkle Tree: https://github.com/vacp2p/rfc-index/pull/203
- Storage Store: https://github.com/vacp2p/rfc-index/pull/207
- Storage Prover: https://github.com/vacp2p/rfc-index/pull/205
- Storage Merkle Tree: https://github.com/vacp2p/rfc-index/pull/203
- Erasure Coding: https://github.com/vacp2p/rfc-index/pull/192
- Manifest: https://github.com/vacp2p/rfc-index/pull/191
#### Deliverables
@@ -75,7 +75,7 @@ Current pipeline:
### Workshop
- fully qualified name: `vac:rfc:codex:2026q1-rfc-iteration:workshop`
- fully qualified name: `ift-ts:rfc:storage:2026q1-rfc-iteration:workshop`
- owner: cofson
- status: not started
- start-date: 2026/01/01

14
content/web/ift/2026q1-demos.md
View File

@@ -8,7 +8,7 @@ draft: false
description: "Demonstration of completed work and presentations to showcase the Web team's deliverables, share progress with the entire organization, and gather feedback for continuous improvement."
---
`vac:web:ift:2026q1-demos`
`ift-ts:web:ift:2026q1-demos`
## Description
@@ -25,7 +25,7 @@ The demos commitment supports IFT's strategic objectives by:
### Biweekly 1 - IFT Townhall Demo
* fully qualified name: `vac:web:ift:2026q1-demos:biweekly-1-ift-townhall`
* fully qualified name: `ift-ts:web:ift:2026q1-demos:biweekly-1-ift-townhall`
* owner: JulesFiliot
* status: not started
* start-date: 2026/01/15
@@ -42,7 +42,7 @@ Prepare and deliver a biweekly demonstration of completed Web team work at the I
### Biweekly 2 - IFT Townhall Demo
* fully qualified name: `vac:web:ift:2026q1-demos:biweekly-2-ift-townhall`
* fully qualified name: `ift-ts:web:ift:2026q1-demos:biweekly-2-ift-townhall`
* owner: jinhojang6
* status: not started
* start-date: 2026/01/29
@@ -59,7 +59,7 @@ Prepare and deliver a biweekly demonstration of completed Web team work at the I
### Biweekly 3 - IFT Townhall Demo
* fully qualified name: `vac:web:ift:2026q1-demos:biweekly-3-ift-townhall`
* fully qualified name: `ift-ts:web:ift:2026q1-demos:biweekly-3-ift-townhall`
* owner: jkbktl
* status: not started
* start-date: 2026/02/12
@@ -76,7 +76,7 @@ Prepare and deliver a biweekly demonstration of completed Web team work at the I
### Biweekly 4 - IFT Townhall Demo
* fully qualified name: `vac:web:ift:2026q1-demos:biweekly-4-ift-townhall`
* fully qualified name: `ift-ts:web:ift:2026q1-demos:biweekly-4-ift-townhall`
* owner: JulesFiliot
* status: not started
* start-date: 2026/02/26
@@ -93,7 +93,7 @@ Prepare and deliver a biweekly demonstration of completed Web team work at the I
### Biweekly 5 - IFT Townhall Demo
* fully qualified name: `vac:web:ift:2026q1-demos:biweekly-5-ift-townhall`
* fully qualified name: `ift-ts:web:ift:2026q1-demos:biweekly-5-ift-townhall`
* owner: jinhojang6
* status: not started
* start-date: 2026/03/12
@@ -110,7 +110,7 @@ Prepare and deliver a biweekly demonstration of completed Web team work at the I
### Biweekly 6 - IFT Townhall Demo
* fully qualified name: `vac:web:ift:2026q1-demos:biweekly-6-ift-townhall`
* fully qualified name: `ift-ts:web:ift:2026q1-demos:biweekly-6-ift-townhall`
* owner: jkbktl
* status: not started
* start-date: 2026/03/26

8
content/web/ift/2026q1-maintenance.md
View File

@@ -8,7 +8,7 @@ draft: false
description: "Ongoing maintenance and support for previously delivered web projects across the IFT ecosystem, ensuring continued functionality, security, and performance optimization."
---
`vac:web:ift:2026q1-maintenance`
`ift-ts:web:ift:2026q1-maintenance`
## Description
@@ -24,7 +24,7 @@ The maintenance commitment supports IFT's strategic objectives by:
### Support & Questions
* fully qualified name: `vac:web:ift:2026q1-maintenance:support-questions`
* fully qualified name: `ift-ts:web:ift:2026q1-maintenance:support-questions`
* owner: JulesFiliot
* status: not started
* start-date: 2026/01/01
@@ -42,7 +42,7 @@ Respond to questions and support requests raised by stakeholders, users, and tea
### Issue Logging & Planning
* fully qualified name: `vac:web:ift:2026q1-maintenance:issue-logging`
* fully qualified name: `ift-ts:web:ift:2026q1-maintenance:issue-logging`
* owner: jinhojang6
* status: not started
* start-date: 2026/01/01
@@ -60,7 +60,7 @@ Log issues, bugs, and improvement requests on GitHub for planning and prioritiza
### Hotfixes
* fully qualified name: `vac:web:ift:2026q1-maintenance:hotfixes`
* fully qualified name: `ift-ts:web:ift:2026q1-maintenance:hotfixes`
* owner: jkbktl
* status: not started
* start-date: 2026/01/01

18
content/web/logos/2026q1-contribute-portal.md
View File

@@ -8,7 +8,7 @@ draft: false
description: "Development of Contribute Portal, a contribution hub that recognizes open source contributors and helps new developers make their first contributions to strengthen the Logos ecosystem."
---
`vac:web:logos:2026q1-contribute-portal`
`ift-ts:web:logos:2026q1-contribute-portal`
## Description
@@ -34,7 +34,7 @@ The Contribute Portal directly supports the quarterly KPIs by:
### Contribution Guidelines
* fully qualified name: `vac:web:logos:2026q1-contribute-portal:contribution-guidelines`
* fully qualified name: `ift-ts:web:logos:2026q1-contribute-portal:contribution-guidelines`
* owner: JulesFiliot
* status: not started
* start-date: 2026/02/26
@@ -51,7 +51,7 @@ Review and update contribution guidelines copy to ensure clarity and completenes
### Use BI team's Github Data
* fully qualified name: `vac:web:logos:2026q1-contribute-portal:bi-data`
* fully qualified name: `ift-ts:web:logos:2026q1-contribute-portal:bi-data`
* owner: jinhojang6
* status: not started
* start-date: 2026/03/05
@@ -69,7 +69,7 @@ Integrate BI team's GitHub data API to power contributor metrics and analytics.
### Leaderboard
* fully qualified name: `vac:web:logos:2026q1-contribute-portal:leaderboard`
* fully qualified name: `ift-ts:web:logos:2026q1-contribute-portal:leaderboard`
* owner: jkbktl
* status: not started
* start-date: 2026/03/05
@@ -86,7 +86,7 @@ Implement seasonal and all-time leaderboards with sorting that highlights high-i
### Tier & Scoring
* fully qualified name: `vac:web:logos:2026q1-contribute-portal:tier-scoring`
* fully qualified name: `ift-ts:web:logos:2026q1-contribute-portal:tier-scoring`
* owner: JulesFiliot
* status: not started
* start-date: 2026/03/12
@@ -104,7 +104,7 @@ Define the tier logic and scoring rules that map contributor activity into the r
### Proposals
* fully qualified name: `vac:web:logos:2026q1-contribute-portal:proposals`
* fully qualified name: `ift-ts:web:logos:2026q1-contribute-portal:proposals`
* owner: jinhojang6
* status: not started
* start-date: 2026/03/12
@@ -118,7 +118,7 @@ Launch the proposal submission flow so volunteers can pitch work or request supp
### Analytics
* fully qualified name: `vac:web:logos:2026q1-contribute-portal:analytics`
* fully qualified name: `ift-ts:web:logos:2026q1-contribute-portal:analytics`
* owner: jkbktl
* status: not started
* start-date: 2026/03/19
@@ -136,7 +136,7 @@ Set up Umami analytics integration for tracking portal usage and contributor eng
### Search
* fully qualified name: `vac:web:logos:2026q1-contribute-portal:search`
* fully qualified name: `ift-ts:web:logos:2026q1-contribute-portal:search`
* owner: JulesFiliot
* status: not started
* start-date: 2026/03/19
@@ -153,7 +153,7 @@ Implement search functionality on dedicated pages to allow users to search by Gi
### Sign-up form
* fully qualified name: `vac:web:logos:2026q1-contribute-portal:sign-up-form`
* fully qualified name: `ift-ts:web:logos:2026q1-contribute-portal:sign-up-form`
* owner: jinhojang6
* status: not started
* start-date: 2026/03/19

10
content/web/logos/2026q1-logos-forum.md
View File

@@ -8,7 +8,7 @@ draft: false
description: "Optimization of the Logos Forum experience to reduce onboarding friction, enable seamless story submission, and improve community contribution workflows."
---
`vac:web:logos:2026q1-logos-forum`
`ift-ts:web:logos:2026q1-logos-forum`
## Description
@@ -30,7 +30,7 @@ The Logos Forum optimization will support Logos' strategic objectives by:
### Custom Domain Email Support
* fully qualified name: `vac:web:logos:2026q1-logos-forum:custom-domain-email-support`
* fully qualified name: `ift-ts:web:logos:2026q1-logos-forum:custom-domain-email-support`
* owner: jinhojang6
* status: not started
* start-date: 2026/03/05
@@ -48,7 +48,7 @@ Allow registration with custom domain email addresses to remove barriers for use
### Cooldown Bypass System
* fully qualified name: `vac:web:logos:2026q1-logos-forum:cooldown-bypass-system`
* fully qualified name: `ift-ts:web:logos:2026q1-logos-forum:cooldown-bypass-system`
* owner: jkbktl
* status: not started
* start-date: 2026/03/12
@@ -66,7 +66,7 @@ Implement referral code on signup to bypass 24-hour cooldown period. If referral
### First Post Intro Flow
* fully qualified name: `vac:web:logos:2026q1-logos-forum:first-post-intro-flow`
* fully qualified name: `ift-ts:web:logos:2026q1-logos-forum:first-post-intro-flow`
* owner: JulesFiliot
* status: not started
* start-date: 2026/03/19
@@ -85,7 +85,7 @@ Enable new users to post their intro immediately, no matter what. Automatic flow
### Content Visibility
* fully qualified name: `vac:web:logos:2026q1-logos-forum:content-visibility`
* fully qualified name: `ift-ts:web:logos:2026q1-logos-forum:content-visibility`
* owner: jinhojang6
* status: not started
* start-date: 2026/03/19

12
content/web/logos/2026q1-logos-website.md
View File

@@ -8,7 +8,7 @@ draft: false
description: "Continued development and enhancement of the Logos website, building upon the comprehensive platform to improve user journeys, add new features, and optimize community engagement."
---
`vac:web:logos:2026q1-logos-website`
`ift-ts:web:logos:2026q1-logos-website`
## Description
@@ -24,7 +24,7 @@ The Logos website enhancement will support Logos' strategic objectives by:
### Contribute Portal
* fully qualified name: `vac:web:logos:2026q1-logos-website:contribute-portal`
* fully qualified name: `ift-ts:web:logos:2026q1-logos-website:contribute-portal`
* owner: jkbktl
* status: not started
* start-date: 2026/03/05
@@ -43,7 +43,7 @@ Integrate contribute portal leaderboard into the Logos website. Coordinate with
### Admin
* fully qualified name: `vac:web:logos:2026q1-logos-website:admin`
* fully qualified name: `ift-ts:web:logos:2026q1-logos-website:admin`
* owner: JulesFiliot
* status: not started
* start-date: 2026/03/12
@@ -61,7 +61,7 @@ Set up admin functionality for production release and integrate with infrastruct
### CRM
* fully qualified name: `vac:web:logos:2026q1-logos-website:crm`
* fully qualified name: `ift-ts:web:logos:2026q1-logos-website:crm`
* owner: jinhojang6
* status: not started
* start-date: 2026/03/12
@@ -79,7 +79,7 @@ Implement CRM functionality as specified in the design board and Discord discuss
### CMS/Sanity
* fully qualified name: `vac:web:logos:2026q1-logos-website:cms-sanity`
* fully qualified name: `ift-ts:web:logos:2026q1-logos-website:cms-sanity`
* owner: jkbktl
* status: not started
* start-date: 2026/03/19
@@ -96,7 +96,7 @@ Propose alternative to Sanity CMS for content management, enabling non-technical
### Selfhosting
* fully qualified name: `vac:web:logos:2026q1-logos-website:selfhosting`
* fully qualified name: `ift-ts:web:logos:2026q1-logos-website:selfhosting`
* owner: JulesFiliot
* status: not started
* start-date: 2026/03/19

4
content/web/status/2026q1-community-curation.md
View File

@@ -8,7 +8,7 @@ draft: false
description: "Migration of the Community Curation DApp to the status-web monorepo, enabling SNT holders to vote on which communities should be included in the Status Communities directory."
---
`vac:web:status:2026q1-community-curation`
`ift-ts:web:status:2026q1-community-curation`
## Description
@@ -40,7 +40,7 @@ The migration to the status-web monorepo will support Status' strategic objectiv
### Migration to status-web Monorepo
* fully qualified name: `vac:web:status:2026q1-community-curation:migration-to-status-web-monorepo`
* fully qualified name: `ift-ts:web:status:2026q1-community-curation:migration-to-status-web-monorepo`
* owner: JulesFiliot
* status: not started
* start-date: 2026/03/05

22
content/web/status/2026q1-sn-hub.md
View File

@@ -8,7 +8,7 @@ draft: false
description: "Continued development and enhancement of Status Network Hub, the main portal application for Status Network users to access all network features including staking, yield earning, bridging, and public funding pool tracking."
---
`vac:web:status:2026q1-sn-hub`
`ift-ts:web:status:2026q1-sn-hub`
## Description
@@ -24,7 +24,7 @@ The SN Hub development will support Status Network's strategic objectives by:
### SDK
* fully qualified name: `vac:web:status:2026q1-sn-hub:sdk`
* fully qualified name: `ift-ts:web:status:2026q1-sn-hub:sdk`
* owner: jkbktl
* status: not started
* start-date: 2026/01/01
@@ -43,7 +43,7 @@ Implement SDK functionality for claiming Karma, distributing Karma, and authenti
### Proxy API
* fully qualified name: `vac:web:status:2026q1-sn-hub:proxy-api`
* fully qualified name: `ift-ts:web:status:2026q1-sn-hub:proxy-api`
* owner: JulesFiliot
* status: not started
* start-date: 2026/01/01
@@ -61,7 +61,7 @@ Set up proxy API infrastructure including Status RPC proxy, Status Market proxy,
### Depositing
* fully qualified name: `vac:web:status:2026q1-sn-hub:depositing`
* fully qualified name: `ift-ts:web:status:2026q1-sn-hub:depositing`
* owner: jinhojang6
* status: not started
* start-date: 2026/01/01
@@ -79,7 +79,7 @@ Implement depositing functionality with GUSD vault integration.
### Karma Evolution
* fully qualified name: `vac:web:status:2026q1-sn-hub:karma-evolution`
* fully qualified name: `ift-ts:web:status:2026q1-sn-hub:karma-evolution`
* owner: jkbktl
* status: not started
* start-date: 2026/01/08
@@ -97,7 +97,7 @@ Implement Karma evolution system including Karma progress tracking and transacti
### NFT Evolution
* fully qualified name: `vac:web:status:2026q1-sn-hub:nft-evolution`
* fully qualified name: `ift-ts:web:status:2026q1-sn-hub:nft-evolution`
* owner: JulesFiliot
* status: not started
* start-date: 2026/01/08
@@ -115,7 +115,7 @@ Implement NFT evolution system based on contracts and Karma integration.
### Backend
* fully qualified name: `vac:web:status:2026q1-sn-hub:backend`
* fully qualified name: `ift-ts:web:status:2026q1-sn-hub:backend`
* owner: jinhojang6
* status: not started
* start-date: 2026/01/15
@@ -133,7 +133,7 @@ Implement backend functionality for leaderboard and app discovery features.
### QA
* fully qualified name: `vac:web:status:2026q1-sn-hub:qa`
* fully qualified name: `ift-ts:web:status:2026q1-sn-hub:qa`
* owner: jkbktl
* status: not started
* start-date: 2026/01/15
@@ -151,7 +151,7 @@ Define test cases for QA testing of SN Hub features and functionality.
### Selfhosting
* fully qualified name: `vac:web:status:2026q1-sn-hub:selfhosting`
* fully qualified name: `ift-ts:web:status:2026q1-sn-hub:selfhosting`
* owner: JulesFiliot
* status: not started
* start-date: 2026/01/15
@@ -169,7 +169,7 @@ Set up self-hosting infrastructure and deployment processes for SN Hub.
### Translations
* fully qualified name: `vac:web:status:2026q1-sn-hub:i18n`
* fully qualified name: `ift-ts:web:status:2026q1-sn-hub:i18n`
* owner: jinhojang6
* status: not started
* start-date: 2026/01/22
@@ -187,7 +187,7 @@ Implement internationalization (i18n) support for SN Hub to enable multi-languag
### SEO
* fully qualified name: `vac:web:status:2026q1-sn-hub:seo`
* fully qualified name: `ift-ts:web:status:2026q1-sn-hub:seo`
* owner: jkbktl
* status: not started
* start-date: 2026/01/22

10
content/web/status/2026q1-sn-website.md
View File

@@ -8,7 +8,7 @@ draft: false
description: "Development and optimization of the Status Network website to showcase network features, provide documentation, and support community engagement."
---
`vac:web:status:2026q1-sn-website`
`ift-ts:web:status:2026q1-sn-website`
## Description
@@ -24,7 +24,7 @@ The SN website development will support Status Network's strategic objectives by
### SEO
* fully qualified name: `vac:web:status:2026q1-sn-website:seo`
* fully qualified name: `ift-ts:web:status:2026q1-sn-website:seo`
* owner: JulesFiliot
* status: not started
* start-date: 2026/01/29
@@ -42,7 +42,7 @@ Implement SEO optimization for the Status Network website to improve search engi
### Translations
* fully qualified name: `vac:web:status:2026q1-sn-website:translations`
* fully qualified name: `ift-ts:web:status:2026q1-sn-website:translations`
* owner: jinhojang6
* status: not started
* start-date: 2026/01/29
@@ -60,7 +60,7 @@ Implement translations support with public contribution flow for community trans
### Analytics
* fully qualified name: `vac:web:status:2026q1-sn-website:analytics`
* fully qualified name: `ift-ts:web:status:2026q1-sn-website:analytics`
* owner: jkbktl
* status: not started
* start-date: 2026/02/05
@@ -78,7 +78,7 @@ Implement analytics with campaign tag management for tracking and measuring webs
### Selfhosting
* fully qualified name: `vac:web:status:2026q1-sn-website:selfhosting`
* fully qualified name: `ift-ts:web:status:2026q1-sn-website:selfhosting`
* owner: JulesFiliot
* status: not started
* start-date: 2026/02/05

4
content/web/status/2026q1-status-app.md
View File

@@ -8,7 +8,7 @@ draft: false
description: "Supporting continued development of Status App by ensuring web applications, interfaces, and extensions remain functional during native app upgrades, refactoring, and protocol improvements."
---
`vac:web:status:2026q1-status-app`
`ift-ts:web:status:2026q1-status-app`
## Description
@@ -24,7 +24,7 @@ The Status App web support will support Status' strategic objectives by:
### External Social Link Preview
* fully qualified name: `vac:web:status:2026q1-status-app:external-social-link-preview`
* fully qualified name: `ift-ts:web:status:2026q1-status-app:external-social-link-preview`
* owner: jkbktl
* status: not started
* start-date: 2026/02/26

26
content/web/status/2026q1-status-wallet-extension.md
View File

@@ -8,7 +8,7 @@ draft: false
description: "Continued development and enhancement of the browser wallet extension focused on trading and investor utility, featuring multi-chain swaps, portfolio management, and real-time token tracking."
---
`vac:web:status:2026q1-status-wallet-extension`
`ift-ts:web:status:2026q1-status-wallet-extension`
## Description
@@ -24,7 +24,7 @@ The Status Wallet Extension development will support Status' strategic objective
### Proxy API Rate Limiting
* fully qualified name: `vac:web:status:2026q1-status-wallet-extension:proxy-api-rate-limiting`
* fully qualified name: `ift-ts:web:status:2026q1-status-wallet-extension:proxy-api-rate-limiting`
* owner: jinhojang6
* status: not started
* start-date: 2026/02/05
@@ -42,7 +42,7 @@ Implement proxy API rate limiting to manage API usage and prevent abuse.
### QA Defining Test Cases Together
* fully qualified name: `vac:web:status:2026q1-status-wallet-extension:qa-defining-test-cases-together`
* fully qualified name: `ift-ts:web:status:2026q1-status-wallet-extension:qa-defining-test-cases-together`
* owner: jkbktl
* status: not started
* start-date: 2026/02/05
@@ -60,7 +60,7 @@ Collaborate with QA team to define comprehensive test cases for wallet extension
### Value Chart
* fully qualified name: `vac:web:status:2026q1-status-wallet-extension:value-chart`
* fully qualified name: `ift-ts:web:status:2026q1-status-wallet-extension:value-chart`
* owner: JulesFiliot
* status: not started
* start-date: 2026/02/12
@@ -78,7 +78,7 @@ Implement value chart functionality to display portfolio value over time.
### Hide Small Balances
* fully qualified name: `vac:web:status:2026q1-status-wallet-extension:hide-small-balances`
* fully qualified name: `ift-ts:web:status:2026q1-status-wallet-extension:hide-small-balances`
* owner: jinhojang6
* status: not started
* start-date: 2026/02/12
@@ -96,7 +96,7 @@ Implement feature to hide small token balances from the wallet view for cleaner
### LI.FI Swap Integration
* fully qualified name: `vac:web:status:2026q1-status-wallet-extension:lifi-swap-integration`
* fully qualified name: `ift-ts:web:status:2026q1-status-wallet-extension:lifi-swap-integration`
* owner: jkbktl
* status: not started
* start-date: 2026/02/12
@@ -114,7 +114,7 @@ Integrate LI.FI swap functionality to enable multi-chain token swaps within the
### Send NFT
* fully qualified name: `vac:web:status:2026q1-status-wallet-extension:send-nft`
* fully qualified name: `ift-ts:web:status:2026q1-status-wallet-extension:send-nft`
* owner: JulesFiliot
* status: not started
* start-date: 2026/02/19
@@ -132,7 +132,7 @@ Implement functionality to send NFTs from the wallet extension.
### Global Password
* fully qualified name: `vac:web:status:2026q1-status-wallet-extension:global-password`
* fully qualified name: `ift-ts:web:status:2026q1-status-wallet-extension:global-password`
* owner: jinhojang6
* status: not started
* start-date: 2026/02/19
@@ -150,7 +150,7 @@ Implement global password functionality for unified authentication across wallet
### Multi Account
* fully qualified name: `vac:web:status:2026q1-status-wallet-extension:multi-account`
* fully qualified name: `ift-ts:web:status:2026q1-status-wallet-extension:multi-account`
* owner: jkbktl
* status: not started
* start-date: 2026/02/26
@@ -168,7 +168,7 @@ Implement multi-account support to allow users to manage multiple accounts withi
### Multi Wallet
* fully qualified name: `vac:web:status:2026q1-status-wallet-extension:multi-wallet`
* fully qualified name: `ift-ts:web:status:2026q1-status-wallet-extension:multi-wallet`
* owner: JulesFiliot
* status: not started
* start-date: 2026/02/26
@@ -186,7 +186,7 @@ Implement multi-wallet support to allow users to connect and manage multiple wal
### Dapp Connection
* fully qualified name: `vac:web:status:2026q1-status-wallet-extension:dapp-connection`
* fully qualified name: `ift-ts:web:status:2026q1-status-wallet-extension:dapp-connection`
* owner: jinhojang6
* status: not started
* start-date: 2026/03/05
@@ -204,7 +204,7 @@ Implement dApp connection functionality to enable wallet extension to connect wi
### Hardware Wallets
* fully qualified name: `vac:web:status:2026q1-status-wallet-extension:hardware-wallets`
* fully qualified name: `ift-ts:web:status:2026q1-status-wallet-extension:hardware-wallets`
* owner: jkbktl
* status: not started
* start-date: 2026/03/05
@@ -222,7 +222,7 @@ Implement hardware wallet support with QR code-based connection and Keycard Shel
### Browser and System Notifications
* fully qualified name: `vac:web:status:2026q1-status-wallet-extension:browser-system-notifications`
* fully qualified name: `ift-ts:web:status:2026q1-status-wallet-extension:browser-system-notifications`
* owner: JulesFiliot
* status: not started
* start-date: 2026/03/12

10
content/web/status/2026q1-status-website.md
View File

@@ -8,7 +8,7 @@ draft: false
description: "Continued optimization and maintenance of the Status website with internationalization support and SEO improvements to enhance global accessibility and discoverability."
---
`vac:web:status:2026q1-status-website`
`ift-ts:web:status:2026q1-status-website`
## Description
@@ -24,7 +24,7 @@ The Status website optimization will support Status' strategic objectives by:
### SEO
* fully qualified name: `vac:web:status:2026q1-status-website:seo`
* fully qualified name: `ift-ts:web:status:2026q1-status-website:seo`
* owner: jinhojang6
* status: not started
* start-date: 2026/02/12
@@ -42,7 +42,7 @@ Implement SEO optimization for the Status website to improve search engine visib
### Translations
* fully qualified name: `vac:web:status:2026q1-status-website:translations`
* fully qualified name: `ift-ts:web:status:2026q1-status-website:translations`
* owner: jkbktl
* status: not started
* start-date: 2026/02/12
@@ -61,7 +61,7 @@ Implement translations support with design improvements, public contribution flo
### Copy Changes, Section Reduction
* fully qualified name: `vac:web:status:2026q1-status-website:copy-changes-section-reduction`
* fully qualified name: `ift-ts:web:status:2026q1-status-website:copy-changes-section-reduction`
* owner: JulesFiliot
* status: not started
* start-date: 2026/02/19
@@ -79,7 +79,7 @@ Update website copy and reduce sections to improve clarity and user experience.
### Selfhosting
* fully qualified name: `vac:web:status:2026q1-status-website:selfhosting`
* fully qualified name: `ift-ts:web:status:2026q1-status-website:selfhosting`
* owner: jinhojang6
* status: not started
* start-date: 2026/02/26

2
quartz.config.ts
View File

@@ -3,7 +3,7 @@ import * as Plugin from "./quartz/plugins"
const config: QuartzConfig = {
configuration: {
pageTitle: "Vac R&D Roadmaps and Reports",
pageTitle: "IFT-TS Roadmaps and Reports",
enableSPA: true,
enablePopovers: true,
defaultDateType: "modified",

2
tools/roadmap_validator/identity.py
View File

@@ -46,7 +46,7 @@ def derive_identity(path: Path) -> Tuple[Optional[CommitmentIdentity], List[Vali
quarter = match.group("quarter")
slug = match.group("slug")
expected_base = f"vac:{unit}:{area}:{quarter}-{slug}"
expected_base = f"ift-ts:{unit}:{area}:{quarter}-{slug}"
expected_tags = [quarter, unit, area]
expected_identifier = expected_base
identity = CommitmentIdentity(