mirror of https://github.com/acid-info/vac.dev.git
Feat/update copy (#79)
* Update vac.dev main copy * Add principles page * Update projects page * Format research-areas * Format principles * Update projects * Update projects on main page * Format main page * Tweak main page * Add open problems stub * Add contribute stub * Update media page - add Waku v2 training session * Remove about folder and move media to top level * Update config layout * update open problems * sembr principles * add ietf nod * fix * Update research-areas.md Co-authored-by: Daniel Kaiser <git@kais3r.de> * Update projects.md Co-authored-by: Daniel Kaiser <git@kais3r.de> * Update research-areas.md Co-authored-by: Daniel Kaiser <git@kais3r.de> * Update research-areas.md Co-authored-by: Daniel Kaiser <git@kais3r.de> * Update research-areas.md Co-authored-by: Daniel Kaiser <git@kais3r.de> * Update vac.md Co-authored-by: Daniel Kaiser <git@kais3r.de> Co-authored-by: User Name <user@mbp22.local> Co-authored-by: Daniel Kaiser <git@kais3r.de>
This commit is contained in:
oskarth
GitHub
parent
73e46553d9
commit
b755aee84c
|
|
@ -1,14 +0,0 @@
|
|||
---
|
||||
title: Get in touch
|
||||
---
|
||||
## Join the team
|
||||
We are a remote team of researchers dedicated to building a fair internet.
|
||||
[View open roles](https://jobs.status.im/?search=Vac)
|
||||
|
||||
## Join the convo
|
||||
Ask questions or speak with us about our work as we research new means of communication.
|
||||
[Join our Discord](https://discord.gg/PQFdubGt6d)
|
||||
|
||||
## Contribute on Github
|
||||
Our work is open source and free for anyone to contribute to, use, and modify for their needs.
|
||||
[Contribute](https://github.com/vacp2p)
|
||||
|
|
@ -1,4 +0,0 @@
|
|||
---
|
||||
title: team
|
||||
injects: [authors]
|
||||
---
|
||||
29
config.json
29
config.json
|
|
@ -24,41 +24,40 @@
|
|||
"home":"vac.md",
|
||||
"fileOrdersInSidenav": [
|
||||
"vac.md",
|
||||
"principles.md",
|
||||
"research-areas.md",
|
||||
"projects.md"
|
||||
"projects.md",
|
||||
"open-problems.md",
|
||||
"contribute.md",
|
||||
"media.md",
|
||||
],
|
||||
"folderOrdersInSidenav": [
|
||||
"research",
|
||||
"about"
|
||||
"research"
|
||||
],
|
||||
"external_links": [
|
||||
{
|
||||
"text": "Research & experimentation",
|
||||
"url": "https://github.com/vacp2p/research/",
|
||||
"category": "Resources"
|
||||
},
|
||||
{
|
||||
"text": "Vac RFCs/Specs",
|
||||
"text": "Specs/RFCs",
|
||||
"url": "https://rfc.vac.dev/",
|
||||
"category": "Resources"
|
||||
},
|
||||
{
|
||||
"text": "Vac Forum",
|
||||
"text": "Forum",
|
||||
"url": "https://forum.vac.dev/",
|
||||
"category": "Resources"
|
||||
},
|
||||
{
|
||||
"text": "Waku v2 training session",
|
||||
"url": "https://drive.google.com/file/d/19P3oDNXGBDClfcS6Sgp0t9LYr3UbIFGt/view",
|
||||
"text": "Waku.org",
|
||||
"url": "https://waku.org",
|
||||
"category": "Resources"
|
||||
}
|
||||
|
||||
]
|
||||
},
|
||||
"ds_id": "vac",
|
||||
"seo": {
|
||||
"title": "Vac",
|
||||
"description": "Vac is an R&D org creating modular p2p protocols for private, secure, censorship-resistant communication.",
|
||||
"cc": "Vac researches peer-to-peer, private, censorship-resistant communication",
|
||||
"title": "Vac Research",
|
||||
"description": "Vac - Communication, Privacy, Etc.",
|
||||
"cc": "Vac - Communication, Privacy, Etc",
|
||||
"image": "vac-site-preview-image.png",
|
||||
"url": "https://staging.vac.dev",
|
||||
"social_media": [
|
||||
|
|
|
|||
|
|
@ -0,0 +1,9 @@
|
|||
# Contribute
|
||||
|
||||
This page is a stub.
|
||||
|
||||
For now, please check out the following links:
|
||||
|
||||
- [Contribute on Github](https://github.com/vacp2p)
|
||||
- [Join our Discord](https://discord.gg/PQFdubGt6d)
|
||||
- [Open roles](https://jobs.status.im/?search=Vac)
|
||||
|
|
@ -1,3 +1,5 @@
|
|||
[Waku v2 training session](https://drive.google.com/file/d/19P3oDNXGBDClfcS6Sgp0t9LYr3UbIFGt/view)
|
||||
|
||||
[Waku: Enabling a New Dimension for dApps](https://www.youtube.com/watch?v=GXU5Fd6gMVw&t=21692s)
|
||||
|
||||
[Vac, Waku v2 and Ethereum Messaging](https://www.youtube.com/watch?v=s0ATpQ4_XFc&ab_channel=OsakaThorp)
|
||||
|
|
@ -0,0 +1,5 @@
|
|||
# Open research problems
|
||||
|
||||
This page is a stub. It will be filled out with open research problems.
|
||||
|
||||
For now, please take a look at our open issues. For example in the [vacp2p/research repo](https://github.com/vacp2p/research/issues).
|
||||
|
|
@ -0,0 +1,70 @@
|
|||
# Principles
|
||||
|
||||
The goal of Vac is widespread adoption of the decentralized web.
|
||||
Our challenge is achieving mass adoption while staying true to our principles outlined below.
|
||||
|
||||
## I. Liberty
|
||||
|
||||
We believe in the sovereignty of individuals.
|
||||
As a research organization that stands for the cause of personal liberty,
|
||||
we aim to maximize social, political, and economic freedoms.
|
||||
This includes being coercion-resistant.
|
||||
|
||||
## II. Censorship resistance
|
||||
|
||||
We enable free flow of information.
|
||||
No content is under surveillance.
|
||||
We abide by the cryptoeconomic design principle of censorship resistance.
|
||||
Even stronger, we design agnostic infrastructures for information.
|
||||
|
||||
## III. Security
|
||||
|
||||
We don't compromise on security when building features.
|
||||
We use state-of-the-art technologies,
|
||||
and research new security methods and technologies to make strong security guarantees.
|
||||
|
||||
## IV. Privacy
|
||||
|
||||
Privacy is the power to selectively reveal oneself to the world.
|
||||
For us, it's essential to protect privacy in both communications and transactions,
|
||||
as well as pseudo-anonymity.
|
||||
Additionally, we strive to provide the right of total anonymity.
|
||||
|
||||
## V. Transparency
|
||||
|
||||
We strive for complete openness and symmetry of information within the organization,
|
||||
and have no border between our core contributors and our community.
|
||||
We are frank about our shortcomings,
|
||||
especially when making short-term tradeoffs in service of our long-term goals.
|
||||
|
||||
## VI. Openness
|
||||
|
||||
The software we create is a public good.
|
||||
It is made available via a free and open source license,
|
||||
for anyone to share, modify and benefit from.
|
||||
We believe in permission-less participation.
|
||||
|
||||
## VII. Decentralization
|
||||
|
||||
We minimize centralization across both the software and the organization itself.
|
||||
In other words, we maximize the number of physical computers composing the network,
|
||||
and maximize the number of individuals who have control over the system(s) we are building.
|
||||
|
||||
## VIII. Inclusivity
|
||||
|
||||
We believe in fair and widespread access to our software, with an emphasis on ease-of-use.
|
||||
This also extends to social inclusivity, permissionless participation, interoperability,
|
||||
and investing in educational efforts.
|
||||
|
||||
## IX. Continuance
|
||||
|
||||
We create software incentivized to continue to exist and improve,
|
||||
without the stewardship of a single entity or any of the current team members.
|
||||
|
||||
## X. Resourcefulness
|
||||
|
||||
We are relentlessly resourceful.
|
||||
As we grow and have ready access to capital,
|
||||
it is our obligation to token holders to fight bureaucracy and inefficiencies within the organization.
|
||||
This means solving problems in the most effective way possible at lower economic costs
|
||||
(in terms of capital, time and resources).
|
||||
25
projects.md
25
projects.md
|
|
@ -2,17 +2,26 @@
|
|||
title: Projects
|
||||
---
|
||||
|
||||
# Vac projects
|
||||
# Projects
|
||||
|
||||
There are several projects under Vac.
|
||||
There are several projects under Vac Research.
|
||||
These are largely independent and can be seen as specific bets.
|
||||
|
||||
## Waku Research
|
||||
## Secure Messaging
|
||||
|
||||
Basically what Vac is primarily focused on today.
|
||||
Serves Waku Product, and aims to make Waku a self-sustained robust network with strong and modular privacy guarantees.
|
||||
This also includes secure messaging research and things like p2p/networking.
|
||||
We design modular, p2p protocols for private, anonymous, secure and censorship-resistant communications. The main focus is [Waku](https://waku.org), the communication layer for Web3.
|
||||
|
||||
## Other projects
|
||||
## zk-WASM
|
||||
|
||||
More projects will be added here soon.
|
||||
Research into making private and provable computation using WASM that is verified using zero-knowledge proofs.
|
||||
|
||||
### RAD - RFCs & Dissemination
|
||||
|
||||
**RFCs**: We build specifications for self-sustainable robust protocols with strong and modular privacy guarantees. [Rough consensus and running code](https://www.ietf.org/about/participate/tao/).
|
||||
|
||||
**Dissemination**: We write papers and aim to collaborate closely with other
|
||||
institutions to build a bridge between industry and academia.
|
||||
|
||||
## Applied ZK & Explorations
|
||||
|
||||
We build tools to enable new fundamental building blocks using cutting-edge zero-knowledge proof systems.
|
||||
|
|
|
|||
|
|
@ -1,29 +1,43 @@
|
|||
---
|
||||
title: Research areas
|
||||
---
|
||||
|
||||
# Overview
|
||||
|
||||
Vac has several research areas it is interested in and has or is developing expertise in. Here’s an overview of some of these areas along with motivation and what type of topics are included. Note that a lot of areas are overlapping in terms of specific projects.
|
||||
|
||||
## Incentivization
|
||||
In a open p2p network, nodes have to be incentivized for services provided to the network. Additionally, these should be privacy-preserving and as trust-minimized as possible. This research areas includes things such as: RLN, service credentials, peer reputation, and protocol revenue.
|
||||
|
||||
In an open p2p network, nodes have to be incentivized for services provided to the network. Additionally, these should be privacy-preserving and as trust-minimized as possible. This research area includes (but is not limited to): RLN, service credentials, peer reputation, and protocol revenue.
|
||||
|
||||
## Applied ZK
|
||||
|
||||
Applied ZK opens up the door to many new constructs, especially related to privacy. This research area includes things like RLN, Unirep and similar novel constructs, but also things like R&D related to ZKs in general such as Circom, proves on mobile, different proof systems such as Halo 2, etc. Done in close collaboration with other teams in the space.
|
||||
|
||||
## Privacy/Anonymity
|
||||
|
||||
Specifically metadata privacy. This includes anonymity studies and providing a modular suite of protocols with clear trade-offs and threat models.
|
||||
|
||||
## Scalability
|
||||
|
||||
Making the network scalable in terms of number of nodes, messages supported, discovering of nodes, caching of historical messages etc. Largely focused on Waku right now, but things like scalable group chats also relevant here.
|
||||
|
||||
## Data synchronization
|
||||
|
||||
End to end data application synchronization protocols, FT Store, interfacing with long term storage, message bus guarantees, possibly CRDTs etc. Guiding principle is to provide additional guarantees for users of Waku (etc) in terms of user experience.
|
||||
|
||||
## P2P/Networking
|
||||
Things related to P2P protocols and networking, including usage of WebRTC, Discovery for resource restricted devices, new p2p protocols with different trade-offs etc.
|
||||
|
||||
R&D related to P2P protocols and networking, including usage of WebRTC,
|
||||
Discovery for resource restricted devices,
|
||||
and new p2p protocols with different trade-offs.
|
||||
|
||||
## Censorship resistance
|
||||
Censorship resistance at all layers of the stack, including obfuscated transports, running in hostile environments, etc.
|
||||
|
||||
Censorship resistance at all layers of the stack, including obfuscated transports and running in hostile environments.
|
||||
|
||||
## Identity/Trust
|
||||
Identity and key management required for non-trivial secure messaging. Multi device management, group management, trust, reputation etc. Especially in a private and secure fashion.
|
||||
|
||||
Identity and key management required for non-trivial secure messaging.
|
||||
This includes multi device management, group management, trust, and reputation.
|
||||
Especially in a private and secure fashion.
|
||||
|
|
|
|||
75
vac.md
75
vac.md
|
|
@ -1,78 +1,35 @@
|
|||
---
|
||||
title: Main
|
||||
---
|
||||
# Vac researches peer-to-peer, private, censorship resistant communication.
|
||||
|
||||
# Vac - Communication, Privacy, Etc.
|
||||
|
||||
## About Vac
|
||||
Vac is an R&D org creating modular p2p protocols for private, secure, censorship resistant communication.
|
||||
|
||||
### Researching All Layers
|
||||
Concerned with all layers in the stack including underlying transports, p2p overlays and routing, initial trust establishment, and semantics for things like group chat.
|
||||
Vac **builds** [public good](https://en.wikipedia.org/wiki/Public_good) protocols for the decentralized web.
|
||||
|
||||
### Peer-to-Peer
|
||||
The protocols we work on are pure peer-to-peer, and aim to minimize centralization. This too is in opposition to many initiatives in the secure messaging space.
|
||||
We do applied research based on which we build protocols, libraries and publications. Custodians of protocols that reflect [a set of principles](vac.dev/principles) - liberty, privacy, etc.
|
||||
|
||||
### Security, Privacy, Censorship Resistance
|
||||
Assumes the basics such as end-to-end encryption, forward secrecy, avoiding MITM-attacks. Vac also places a premium on privacy and censorship resistance from port blocking, traffic analysis, and similar.
|
||||
## Our Principles
|
||||
|
||||
### Modular System
|
||||
Provide options at each layer in the stack, instead of having a tightly coupled set of protocols. Allowing developers to choose what they use and ensure they know each choice comes with different trade-offs.
|
||||
Liberty, censorship resistance, security, privacy, transparency, openness, decentralization, inclusivity, continuance, resourcefulness.
|
||||
|
||||
These principles act as tools. Tools for thinking, for communication, and for decentralized decision making. They keep us honest about where we are failing short of our vision.
|
||||
|
||||
### Generalized Messaging
|
||||
This includes both human to human communication, as well as machine to machine communication. Texting, data transfer, financial transactions, state channels and more.
|
||||
The meaning of these principles are elaboarted on here: [Vac Principles](vac.dev/principles).
|
||||
|
||||
## Principles
|
||||
## Projects
|
||||
|
||||
The goal of Vac is widespread adoption of the decentralized web. Our challenge is achieving mass adoption while staying true to our principles outlined below.
|
||||
**Secure Messaging**. We design modular, p2p protocols for private, anonymous, secure and censorship-resistant communications. The main focus is [Waku](https://waku.org), the communication layer for Web3.
|
||||
|
||||
### I. Liberty
|
||||
**zk-WASM**. Research into making private and provable computation using WASM that is verified using zero-knowledge proofs.
|
||||
|
||||
We believe in the sovereignty of individuals. As a research organization that stands for the cause of personal liberty, we aim to maximize social, political, and economic freedoms. This includes being coercion-resistant.
|
||||
**RAD - RFCs & Dissemination**. We build specifications for self-sustainable robust protocols with strong and modular privacy guarantees. Rough consensus and running code. We also write papers and aim to collaborate closely with other institutions to build a bridge between industry and academia.
|
||||
|
||||
### II. Censorship resistance
|
||||
**Applied ZK & Explorations**. We build tools to enable new fundamental building blocks using cutting-edge zero-knowledge proof systems.
|
||||
|
||||
We enable free flow of information. No content is under surveillance. We abide by the cryptoeconomic design principle of censorship resistance. Even stronger, we design agnostic infrastructures for information.
|
||||
## Links
|
||||
|
||||
### III. Security
|
||||
|
||||
We don't compromise on security when building features. We use state-of-the-art technologies, and research new security methods and technologies to make strong security guarantees.
|
||||
|
||||
### IV. Privacy
|
||||
|
||||
Privacy is the power to selectively reveal oneself to the world. For us, it's essential to protect privacy in both communications and transactions, as well as pseudo-anonymity. Additionally, we strive to provide the right of total anonymity.
|
||||
|
||||
### V. Transparency
|
||||
|
||||
We strive for complete openness and symmetry of information within the organization, and have no border between our core contributors and our community. We are frank about our shortcomings, especially when making short-term tradeoffs in service of our long-term goals.
|
||||
|
||||
### VI. Openness
|
||||
|
||||
The software we create is a public good. It is made available via a free and open source license, for anyone to share, modify and benefit from. We believe in permission-less participation.
|
||||
|
||||
### VII. Decentralization
|
||||
|
||||
We minimize centralization across both the software and the organization itself. In other words, we maximize the number of physical computers composing the network, and maximize the number of individuals who have control over the system(s) we are building.
|
||||
|
||||
### VIII. Inclusivity
|
||||
|
||||
We believe in fair and widespread access to our software, with an emphasis on ease-of-use. This also extends to social inclusivity, permissionless participation, interoperability, and investing in educational efforts.
|
||||
|
||||
### IX. Continuance
|
||||
|
||||
We create software incentivized to continue to exist and improve, without the stewardship of a single entity or any of the current team members.
|
||||
|
||||
### X. Resourcefulness
|
||||
|
||||
We are relentlessly resourceful. As we grow and have ready access to capital, it is our obligation to token holders to fight bureaucracy and inefficiencies within the organization. This means solving problems in the most effective way possible at lower economic costs (in terms of capital, time and resources).
|
||||
|
||||
## Research
|
||||
The research team is focused on research and specifications of protocols within the general scope of Vac. Waku v2 is the current main focus, and the main client is nim-waku.
|
||||
|
||||
[Go to research page](/research)
|
||||
|
||||
Vac RFCs: https://rfc.vac.dev/ |
|
||||
Specs repo: https://github.com/vacp2p/rfc |
|
||||
Board: https://github.com/orgs/vacp2p/projects/5 |
|
||||
Forum: https://forum.vac.dev/
|
||||
- [Write-ups](/research)
|
||||
- [Vac RFCs](https://rfc.vac.dev)
|
||||
- [Forum](https://forum.vac.dev)
|
||||
|
|
|
|||
Loading…
Reference in New Issue