1f9a6a8179
|
||
|---|---|---|
| .github/ISSUE_TEMPLATE | ||
| _includes | ||
| _layouts | ||
| assets | ||
| specs | ||
| .gitignore | ||
| .remarkrc | ||
| .travis.yml | ||
| 404.html | ||
| CNAME | ||
| Gemfile | ||
| Gemfile.lock | ||
| README.md | ||
| _config.yml | ||
| package-lock.json | ||
| package.json | ||
README.md
This repository contains the specs for vac, a modular peer-to-peer messaging stack, with a focus on secure messaging. A detailed explanation of the vac and its design goals can be found here.
Status
The entire vac protocol is under active development, each specification has its own status which is reflected through the version number at the top of every document. We use semver to version these specifications.
Protocols
These protocols define various components of the vac stack.
- mvds - Data Synchronization protocol for unreliable transports.
- remote log - Remote replication of local logs.
- mvds metadata - Metadata field for MVDS messages.
Waku
Waku is a protocol that substitutes EIP-627.
- waku - ÐΞVp2p wire protocol, substituting EIP-627.
- envelope data format - waku envelope data field specification.
- mailserver - Mailserver specification for archiving and delivering historical waku envelopes on demand.
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.
The lifecycle of the specs follows the COSS Lifecycle
Meta
The keywords “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in RFC 2119.