mirror of https://github.com/acid-info/vac.dev.git
Add/research areas roadmaps (#87)
This commit is contained in:
parent
355708f650
commit
1ae367576a
|
@ -56,4 +56,10 @@ and [AutoNAT](https://docs.libp2p.io/concepts/nat/#hole-punching-stun#autonat).
|
||||||
The main focus of this topic is on researching novel ICE-complementary NAT traversal techniques that are decentralized and have desirable privacy and anonymity properties.
|
The main focus of this topic is on researching novel ICE-complementary NAT traversal techniques that are decentralized and have desirable privacy and anonymity properties.
|
||||||
The topic also comprises integrating and specifying ICE for [Waku v2](https://rfc.vac.dev/spec/10/).
|
The topic also comprises integrating and specifying ICE for [Waku v2](https://rfc.vac.dev/spec/10/).
|
||||||
|
|
||||||
|
# Further Research Collaboration Opportunities
|
||||||
|
|
||||||
|
Besides the open research problems listed in the section above,
|
||||||
|
you may browse our [Research Areas](https://vac.dev/research-areas) page
|
||||||
|
and check our roadmaps for various research topics.
|
||||||
|
|
||||||
|
|
||||||
|
|
|
@ -4,34 +4,50 @@ title: Research areas
|
||||||
|
|
||||||
# Overview
|
# 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.
|
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
|
## 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.
|
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
|
||||||
|
|
||||||
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.
|
Applied ZK opens up the door to many new constructs, especially related to privacy.
|
||||||
|
This research area includes the development of primitives like RLN, Unirep and similar novel constructs,
|
||||||
|
but also research and development related to zero-knowledge technology, such as ZK frameworks like Circom and Halo2, ZK-VM, WASM in the browser, and efficient zk proof systems running on resource-restricted devices.
|
||||||
|
Done in close collaboration with other teams in the space.
|
||||||
|
|
||||||
## Privacy/Anonymity
|
## Privacy/Anonymity
|
||||||
|
|
||||||
Specifically metadata privacy. This includes anonymity studies and providing a modular suite of protocols with clear trade-offs and threat models.
|
Specifically metadata privacy.
|
||||||
|
This includes anonymity studies and providing a modular suite of protocols with clear trade-offs and threat models.
|
||||||
|
|
||||||
|
[Privacy/Anonymity Roadmap](https://github.com/vacp2p/research/issues/107)
|
||||||
|
|
||||||
## Scalability
|
## 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.
|
Making the network scalable in terms of number of nodes, message rate, 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
|
## 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.
|
End-to-end data application synchronization protocols, [FT Store](https://rfc.vac.dev/spec/21/), interfacing with long-term storage, message bus guarantees,
|
||||||
|
possibly [CRDTs](https://en.wikipedia.org/wiki/Conflict-free_replicated_data_type) etc.
|
||||||
|
Guiding principle is to provide additional guarantees for users of Waku (etc) in terms of user experience.
|
||||||
|
|
||||||
## P2P/Networking
|
## P2P/Networking
|
||||||
|
|
||||||
R&D related to P2P protocols and networking, including usage of WebRTC,
|
R&D related to P2P protocols and networking, including usage of WebRTC,
|
||||||
Discovery for resource restricted devices,
|
Discovery for resource-restricted devices,
|
||||||
and new p2p protocols with different trade-offs.
|
and new p2p protocols with different trade-offs.
|
||||||
|
|
||||||
|
[Ambient Peer Discovery Roadmap](https://github.com/vacp2p/research/issues/116)
|
||||||
|
|
||||||
## Censorship resistance
|
## Censorship resistance
|
||||||
|
|
||||||
Censorship resistance at all layers of the stack, including obfuscated transports and running in hostile environments.
|
Censorship resistance at all layers of the stack, including obfuscated transports and running in hostile environments.
|
||||||
|
|
Loading…
Reference in New Issue