https://rfc.vac.dev/

Go to file

Jimmy Debe 4070f8687a Rename vac/3/remote-log.png to vac/3/images/remote-log.png		2024-02-01 22:44:40 -05:00
codex	Vac RFC index initial structure	2024-01-22 19:06:06 +01:00
nomos	Create CLARO.md	2024-01-27 20:45:58 -05:00
status	Update README.md	2024-01-29 00:29:02 -05:00
vac	Rename vac/3/remote-log.png to vac/3/images/remote-log.png	2024-02-01 22:44:40 -05:00
waku	Update and rename WAKU1.md to waku1.md	2024-02-01 22:15:35 -05:00
README.md	Update README.md	2024-01-28 23:12:57 -05:00

README.md

Vac RFC Index

RFC Process

This repository contains specifications for the Vac, Waku, Nomos, Codex, and Status projects. The RFCs, (Request for Comments), included in this repository will be managed by the Vac team when specifcations have reached a rough consensus towards stabilization within each working group.

Vac is an R&D org creating modular p2p protocols for private, secure, and censorship-resistant communication. A detailed, albeit slightly outdated (2019), explanation of Vac and its design goals can be found here.

Vac, while having a core team of maintainers and contributors, is an open and permission-less organization.

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

Contributing

Please see 1/COSS for general guidelines and spec 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