mirror of
https://github.com/vacp2p/roadmap.git
synced 2026-01-08 21:27:58 -05:00
RFC Commitments proposal Q1 2026 (#342)
Co-authored-by: fbarbu15 <florin@status.im>
This commit is contained in:
Cofson
51
content/rfc/anoncomms/2026q1-rfc-iteration.md
Normal file
51
content/rfc/anoncomms/2026q1-rfc-iteration.md
Normal file
@@ -0,0 +1,51 @@
|
||||
---
|
||||
title: RFC Iteration
|
||||
tags:
|
||||
- 2026q1
|
||||
- rfc
|
||||
- anoncomms
|
||||
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`
|
||||
|
||||
Iteration commitments generally comprise:
|
||||
through discussion and curation,
|
||||
support the process of auditing raw, draft, mature selected RFCs.
|
||||
|
||||
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 Anoncomms RFCs: WIP.
|
||||
|
||||
## Description
|
||||
|
||||
This commitment supports the process of the choosing which raw RFCs,
|
||||
from the existing documentation to be put in pipeline to be written or updated. This also includes the process of driving of the merge of open PRs and refining existing raw RFCs into more mature ones.
|
||||
|
||||
This commitment supports the audit of the following mature specifications,
|
||||
which are either in draft or raw states:
|
||||
- WIP
|
||||
|
||||
|
||||
We will also include specification validation -
|
||||
editorial work through previous and future RFCs to improve them
|
||||
(identify edge cases for example)
|
||||
|
||||
## Task List
|
||||
|
||||
### WIP (new RFCs/Specs)
|
||||
|
||||
- fully qualified name: `vac:rfc:anoncomms:2026q1-rfc-iteration:wip`
|
||||
- owner: cofson
|
||||
- status: not started
|
||||
- start-date: 2026/01/01
|
||||
- end-date: 2026/03/31
|
||||
#### Description
|
||||
Adding new Anoncomms specifications to work in the pipeline.
|
||||
|
||||
#### Deliverables
|
||||
- New RFCs (WIP)
|
||||
92
content/rfc/codex/2026q1-rfc-iteration.md
Normal file
92
content/rfc/codex/2026q1-rfc-iteration.md
Normal file
@@ -0,0 +1,92 @@
|
||||
---
|
||||
title: RFC Iteration
|
||||
tags:
|
||||
- 2026q1
|
||||
- rfc
|
||||
- codex
|
||||
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`
|
||||
|
||||
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:
|
||||
Block Exchange, Slot builder, Prover, Community history,
|
||||
DHT, Store, Merkle tree, Erasure Coding, Manifest.
|
||||
|
||||
## Description
|
||||
|
||||
This commitment supports the process of the choosing which raw RFCs,
|
||||
from the existing documentation to be put in pipeline to be written or updated. This also includes the process of driving of the merge of open PRs and refining existing raw RFCs into more mature ones.
|
||||
|
||||
This commitment supports the audit of the following mature specifications,
|
||||
which are either in draft or raw states:
|
||||
- WIP
|
||||
|
||||
|
||||
We will also include specification validation -
|
||||
editorial work through previous and future RFCs to improve them
|
||||
(identify edge cases for example)
|
||||
|
||||
## Task List
|
||||
|
||||
### WIP (new RFCs/Specs)
|
||||
|
||||
- fully qualified name: `vac:rfc:codex: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.
|
||||
|
||||
#### Deliverables
|
||||
- New specs (WIP)
|
||||
### Merge Open PRs
|
||||
|
||||
- fully qualified name: `vac:rfc:codex:2026q1-rfc-iteration:merge-open-prs`
|
||||
- owner: cofson
|
||||
- status: not started
|
||||
- start-date: 2026/01/01
|
||||
- end-date: 2026/03/31
|
||||
|
||||
#### Description
|
||||
This task revolves around
|
||||
merging the existing open PRs,
|
||||
so that the process of merging PRs
|
||||
is as brief as possible.
|
||||
|
||||
Current pipeline:
|
||||
- Block Exchange (Improvement): https://github.com/vacp2p/rfc-index/pull/215
|
||||
- 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
|
||||
- Erasure Coding: https://github.com/vacp2p/rfc-index/pull/192
|
||||
- Manifest: https://github.com/vacp2p/rfc-index/pull/191
|
||||
#### Deliverables
|
||||
- Merged PRs
|
||||
|
||||
### Workshop
|
||||
|
||||
- fully qualified name: `vac:rfc:codex:2026q1-rfc-iteration:workshop`
|
||||
- owner: cofson
|
||||
- status: not started
|
||||
- start-date: 2026/01/01
|
||||
- end-date: 2026/03/31
|
||||
|
||||
#### Description
|
||||
Organize and hold a Spec Improvement Workshop,
|
||||
in order to improve the process of specification writing.
|
||||
|
||||
#### Deliverables
|
||||
- Presentation (potentially in multiple parts)
|
||||
- Recording(s)
|
||||
- Documentation
|
||||
- Support by the RFC team
|
||||
@@ -7,6 +7,24 @@ tags:
|
||||
|
||||
[[rfc/preview|Roadmap Preview]]
|
||||
|
||||
## 2026q1 `vac:rfc:`
|
||||
|
||||
|
||||
### `logos:`
|
||||
* [[rfc/logos/2026q1-rfc-iteration|rfc-iteration]]
|
||||
|
||||
### `anoncomms:`
|
||||
* [[rfc/anoncomms/2026q1-rfc-iteration|rfc-iteration]]
|
||||
|
||||
### `waku:`
|
||||
* [[rfc/waku/2026q1-rfc-iteration|rfc-iteration]]
|
||||
|
||||
### `nomos:`
|
||||
* [[rfc/nomos/2026q1-rfc-iteration|rfc-iteration]]
|
||||
|
||||
### `codex:`
|
||||
* [[rfc/codex/2026q1-rfc-iteration|rfc-iteration]]
|
||||
|
||||
## 2025q4 `vac:rfc:`
|
||||
|
||||
|
||||
|
||||
49
content/rfc/logos/2026q1-rfc-iteration.md
Normal file
49
content/rfc/logos/2026q1-rfc-iteration.md
Normal file
@@ -0,0 +1,49 @@
|
||||
---
|
||||
title: RFC Iteration
|
||||
tags:
|
||||
- 2026q1
|
||||
- rfc
|
||||
- logos
|
||||
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`
|
||||
|
||||
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.
|
||||
|
||||
## Description
|
||||
|
||||
This commitment supports the process of the writing raw RFCs,
|
||||
from the existing documentation and specifications.
|
||||
We will also include specification validation -
|
||||
editorial work through previous and future RFCs to improve them
|
||||
(identify edge cases for example)
|
||||
as well as making sure that the relevant document has enough information
|
||||
in order to ease the developer experience for coming developers.
|
||||
|
||||
This commitment also involves the upskilling of the RFC team,
|
||||
1 day weekly effort as well as helping other teams in their upskilling efforts.
|
||||
|
||||
## Task List
|
||||
|
||||
### Upskilling the Team
|
||||
|
||||
- fully qualified name: `vac:rfc:logos:2026q1-rfc-iteration:upskilling-the-team`
|
||||
- owner: cofson
|
||||
- status: not started
|
||||
- start-date: 2026/01/01
|
||||
- end-date: 2026/03/31
|
||||
|
||||
#### Description
|
||||
This task revolves around
|
||||
the effort of upskilling the team,
|
||||
so that we can provide better support to the other teams
|
||||
as well as understand and apply the IETF RFC process.
|
||||
|
||||
#### Deliverables
|
||||
- Weekly reports on lessons learned.
|
||||
- Applied practices on our RFC process.
|
||||
174
content/rfc/nomos/2026q1-rfc-iteration.md
Normal file
174
content/rfc/nomos/2026q1-rfc-iteration.md
Normal file
@@ -0,0 +1,174 @@
|
||||
---
|
||||
title: RFC Iteration
|
||||
tags:
|
||||
- 2026q1
|
||||
- rfc
|
||||
- nomos
|
||||
draft: false
|
||||
description: "Iteration commitments generally comprise: through discussion and curation, support the process of auditing raw, draft, mature selected Nomos RFCs."
|
||||
---
|
||||
|
||||
`vac:rfc:nomos:2026q1-rfc-iteration`
|
||||
|
||||
Iteration commitments generally comprise:
|
||||
through discussion and curation,
|
||||
support the process of auditing raw, draft, mature selected Nomos RFCs.
|
||||
|
||||
## Description
|
||||
|
||||
This commitment supports the process of the writing raw RFCs,
|
||||
from the existing documentation and specifications in Nomos team Notion.
|
||||
We will also include specification validation -
|
||||
editorial work through previous and future RFCs to improve them
|
||||
(identify edge cases for example)
|
||||
as well as making sure that the relevant document has enough information
|
||||
in order to ease the developer experience for coming developers.
|
||||
|
||||
The specifications in pipeline:
|
||||
- Mantle
|
||||
- Bedrock Genesis Block
|
||||
- Service Reward Distribution Protocol
|
||||
- Anonymous Leaders Reward Protocol
|
||||
- Wallet Technical Standard
|
||||
- Block Construction, Validation and Execution
|
||||
- Bedrock Architecture Overview *(to be confirmed)*
|
||||
- Proof of Leadership
|
||||
- Payload Formatting
|
||||
|
||||
## Task List
|
||||
|
||||
### Mantle
|
||||
|
||||
- fully qualified name: `vac:rfc:nomos: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.
|
||||
|
||||
#### Deliverables
|
||||
- PRs/Issues/Docs/Reports
|
||||
|
||||
### Proof of Leadership
|
||||
|
||||
- fully qualified name: `vac:rfc:nomos: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.
|
||||
|
||||
#### Deliverables
|
||||
- PRs/Issues/Docs/Reports
|
||||
|
||||
### Bedrock Genesis Block
|
||||
|
||||
- fully qualified name: `vac:rfc:nomos: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.
|
||||
|
||||
#### Deliverables
|
||||
- PRs/Issues/Docs/Reports
|
||||
|
||||
### Service Reward Distribution Protocol
|
||||
|
||||
- fully qualified name: `vac:rfc:nomos: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.
|
||||
|
||||
#### Deliverables
|
||||
- PRs/Issues/Docs/Reports
|
||||
|
||||
### Anonymous Leaders Reward Protocol
|
||||
|
||||
- fully qualified name: `vac:rfc:nomos: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.
|
||||
|
||||
#### Deliverables
|
||||
- PRs/Issues/Docs/Reports
|
||||
|
||||
### Wallet Technical Standard
|
||||
|
||||
- fully qualified name: `vac:rfc:nomos: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.
|
||||
|
||||
#### Deliverables
|
||||
- PRs/Issues/Docs/Reports
|
||||
|
||||
### Payload Formatting
|
||||
|
||||
- fully qualified name: `vac:rfc:nomos: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.
|
||||
|
||||
#### Deliverables
|
||||
- PRs/Issues/Docs/Reports
|
||||
|
||||
### Block Construction, Validation and Execution
|
||||
|
||||
- fully qualified name: `vac:rfc:nomos: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.
|
||||
|
||||
#### Deliverables
|
||||
- PRs/Issues/Docs/Reports
|
||||
|
||||
### Merge Open PRs
|
||||
|
||||
- fully qualified name: `vac:rfc:nomos:2026q1-rfc-iteration:merge-open-prs`
|
||||
- owner: cofson
|
||||
- status: not started
|
||||
- start-date: 2026/01/01
|
||||
- end-date: 2026/03/31
|
||||
|
||||
#### Description
|
||||
This task revolves around
|
||||
merging the existing open PRs,
|
||||
so that the process of merging PRs
|
||||
is as brief as possible.
|
||||
|
||||
Current pipeline:
|
||||
- Message Formatting: https://github.com/vacp2p/rfc-index/pull/219
|
||||
- Message Encapsulation: https://github.com/vacp2p/rfc-index/pull/218
|
||||
- Proof of Quota: https://github.com/vacp2p/rfc-index/pull/217
|
||||
- Key Types and Generation: https://github.com/vacp2p/rfc-index/pull/216
|
||||
- Blend Protocol: https://github.com/vacp2p/rfc-index/pull/213
|
||||
- Digital Signature: https://github.com/vacp2p/rfc-index/pull/167
|
||||
#### Deliverables
|
||||
- Merged PRs
|
||||
159
content/rfc/waku/2026q1-rfc-iteration.md
Normal file
159
content/rfc/waku/2026q1-rfc-iteration.md
Normal file
@@ -0,0 +1,159 @@
|
||||
---
|
||||
title: RFC Iteration
|
||||
tags:
|
||||
- 2026q1
|
||||
- rfc
|
||||
- waku
|
||||
draft: false
|
||||
description: "Iteration commitments generally comprise: through discussion and curation, support the process of auditing raw, draft, mature selected Waku RFCs."
|
||||
---
|
||||
|
||||
`vac:rfc:waku:2026q1-rfc-iteration`
|
||||
|
||||
Iteration commitments generally comprise:
|
||||
through discussion and curation,
|
||||
support the process of auditing raw, draft, mature selected Waku RFCs.
|
||||
|
||||
## Description
|
||||
|
||||
This commitment supports the audit of mature RFCs, which are
|
||||
either in draft or raw states. The audit comprises of:
|
||||
- Reading through the spec;
|
||||
- Checking the relevant codebase;
|
||||
- Changing the parts of the spec (descriptions and codebase) where applicable;
|
||||
- Updates of relevant links;
|
||||
- Changing the RFC status (optional);
|
||||
- Going through rounds of feedback with the relevant project team;
|
||||
- Adding clarifications where needed in the spec;
|
||||
- Checking for inconsistencies with other documentation/codebase.
|
||||
|
||||
The following RFCs will be worked on in this quarter:
|
||||
- 10/WAKU2
|
||||
- 12/WAKU2-FILTER
|
||||
- 13/WAKU2-STORE
|
||||
- 14/WAKU2-MESSAGE
|
||||
- 19/WAKU2-LIGHTPUSH
|
||||
- 34/WAKU2-PEER-EXCHANGE
|
||||
- 15/WAKU-BRIDGE
|
||||
|
||||
We will also include specification validation -
|
||||
editorial work through previous and future RFCs to improve them
|
||||
(identify edge cases for example)
|
||||
|
||||
## Task List
|
||||
|
||||
### 10/WAKU2
|
||||
|
||||
- Fully qualified name: `vac:rfc:waku:2026q1-rfc-iteration:10/WAKU2`
|
||||
- Owner: jimstir
|
||||
- Status: not started
|
||||
- Start date: 2026/01/01
|
||||
- End date: 2026/01/15
|
||||
|
||||
#### Description
|
||||
|
||||
Waku v2 is a family of modular peer-to-peer protocols for secure communication.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- Updated RFC document (potentially with an upgraded status).
|
||||
|
||||
### 12/WAKU2-FILTER
|
||||
|
||||
- Fully qualified name: `vac:rfc:waku:2026q1-rfc-iteration:12/WAKU2-FILTER`
|
||||
- Owner: jimstir
|
||||
- Status: not started
|
||||
- Start date: 2026/01/16
|
||||
- End date: 2026/01/31
|
||||
|
||||
#### Description
|
||||
|
||||
`WakuFilter` is a protocol that enables subscribing to messages that a peer
|
||||
receives.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- Updated RFC document (potentially with an upgraded status).
|
||||
|
||||
### 13/WAKU2-STORE
|
||||
|
||||
- Fully qualified name: `vac:rfc:waku:2026q1-rfc-iteration:13/WAKU2-STORE`
|
||||
- Owner: jimstir
|
||||
- Status: not started
|
||||
- Start date: 2026/02/01
|
||||
- End date: 2026/02/15
|
||||
|
||||
#### Description
|
||||
|
||||
This specification explains the `13/WAKU2-STORE` protocol, which enables
|
||||
querying messages received through the relay protocol and stored by other nodes.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- Updated RFC document (potentially with an upgraded status).
|
||||
|
||||
### 14/WAKU2-MESSAGE
|
||||
|
||||
- Fully qualified name: `vac:rfc:waku:2026q1-rfc-iteration:14/WAKU2-MESSAGE`
|
||||
- Owner: jimstir
|
||||
- Status: not started
|
||||
- Start date: 2026/02/16
|
||||
- End date: 2026/02/28
|
||||
|
||||
#### Description
|
||||
|
||||
Specification of the Waku v2 message format, used to encapsulate messages with
|
||||
specific security goals and provide Whisper/Waku v1 backward compatibility.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- Updated RFC document (potentially with an upgraded status).
|
||||
|
||||
### 19/WAKU2-LIGHTPUSH
|
||||
|
||||
- Fully qualified name: `vac:rfc:waku:2026q1-rfc-iteration:19/WAKU2-LIGHTPUSH`
|
||||
- Owner: jimstir
|
||||
- Status: not started
|
||||
- Start date: 2026/03/01
|
||||
- End date: 2026/03/15
|
||||
|
||||
#### Description
|
||||
|
||||
`WAKU2-LIGHTPUSH` is a protocol for light nodes with limited resources to
|
||||
publish messages in the Waku network and receive confirmation of delivery.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- Updated RFC document (potentially with an upgraded status).
|
||||
|
||||
### 34/WAKU2-PEER-EXCHANGE
|
||||
|
||||
- Fully qualified name: `vac:rfc:waku:2026q1-rfc-iteration:34/WAKU2-PEER-EXCHANGE`
|
||||
- Owner: jimstir
|
||||
- Status: not started
|
||||
- Start date: 2026/03/16
|
||||
- End date: 2026/03/31
|
||||
|
||||
#### Description
|
||||
|
||||
A peer discovery protocol for resource-restricted devices.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- Updated RFC document (potentially with an upgraded status).
|
||||
|
||||
### 15/WAKU-BRIDGE
|
||||
|
||||
- Fully qualified name: `vac:rfc:waku:2026q1-rfc-iteration:15/WAKU-BRIDGE`
|
||||
- Owner: jimstir
|
||||
- Status: not started
|
||||
- Start date: 2026/03/16
|
||||
- End date: 2024/03/31
|
||||
|
||||
#### Description
|
||||
|
||||
A bridge between Waku v1 and Waku v2.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
- Updated RFC document (potentially with an upgraded status).
|
||||
Reference in New Issue
Block a user