Oskar Thorén b59b9247f2
Waku version 0 - initial (#28)
* Init with EIP-627

* Header and abstract

* WIP

* Update waku.md

* Update waku.md

* Inline comments

* add Dean and toc

* document rlpx subprotocol

* Rename waku.md to waku/README.md

* reworded

* light-node (#31)

* added

* sections

* changelog

* updated

* updates

* Update README.md

* Update README.md

* Update README.md

* Update README.md

* Update README.md

* Update README.md

* Update RLPx subprotocol based on nim-eth changes

* Add section on backwards compatibility

* changelog and todo

* update toc

* update rlpx section

* specify rlpx version number

* add differences shh6 waku 0

* generalize light node section to additional capabilities

* add mock security considerations section

* mock section of forwards comp

* bump mini version

* fix typo

* Update waku/README.md

Co-Authored-By: kdeme <kim.demey@gmail.com>

* Update waku/README.md

Co-Authored-By: kdeme <kim.demey@gmail.com>

* Update README.md

* Update README.md

* Update waku/README.md

Co-Authored-By: kdeme <kim.demey@gmail.com>

* Update README.md

* Update README.md

* Update README.md

* Update waku/README.md

Co-Authored-By: Adam Babik <a.babik@designfortress.com>

* Update README.md

* Update README.md

* Update waku/README.md

Co-Authored-By: kdeme <kim.demey@gmail.com>

* Update waku/README.md

Co-Authored-By: kdeme <kim.demey@gmail.com>

* Update README.md (#42)

* Move back to waku.md KISS

* try footnote link

* rlp detail links

* add ABNF spec

* moar abnf, and remove superfluous data format descriptions

* modify abstract and motivation

* abnf whisper envelope

* move security consider

* clarify duplication

* some backwards compatibility notes and move things a bit

* version 0.1.0 prepare for merge; toc; ack section

* tweak acks
2019-11-21 23:15:40 +08:00
2019-10-01 12:52:02 +08:00
2019-08-02 18:20:01 +02:00
2019-09-22 20:39:34 +02:00
2019-08-04 15:25:11 +02:00
2019-11-21 10:51:16 +08:00
2019-11-02 15:52:22 +01:00
2019-11-21 23:15:40 +08:00

Specifications

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

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.

Description
Modular p2p messaging stack, with a focus on secure messaging.
https://rfc.vac.dev/
Readme
Languages
HTML 77.9%
Dockerfile 22.1%