e39d2884fe
adding done: - multi steward support sections such as: consensus types, big and small type flows - new two de-mls term epoch and backup steward - violation list section - who can initiate the consensuses - deterministically creation of the steward list (against biased list) - order of the consensus messages - adding member-id as 160 bit id - adding flexible committing for multiple steward - unifying the commit among multiple committing for specific epoch - clarifying minimum number of steward list s_min and the scenario that group member number getting below this next (in a separate PR) - introducing peer scoring (currently we only kicked off malicious members) - anti deadlock mechanism in case of non-active steward (even if the committing is flexible now) - identifying the format of dishonesty evidence --------- Co-authored-by: Ekaterina Broslavskaya <seemenkina@gmail.com> Co-authored-by: Jazz Turner-Baggs <473256+jazzz@users.noreply.github.com>
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: