vacp2p
/
rfc
mirror of https://github.com/vacp2p/rfc.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
Modular p2p messaging stack, with a focus on secure messaging. https://rfc.vac.dev/
509 Commits 45 Branches 11 Tags 32 MiB
HTML 77.9%
Dockerfile 22.1%
Go to file
kaiserd 2dc9050600
Update README.md 		2024-06-14 16:38:49 +02:00
.github chore: Add GH labels (#516) 2022-07-27 18:33:16 +08:00
archetypes Merge repo with rfc.vac.dev (#310) 2021-04-01 12:03:14 +08:00
ci ci: add cleanup step, also timeout and timestamps 2023-09-26 10:46:31 +02:00
content 70/ETH-SECPM_improvements (#630) 2024-02-28 15:57:14 +01:00
example-content Merge repo with rfc.vac.dev (#310) 2021-04-01 12:03:14 +08:00
layouts/docs Merge repo with rfc.vac.dev (#310) 2021-04-01 12:03:14 +08:00
resources/_gen/assets/scss Merge repo with rfc.vac.dev (#310) 2021-04-01 12:03:14 +08:00
static 71/STATUS-Push-Notification-Server (#643) 2023-12-11 18:56:56 +01:00
themes Merge repo with rfc.vac.dev (#310) 2021-04-01 12:03:14 +08:00
.gitignore gitignore: add more hugo temporary files 2023-09-26 10:45:12 +02:00
.gitmodules Merge repo with rfc.vac.dev (#310) 2021-04-01 12:03:14 +08:00
.pyspelling.yml Update main.yml (#136) 2020-05-28 11:46:43 +02:00
.remarkrc adds link checks (#131) 2020-05-21 12:20:44 +08:00
.textlintrc text-lint (#134) 2020-05-25 11:55:06 +02:00
README.md Update README.md 2024-06-14 16:38:49 +02:00
config.toml support level 1 for the table of content (#597) 2023-05-10 19:07:01 +05:30

README.md

⚠️ WARNING
This repository is archived. New rfc-index

Vac RFCs

This repository contains specifications for the Vac project. 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 RFCs (Request for Comments) includes specs for the Waku family of specs, but also other things such as: node discovery, data sync, recommendations around usage, spec process, interfacing with auxiliary systems such as distributed storage, payload encryption, and so on.

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: https://github.com/orgs/vacp2p/projects/5

Building locally

Run git submodule update --init to install the Hugo "book" theme. Ensure you have the Hugo extended edition (https://gohugo.io/getting-started/installing/), then run hugo server.

These protocols define various components of the vac stack.

Style guide

Sequence diagrams are generated using Mscgen like this: mscgen -T png -i input.msc -o output.png. Both the source and generated image should be in source control. For ease of readability, the generated image is embedded inside the main spec document.

Alternatively, mscgenjs can be used to generate sequence diagrams (mscgenjs produces better quality figures especially concerning lines' spaces and figures' margins). Once installed, the following command can be used to generate the sequence diagrams mscgenjs -T png -i input.msc -o output.png. More details on the installation and compilation are given in mscgenjs repository. You may try the online playground https://mscgen.js.org/ as well to get a sense of the output figures.

Continuous Integration

The master branch is built by our Jenkins instance and deployed to https://rfc.vac.dev/.

Acknowledgement

Site layout and process inspired by https://rfc.zeromq.org/