acid-info
/
vac.dev
mirror of https://github.com/acid-info/vac.dev.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

drop unused faq.md file 

Signed-off-by: Jakub Sokołowski <jakub@status.im>
This commit is contained in:
Jakub Sokołowski 2022-01-11 20:56:13 +01:00 committed by Jinho Jang
parent 7083a22ba9
commit 57225b2c60
1 changed files with 0 additions and 37 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

37
faq.md
View File

@ -1,37 +0,0 @@
---
layout: page
permalink: /faq/
title: FAQ
---
## Are there messaging protocols out there that you feel live up to your security and privacy Standards? Where does Signal fall in?
There are a lot of protocols out there and new ones come up every day, in terms of fitting our requirements on
scalability, decentralization, security and privacy we've yet to find one that works just as is, which is why we are
developing our own.
Signal is using a centralized server, but they provide many protocols. [Status](https://status.im) for example used a modified version of
Signal's Double Ratchet and X3DH key exchange for encryption and forward secrecy in their app.
So kudos to them for that work!
You can find this in status client specification [here](https://specs.status.im/spec/1).
## Are there any benefits to building messaging protocols for Ethereum? Is Waku a long term solution?
Waku is completely separate from Ethereum, the only overlap is that a lot of components such as P2P protocols are the
same. Future incentivization schemes are likely to use Ethereum in terms of deposits and settlement, but that's it.
Waku is more scalable than Whisper, but it still has a lot of issues. We aim to address these in an incremental manner
until it works as a long term solution and stands the test of time.
## What are the key privacy tradeoffs between Waku and Whisper?
First off, the privacy guarantees provided by Whisper are mostly theoretical at this stage. They've not received a lot
of scrutiny from academic researchers and so on.
There are a few trade-offs that allow Waku to be more scalable and suitable for resource restricted devices than Whisper.
It is worth noting that all of these are [optional](https://rfc.vac.dev/spec/6/#packet-usage), and a Waku client can choose to get all the privacy benefits by turning these options off:
1. Light client means mobile nodes don't relay messages that aren't their own.
2. Mailserver for offline messaging means a mailserver knows which messages you are requesting and what your IP is.
3. Fetching messages by topic instead of bloom filter means there's less (none) false positives, which reveal that you care about certain topics more.