diff --git a/content/rfc/codex/2025q4-rfc-iteration.md b/content/rfc/codex/2025q4-rfc-iteration.md new file mode 100644 index 000000000..57d879c16 --- /dev/null +++ b/content/rfc/codex/2025q4-rfc-iteration.md @@ -0,0 +1,149 @@ +--- +title: RFC Iteration +tags: + - 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:2025q4-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, +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: +- Slot builder +- Purchase module +- Block Exchange +- Erasure coding module + + +We will also include specification validation - +editorial work through previous and future RFCs to improve them +(identify edge cases for example) + + + +**Alignment with VAC Narratives:** + +- The VAC RFC team plans to become a repository +for RFCs regarding all IFT + projects. +- By promoting the RFC culture, +we hope to incentivize projects to submit their RFCs +to the rfc-editors team. +- We aim to have the broader web3 community use our RFCs +in their projects, similar to [IETF](https://www.ietf.org/). + +## Task List + +### Slot Builder + +- Fully qualified name: + `vac:rfc:codex:2025q4-rfc-iteration:slot-builder' +- Owner: jimstir +- Status: 10% +- Start date: 2025/10/01 +- End date: 2025/10/15 +### Erasure Coding Module + +- Fully qualified name: + `vac:rfc:codex:2025q4-rfc-iteration:erasure-coding-module` +- Owner: cofson +- Status: not started +- Start date: 2025/10/15 +- End date: 2025/10/30 + +### Purchase Module + +- Fully qualified name: + `vac:rfc:codex:2025q4-rfc-iteration:purchase-module` +- Owner: cofson +- Status: not started +- Start date: 2025/10/04 +- End date: 2025/10/19 + +### The Block Exchange + +- Fully qualified name: + `vac:rfc:codex:2025q4-rfc-iteration:the-block-exchange' +- Owner: cofson +- Status: not started +- Start date: 2025/10/04 +- End date: 2025/10/31 + + \ No newline at end of file diff --git a/content/rfc/ift/2025q4-rfc-culture-establishment.md b/content/rfc/ift/2025q4-rfc-culture-establishment.md new file mode 100644 index 000000000..df4e17172 --- /dev/null +++ b/content/rfc/ift/2025q4-rfc-culture-establishment.md @@ -0,0 +1,60 @@ +--- +title: RFC Culture Establishment +tags: + - rfc + - ift + - vac +draft: false +description: Continuation of RFC Culture establishment through introducing new initiatives. +--- + +`vac:rfc:ift:2025q4-rfc-culture-establishment` + +Continuation of RFC Culture establishment +through introducing new initiatives. + +## Description + +This commitment involves continuation +of the RFC culture implementation +through implementing the following: +- Introduction of discussion boards +(through forum posts and Discord) +to discuss new RFC creation/requirements +- Continued discussion on identifying new RFCs +from existing documentation. +This is done in order to try achieving rough consensus +on which new RFCs are to be made. + +**Alignment with VAC Narratives:** + +- The VAC RFC team aims +to become a repository for RFCs across all IFT projects. +- By demonstrating the value of the RFC process, we want future projects +to submit their RFCs to our team of rfc-editors. +- One of our goals is for the broader web3 community +to use our RFCs in their projects and ecosystems, +similar to [IETF](https://www.ietf.org/). + +## Task List + + +### Team Communication + +- Fully qualified name: `vac:rfc:ift:2025q4-culture-establishment-team-communication` +- Owner: cofson +- Status: not started +- Start date: 2025/10/01 +- End date: 2025/12/31 + +#### Description + +Continue discussions with relevant teams in Discord +and via other means (such as GitHub) where necessary. + +#### Deliverables + +- Plans +- Updates to plans + + diff --git a/content/rfc/ift/2025q4-rfc-index-maintenance.md b/content/rfc/ift/2025q4-rfc-index-maintenance.md new file mode 100644 index 000000000..369473c84 --- /dev/null +++ b/content/rfc/ift/2025q4-rfc-index-maintenance.md @@ -0,0 +1,61 @@ +--- +title: rfc-index-maintenance +tags: + - rfc + - vac +draft: false +description: This commitment revolves around a continuous effort to fix and update across the relevant RFC websites (including the communication). +--- + +`vac:rfc:ift:2025q4-rfc-index-maintenance` + +## Description + +This commitment revolves around a continuous effort +to fix and update across the relevant RFC websites +(including the communication). + +**Alignment with VAC Narratives:** + +- The information needs to be up to date +in order for projects and external parties +to have a clear view of information provided, +in accordance with the IFT standards. + +## Task List + +### Maintenance + +- Fully qualified name: `vac:rfc:ift:2025q4-rfc-index-maintenance:maintenance` +- Owner: Filip +- Status: not started +- Start date: 2025/10/01 +- End date: 2025/12/31 + +#### Description + +Check on the rfc-index, +fix any issues that arise and +note them properly. + +#### Deliverables + +- Fixed version of rfc-index + +### Maintenance of vac.dev + +- Fully qualified name: `vac:rfc:ift:2025q4-rfc-index-maintenance:maintenance-of-vac.dev` +- Owner: Filip +- Status: not started +- Start date: 2025/10/01 +- End date: 2025/12/31 + +#### Description + +Check on the vac.dev, +fix any issues that arise and +note them properly. + +#### Deliverables + +- Fixed version of vac.dev \ No newline at end of file diff --git a/content/rfc/nescience/2025q4-rfc-iteration.md b/content/rfc/nescience/2025q4-rfc-iteration.md new file mode 100644 index 000000000..8aac55482 --- /dev/null +++ b/content/rfc/nescience/2025q4-rfc-iteration.md @@ -0,0 +1,42 @@ +--- +title: RFC Iteration +tags: + - rfc + - nomos +draft: false +description: "Iteration commitments generally comprise: through discussion and curation, support the process of auditing raw, draft, mature selected RFCs." +--- + +`vac:rfc:nescience:2025q4-rfc-iteration` + +Iteration commitments generally comprise: +through discussion and curation, +support the process of auditing raw, draft, mature selected RFCs. + +## Description + +This commitment covers the writing of the following mature RFCs +according to COSS, based on the Notion documentation: +- TBD + +We will also include specification validation - +to make sure there are no errors, missing information, inconsistencies +and that the specification is up to standards. + + + +**Alignment with VAC Narratives:** + +- The VAC RFC team plans to become a repository +for RFCs regarding all IFT projects. +- By promoting the RFC culture, +we hope to incentivize projects to submit their RFCs +to the rfc-editors team. +- We aim to have the broader web3 community use our RFCs +in their projects, similar to [IETF](https://www.ietf.org/). + +## Task List + +TBD + + diff --git a/content/rfc/nomos/2025q4-rfc-iteration.md b/content/rfc/nomos/2025q4-rfc-iteration.md new file mode 100644 index 000000000..1b59d5ba8 --- /dev/null +++ b/content/rfc/nomos/2025q4-rfc-iteration.md @@ -0,0 +1,90 @@ +--- +title: RFC Iteration +tags: + - 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:2025q4-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: +- Cryptarchia v1 Protocol Specification +- Cryptarchia v1 Bootstrapping & Synchronization +- Cryptarchia Fork Choice Rule +- Total Stake Inference +- Proof of Leadership Specification + + +**Alignment with VAC Narratives:** + +- The VAC RFC team plans to become a repository +for RFCs regarding all IFT + projects. +- By promoting the RFC culture, +we hope to incentivize projects to submit their RFCs +to the rfc-editors team. +- We aim to have the broader web3 community use our RFCs +in their projects, similar to [IETF](https://www.ietf.org/). + +## Task List + +### Cryptarchia v1 Protocol Specification + +- Fully qualified name: + `vac:rfc:nomos:2025q4-rfc-iteration:cryptarchia-v1-protocol-specification` +- Owner: cofson +- Status: not started +- Start date: 2025/11/01 +- End date: 2025/11/15 + +### Cryptarchia v1 Bootstrapping & Synchronization + +- Fully qualified name: + `vac:rfc:nomos:2025q4-rfc-iteration:cryptarchia-v1-bootstrapping-and-synchronization` +- Owner: cofson +- Status: not started +- Start date: 2025/11/01 +- End date: 2025/11/15 + +### Cryptarchia Fork Choice Rule + +- Fully qualified name: + `vac:rfc:nomos:2025q4-rfc-iteration:cryptarchia-fork-choice-rule` +- Owner: cofson +- Status: not started +- Start date: 2025/12/01 +- End date: 2025/12/15 + +### Total Stake Inference + +- Fully qualified name: + `vac:rfc:nomos:2025q4-rfc-iteration:total-stake-inference` +- Owner: cofson +- Status: not started +- Start date: 2025/12/01 +- End date: 2025/12/15 + +### Proof of Leadership Specification + +- Fully qualified name: + `vac:rfc:nomos:2025q4-rfc-iteration:proof-of-leadership-specification` +- Owner: cofson +- Status: not started +- Start date: 2025/12/20 +- End date: 2025/12/31 \ No newline at end of file diff --git a/content/rfc/status/2025q4-rfc-iteration.md b/content/rfc/status/2025q4-rfc-iteration.md new file mode 100644 index 000000000..d04e2e671 --- /dev/null +++ b/content/rfc/status/2025q4-rfc-iteration.md @@ -0,0 +1,50 @@ +--- +title: RFC Iteration +tags: + - rfc +draft: false +description: "Iteration commitments generally comprise: through discussion and curation, support the process of auditing raw, draft, mature selected Status RFCs." +--- + +`vac:rfc:status:2025q4-rfc-iteration` + +Iteration commitments generally comprise: +through discussion and curation, +supporting the process of auditing +raw, draft, mature selected Status 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: +- Chat specifications + + +**Alignment with VAC Narratives:** + +- The VAC RFC team plans to become a repository +for RFCs regarding all IFT + projects. +- By promoting the RFC culture, +we hope to incentivize projects to submit their RFCs +to the rfc-editors team. +- We aim to have the broader web3 community use our RFCs +in their projects, similar to [IETF](https://www.ietf.org/). + +## Task List + +### Chat Specifications Support + +- Fully qualified name: + `vac:rfc:status:2025q4-rfc-iteration:chat-specifications-support` +- Owner: Filip +- Status: not started +- Start date: 2025/11/01 +- End date: 2025/12/31 diff --git a/content/rfc/waku/2025q4-rfc-iteration.md b/content/rfc/waku/2025q4-rfc-iteration.md new file mode 100644 index 000000000..d41a584ad --- /dev/null +++ b/content/rfc/waku/2025q4-rfc-iteration.md @@ -0,0 +1,58 @@ +--- +title: RFC Iteration +tags: + - 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:2025q4-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: +- Opchan + +We will also include specification validation - +editorial work through previous and future RFCs to improve them +(identify edge cases for example) + +**Alignment with VAC Narratives:** + +- The VAC RFC team plans to become a repository +for RFCs regarding all IFT + projects. +- By promoting the RFC culture, +we hope to incentivize projects to submit their RFCs +to the rfc-editors team. +- We aim to have the broader web3 community use our RFCs +in their projects, similar to [IETF](https://www.ietf.org/). +- We aim to provide feedback on specifications +from the point of view of a new developer. + +## Task List + +### Opchan + +- Fully qualified name: + `vac:rfc:waku:2025q4-rfc-iteration:opchan` +- Owner: jimstir +- Status: 30% (paused) +- Start date: 2025/11/01 +- End date: 2025/11/30 \ No newline at end of file diff --git a/content/rfc/zerokit/2025q3-rfc-iteration.md b/content/rfc/zerokit/2025q3-rfc-iteration.md index f2e77b7af..25bd90908 100644 --- a/content/rfc/zerokit/2025q3-rfc-iteration.md +++ b/content/rfc/zerokit/2025q3-rfc-iteration.md @@ -2,7 +2,6 @@ title: RFC Iteration tags: - rfc - - waku draft: false description: "Iteration commitments generally comprise: through discussion and curation, support the process of auditing raw, draft, mature selected Zerokit RFCs." ---