Skip to content
Modular p2p messaging stack, with a focus on secure messaging.
Branch: master
Clone or download
decanus and oskarth Update (#33)
* Update

* Update
Latest commit 2e52055 Nov 18, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github/ISSUE_TEMPLATE Update Nov 14, 2019
assets Update remote log asset Oct 1, 2019
404.html Create 404.html Sep 22, 2019
CNAME Create CNAME Aug 4, 2019 Update Nov 2, 2019
_config.yml Update _config.yml Aug 2, 2019 Update Nov 17, 2019 Changelog and fix ToC numbres (#26) Nov 14, 2019


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.


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.


These protocols define various components of the vac stack.

  • mvds - Data Synchronization protocol for unreliable transports.
  • remote log - Remote replication of local logs.
  • mdf - Metadata field for MVDS messages.

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

You can’t perform that action at this time.