Hanno Cornelius 171e934d61 docs: add SDS-Repair extension (#176)
Added SDS-R, an (optional) extension of SDS to allow for coordinated
repair of missing messages over a limited time window.

It functions by allowing subgroups of participants to rebroadcast
dependencies that were reported missing by other participants. As with
the rest of SDS, it aims to scale to larger groups first and could
likely be simplified for 1:1 or small group chats. To prevent an
explosion in repair requests or broadcast storms, it uses backoff timers
to prevent multiple participants from performing the same action (either
request a repair or rebroadcast in response to a repair request) in a
probabilistic manner.

Note that what is still missing is a specified recommended way to use
SDS-R in conjunction with retrieving missing dependencies from Store
nodes.

---------

Co-authored-by: fryorcraken <110212804+fryorcraken@users.noreply.github.com>
2025-10-13 15:37:44 +01:00
2024-09-13 16:51:09 +02:00
2025-06-05 10:13:21 -04:00
2025-10-13 15:37:44 +01:00
2024-10-09 17:54:02 +02:00

Vac Request For Comments(RFC)

NOTE: This repo is WIP. We are currently restructuring the RFC process.

This repository contains specifications from the Waku, Nomos, Codex, and Status projects that are part of the IFT portfolio. Vac is an IFT service that will manage the RFC, Request for Comments, process within this repository.

New RFC Process

This repository replaces the previous rfc.vac.dev resource. Each project will maintain initial specifications in separate repositories, which may be considered as a raw specification. All Vac raw specifications and discussions will live in the Vac subdirectory. When projects have reached some level of maturity for a specification living in their repository, the process of updating the status to draft may begin in this repository. Specifications will adhere to 1/COSS before obtaining draft status.

Implementations should follow specifications as described, and all contributions will be discussed before the stable status is obtained. The goal of this RFC process will to engage all interseted parities and reach a rough consensus for techcinal specifications.

Contributing

Please see 1/COSS for general guidelines and specification lifecycle.

Feel free to join the Vac discord.

Here's the project board used by core contributors and maintainers: Projects

IFT Projects' Raw Specifications

The repository for each project raw specifications:

Description
No description provided
Readme 25 MiB
Languages
Markdown 100%