https://rfc.vac.dev/

Go to file

Jimmy Debe 9617146a6a Rename waku/standards/core/waku_legacy/9/waku2-rpc.md to waku/legacy/9/rpc.md		2024-02-12 20:25:02 -05:00
codex	Vac RFC index initial structure	2024-01-22 19:06:06 +01:00
nomos	Update and rename CLARO.md to claro.md	2024-02-02 00:03:44 -05:00
status	Update and rename status/57/simple-scaling.md to status/raw/57/simple-scaling.md	2024-02-12 20:09:03 -05:00
vac	Create libp2p-dns-discovery.md	2024-02-08 02:34:53 -05:00
waku	Rename waku/standards/core/waku_legacy/9/waku2-rpc.md to waku/legacy/9/rpc.md	2024-02-12 20:25:02 -05:00
README.md	Update README.md	2024-02-09 16:11:32 +01:00

README.md

Vac Request For Comments(RFC)

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

RFC Process

This repository contains specifications from the Vac, Waku, Nomos, Codex, and Status software teams. The goal of the RFC, Request for Comments, process is to standardize techincal specification. This repository will track specifications that adhere to 1/COSS. RFCs will be managed by the Vac team when specifcations have reached a rough consensus towards stabilization within each team.

Vac is an R&D org creating modular p2p protocols for private, secure, and censorship-resistant communication.

See rfc.vac.dev for an easy to browse index of all RFCs.

Contributing

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

Feel free to join the Vac discord. There's a channel specifically for RFC discussions.

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