RFC Commitments proposal Q1 2026 #342
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,50 @@ | ||
| --- | ||
| 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, Erasure coding, Proving system | ||
|
|
||
| ## Description | ||
|
|
||
| This commitment supports the process of the choosing which raw RFCs, | ||
|
Collaborator
There was a problem hiding this comment. We can say that we need to drive the merging of open PRs and also refine raw RFC into more mature ones |
||
| from the existing documentation to be put in pipeline to be written or updated. | ||
|
|
||
| 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 | ||
|
Collaborator
There was a problem hiding this comment. We can have a task to merge open PRs |
||
|
|
||
| - fully qualified name: `vac:rfc:codex:2026q1-rfc-iteration:wip` | ||
| - owner: cofson | ||
| - status: not started | ||
| - start-date: 2026/01/01 | ||
| - end-date: 2025/01/01 | ||
|
|
||
|
|
||
| #### Description | ||
| WIP | ||
|
|
||
|
|
||
| #### Deliverables | ||
| - WIP | ||
|
|
||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,125 @@ | ||
| --- | ||
| 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: | ||
| - Proof of Quota Specification | ||
| - Mantle Specification | ||
| - Bedrock Genesis Block | ||
| - Service Reward Distribution Protocol | ||
| - Anonymous Leaders Reward Protocol | ||
| - Wallet Technical Standard | ||
| - Block Construction, Validation and Execution Specification | ||
| - Bedrock Architecture Overview | ||
| - Proof of Leadership Specification | ||
| - Message Encapsulation Mechanism | ||
| - Message Formatting Specification | ||
| - Payload Formatting Specification | ||
|
|
||
| ## Task List | ||
|
|
||
| ### Proof of Quota Specification | ||
|
|
||
| - fully qualified name: `vac:rfc:nomos:2026q1-rfc-iteration:proof-of-quota-specification` | ||
| - owner: cofson | ||
| - status: not started | ||
| - start-date: 2026/01/01 | ||
| - end-date: 2026/01/15 | ||
|
|
||
| #### Description | ||
| Create the RFC for the Proof of Quota Specification based on the Nomos raw spec that applies 1/COSS. | ||
|
|
||
| #### Deliverables | ||
| - PRs/Issues/Docs/Reports | ||
|
|
||
| ### Mantle Specification | ||
|
|
||
| - fully qualified name: `vac:rfc:nomos:2026q1-rfc-iteration:mantle-specification` | ||
| - owner: cofson | ||
| - status: not started | ||
| - start-date: 2026/01/16 | ||
| - end-date: 2026/01/31 | ||
|
|
||
| #### Description | ||
| Create the RFC for the Mantle Specification based on the Nomos raw spec that applies 1/COSS. | ||
|
|
||
| #### Deliverables | ||
| - PRs/Issues/Docs/Reports | ||
|
|
||
| ### Bedrock Genesis Block Specification | ||
|
|
||
| - fully qualified name: `vac:rfc:nomos:2026q1-rfc-iteration:bedrock-genesis-block-specification` | ||
| - owner: cofson | ||
| - status: not started | ||
| - start-date: 2026/02/01 | ||
| - end-date: 2026/02/15 | ||
|
|
||
| #### Description | ||
| Create the RFC for the Bedrock Genesis Block Specification 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 - Wallet Technical Standard |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -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). |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we can list code RFC that are not merged yet