One of Waku's main design goals is being privacy and anonymity preserving.
While Waku v2 is privacy-preserving, Waku v2 relay currently protects anonymity only in weak attacker models like local attacker and single node attacker.
However, Waku v2 is modular and was designed with pluggable privacy/anonymity in mind.
The following agenda of issues covers our plans to analyse 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.
Issues
(This roadmap is WIP. Items on the roadmap, especially ones farther in the future, might change.)
[x] #106
HackMD covering the current state of Waku v2 Privacy as well as FAQ including Tor and Briar
[ ] Waku Privacy/Anonymity FAQ (to be published on website)
Building on #106, #104, and further results from earlier issues on this roadmap
[ ] integrated Onion Routing for Waku v2
[ ] Waku onion routing protocol RFC
This is an ambitious goal and might be pushed further into the future.
The reason for it being on the roadmap is the desire to be independent of other technologies.
Also, Tor features many centralized elements.
Background / Motivation
One of Waku's main design goals is being privacy and anonymity preserving. While Waku v2 is privacy-preserving, Waku v2 relay currently protects anonymity only in weak attacker models like local attacker and single node attacker.
However, Waku v2 is modular and was designed with pluggable privacy/anonymity in mind. The following agenda of issues covers our plans to analyse 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.
Issues
(This roadmap is WIP. Items on the roadmap, especially ones farther in the future, might change.)