b755aee84c
* 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>
2.2 KiB
title
| 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 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
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 and running in hostile environments.
Identity/Trust
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.