Vac Request For Comments(RFC)

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. 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 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