status-im
/
specs
mirror of https://github.com/status-im/specs.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

remove last x4 stuff

This commit is contained in:
Oskar Thoren 2019-08-27 15:18:18 +02:00
parent 8af9c66717
commit fc948cf7a9
No known key found for this signature in database
GPG Key ID: B2ECCFD3BC2EF77E
2 changed files with 0 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
README.md
View File

@ -27,7 +27,6 @@ The following SIPs are under consideration for standardization.
Badly scoped:
- [Initial Protocol Overview](x4.md)
- [Initial Trust Establishment Specification](x5.md)
- [Initial Transport Privacy through Whisper Specification](x7.md)

11
x4.md
View File

@ -1,11 +0,0 @@
# Conversational Security Layer
# Transport privacy layer
The purpose of the transport privacy layer is to hide metadata (provide darkness) that are always sent when communicating over the internet. In some cases, leaked metadata might be as dangerous as leaking the actual payload so it's important to reduce that.
The Status Protocol uses [Whisper in version 6](https://github.com/ethereum/wiki/wiki/Whisper) as a privacy protection protocol. Whisper routes messages by broadcasting them to all connected peers so that identifying of the recipient is almost impossible (the sender is not equally protected, though). [Read more](https://github.com/ethereum/go-ethereum/wiki/Achieving-Darkness) about how Whisper achieves darkness.
Note: there is one more cross-layer dependency in the Status Protocol between the privacy and data layers. Whisper uses topics to reduce traffic and preliminarily filter out messages. However, selecting a topic depends on the type of the message that is a topic for 1-1 chat will be different from a topic for a public chat.
Please refer to [Initial Transport Privacy through Whisper Specification](x7.md) for more details.