mirror of
https://github.com/vacp2p/vac-book.git
synced 2026-01-08 04:53:56 -05:00
Update
This commit is contained in:
39
.obsidian/workspace.json
vendored
39
.obsidian/workspace.json
vendored
@@ -18,8 +18,33 @@
|
||||
"source": false
|
||||
}
|
||||
}
|
||||
},
|
||||
{
|
||||
"id": "656283cc8de0b6d4",
|
||||
"type": "leaf",
|
||||
"state": {
|
||||
"type": "markdown",
|
||||
"state": {
|
||||
"file": "README.md",
|
||||
"mode": "source",
|
||||
"source": false
|
||||
}
|
||||
}
|
||||
},
|
||||
{
|
||||
"id": "4e258b0332457c2a",
|
||||
"type": "leaf",
|
||||
"state": {
|
||||
"type": "markdown",
|
||||
"state": {
|
||||
"file": "scratch/vac-book-migration.md",
|
||||
"mode": "source",
|
||||
"source": false
|
||||
}
|
||||
}
|
||||
}
|
||||
]
|
||||
],
|
||||
"currentTab": 2
|
||||
}
|
||||
],
|
||||
"direction": "vertical"
|
||||
@@ -85,7 +110,7 @@
|
||||
"state": {
|
||||
"type": "backlink",
|
||||
"state": {
|
||||
"file": "README.md",
|
||||
"file": "scratch/vac-book-migration.md",
|
||||
"collapseAll": false,
|
||||
"extraContext": false,
|
||||
"sortOrder": "alphabetical",
|
||||
@@ -102,7 +127,7 @@
|
||||
"state": {
|
||||
"type": "outgoing-link",
|
||||
"state": {
|
||||
"file": "README.md",
|
||||
"file": "scratch/vac-book-migration.md",
|
||||
"linksCollapsed": false,
|
||||
"unlinkedCollapsed": true
|
||||
}
|
||||
@@ -125,7 +150,7 @@
|
||||
"state": {
|
||||
"type": "outline",
|
||||
"state": {
|
||||
"file": "README.md"
|
||||
"file": "scratch/vac-book-migration.md"
|
||||
}
|
||||
}
|
||||
}
|
||||
@@ -146,8 +171,10 @@
|
||||
"command-palette:Open command palette": false
|
||||
}
|
||||
},
|
||||
"active": "8f7e7a7390c5ce8e",
|
||||
"active": "4e258b0332457c2a",
|
||||
"lastOpenFiles": [
|
||||
"README.md"
|
||||
"README.md",
|
||||
"topics/secure-messaging-overview.md",
|
||||
"Untitled.md"
|
||||
]
|
||||
}
|
||||
@@ -3,6 +3,11 @@ Welcome to the Vac book! This acts as a knowledge base for https://vac.dev/.
|
||||
|
||||
This replaces the somewhat-outdated Vac overview here: https://hackmd.io/@vac/main/
|
||||
|
||||
## About
|
||||
|
||||
- **topics** - Notes on various topics.
|
||||
- **scratch** - Temporary, throw-away stuff.
|
||||
|
||||
## Contribute
|
||||
|
||||
Best used together with Obsidan, but any text editor works.
|
||||
|
||||
25
scratch/vac-book-migration.md
Normal file
25
scratch/vac-book-migration.md
Normal file
@@ -0,0 +1,25 @@
|
||||
|
||||
https://hackmd.io/@vac/main
|
||||
|
||||
- [ ] Vac overview
|
||||
- [ ] Tools and workfows
|
||||
- [ ] Waku v2 training
|
||||
- [ ] Research
|
||||
- [ ] Intro
|
||||
- [ ] Waku v1 vs Waku v2
|
||||
- [ ] Secure Messaging
|
||||
- [ ] Overview
|
||||
- [ ] 2023 priorities
|
||||
- [ ] Team allocation
|
||||
- [ ] nwaku
|
||||
- [ ] Intro
|
||||
- [ ] Waku Connect
|
||||
- [ ] Intro, Waku Connect PM, Bounty ideas, Presentations
|
||||
- captured elsewhere?
|
||||
- [ ] Outreach
|
||||
- [ ] Platform
|
||||
- [ ] Operator
|
||||
- [ ] Research
|
||||
- [ ] Other
|
||||
- [ ] Vac PM notes
|
||||
- [ ] Onboarding guide
|
||||
108
topics/secure-messaging-overview.md
Normal file
108
topics/secure-messaging-overview.md
Normal file
@@ -0,0 +1,108 @@
|
||||
|
||||
# Secure Messaging (SeM) Overview
|
||||
|
||||
> *Note*: This page is still WiP.
|
||||
This page will be published either as a page on `vac.dev`,
|
||||
or alternatively on `sem.vac.dev`.
|
||||
|
||||
Vac's Secure Messaging (SeM) project researches and designs
|
||||
modular p2p protocols for scaling, secure, private, anonymous, and censorship-resistant communications.
|
||||
The main focus is [Waku](https://waku.org), the communication layer for Web3.
|
||||
|
||||
The following tracks are part of SeM.
|
||||
|
||||
### Secure Scaling
|
||||
|
||||
[*Secure Scaling Roadmap*](https://github.com/vacp2p/research/issues/154)
|
||||
|
||||
The *secure scaling* track is concerned with scaling Waku protocols in a secure and efficient way.
|
||||
This includes DoS protection and resilience, as well as making sure that privacy and anonymity properties are not violated.
|
||||
|
||||
### Restricted Run
|
||||
|
||||
[*Restricted Run Roadmap*](https://github.com/vacp2p/research/issues/153)
|
||||
|
||||
Waku's [adaptive node](https://rfc.vac.dev/spec/30/) concept allows nodes of (almost) any resource profile to participate in Waku networks.
|
||||
Nodes with more resources contribute the network, incentivized by various means addressed in the [protocol incentivization track](#protocol_incentivization).
|
||||
Nodes with restricted resources mainly consume services.
|
||||
|
||||
The *restricted run* track researches and develops protocols and protocol extensions for resource restricted nodes.
|
||||
The restricted run track covers the need of restricted devices in areas covered by the other tracks (e.g. secure scaling, anonymity, discovery),
|
||||
and can be seen as orthogonal to these tracks.
|
||||
|
||||
The complexity that makes protocols like [11/WAKU2-RELAY](https://rfc.vac.dev/spec/11/)
|
||||
too resource intense for some nodes also provides (depending on the specific protocol)
|
||||
desirable privacy, anonymity, resilience, and latency properties.
|
||||
A special challenge in the restricted run track stems from compensating these trade-offs as well as possible.
|
||||
We aim to offer restricted nodes protocols that first and foremost allow network participation at all,
|
||||
but also have desirable properties beyond that.
|
||||
|
||||
Examples for restricted run protocols are
|
||||
|
||||
* [12/WAKU2-FILTER](https://rfc.vac.dev/spec/12/)
|
||||
* [19/WAKU2-LIGHTPUSH](https://rfc.vac.dev/spec/19/)
|
||||
* [34/WAKU2-PEER-EXCHANGE](https://rfc.vac.dev/spec/34/)
|
||||
|
||||
*Restricted run* also covers the needs of restricted nodes beyond protocol design, e.g. NAT traversal.
|
||||
|
||||
### Discovery
|
||||
|
||||
[*Discovery Roadmap*](https://github.com/vacp2p/research/issues/116)
|
||||
|
||||
In order to build a P2P network,
|
||||
participating nodes first have to discover peers within this network.
|
||||
Ambient peer discovery allows nodes to find peers, making it an integral part of any decentralized application.
|
||||
Our [research log post on Ambient Peer Discovery](https://vac.dev/wakuv2-apd) gives more background on this research area.
|
||||
|
||||
The *discovery* track aims to
|
||||
|
||||
* improve our existing discovery methods in terms of privacy, anonymity, resilience, and network efficiency
|
||||
* research and design new discovery methods, as we want the best possible connectivity for Waku nodes
|
||||
|
||||
### Application Protocols
|
||||
|
||||
[*Application Protocols Roadmap*](https://github.com/vacp2p/research/issues/165)
|
||||
|
||||
### Privacy & Anonymity
|
||||
|
||||
[*Anonymity Roadmap*](https://github.com/vacp2p/research/issues/107)
|
||||
|
||||
One of Waku's main design goals is being privacy and anonymity preserving.
|
||||
Waku v2 is modular and was designed with pluggable privacy/anonymity in mind.
|
||||
|
||||
The *Anonymity* track analyses current Waku v2 protocols with respect to their privacy/anonymity guarantees,
|
||||
as well as plans to evaluate, specify, and implement new protocols that will enhance Waku v2 privacy/anonymity.
|
||||
|
||||
Our [research log post on Waku Relay Anonymity](https://vac.dev/wakuv2-apd) provides more background.
|
||||
Adversarial models we consider are listed in [45/WAKU2-ADVERSARIAL-MODELS](https://rfc.vac.dev/spec/45/).
|
||||
|
||||
### Conversational Security
|
||||
|
||||
[*Conversational Security Roadmap*](https://github.com/vacp2p/research/issues/169)
|
||||
|
||||
### RLN
|
||||
|
||||
We plan to move the RLN track into a dedicated project: [rlnp2p.vac.dev](https://rlnp2p.vac.dev/)
|
||||
|
||||
The *protocol incentivization* track uses results from *rlnp2p*.
|
||||
|
||||
### Protocol Incentivization
|
||||
|
||||
[*Protocol Incentivization Roadmap*](https://github.com/vacp2p/research/issues/171)
|
||||
|
||||
The *protocol incentivization* track covers research on incentives for nodes to offer specific services and/or resources.
|
||||
|
||||
Part of this is research on service credentials.
|
||||
The goal is allowing service consumers to purchase *service credentials* (or tokens) that can be used to obtain services from Waku nodes.
|
||||
Service providers will be able to claim funds associated with received credentials.
|
||||
|
||||
### Data Synchronization
|
||||
|
||||
[*Data Synchronization Roadmap*](https://github.com/vacp2p/research/issues/170)
|
||||
|
||||
The SeM *data synchronization* track covers research of secure and efficient asynchronous data synchronization between nodes.
|
||||
It complements live messaging via [11/WAKU2-RELAY](11/WAKU2-RELAY).
|
||||
|
||||
### Censorship Resistance
|
||||
|
||||
Future Work.
|
||||
Reference in New Issue
Block a user