From 73a07a491170a4da8228528730236f0287c56c25 Mon Sep 17 00:00:00 2001 From: Oskar Thoren Date: Tue, 27 Aug 2019 15:47:23 +0200 Subject: [PATCH] remove intro x7 --- x7.md | 23 ----------------------- 1 file changed, 23 deletions(-) diff --git a/x7.md b/x7.md index 7ed17de..bc1d2b2 100644 --- a/x7.md +++ b/x7.md @@ -44,29 +44,6 @@ This protocol assumes the following: 2. Participants of a given Whisper network in order to communicate with each other MUST accept messages with lowered PoW value. More in (Whisper node configuration)(#whisper-node-configuration). 3. Time MUST be synced between all nodes participating in the given network (this is intrinsic requirement of the Whisper specification as well). A clock drift between two peers larger than 20 seconds MAY result in discarding incoming messages. -# Protocol Overview - -Notice: this protocol is documented post factum. The goal of it is to clearly present the current design and prepare the ground for its second version. - -The implementation of this protocol is mainly done in https://github.com/status-im/status-react and https://github.com/status-im/status-go repositories. - -The goal of this protocol is to allow people running Ethereum nodes with Whisper service enabled to exchange messages that are end-to-end encrypted in a way that guarantees [darkness to some extent](https://github.com/ethereum/go-ethereum/wiki/Achieving-Darkness). - -It's important to notice that messages [are not limited to be text messages](#content-types) only. They can also have special meaning depending on the client implementation. For example, in the current implementation, there are message which informs about Eth requests. - -This protocol consist of three components: -* payload -* Whisper adapter -* offline messaging. - -[The payload section](#payload) describes how the messages are encoded and decoded and what each fields of a message means. This is required to properly interpret messages by the client. - -Whisper adapter specifies interaction with the Whisper service with regards to keys management, configuration and attaching metadata required to properly forward and process messages. - -Offline messaging describes how the protocol handles delivering messages when one or more participants are offline and the messages expire in the Whisper network. - -The protocol does not specify additional things like peers discovery, running Whisper nodes, underlying p2p protocols etc. - # Perfect Forward Secrecy (PFS) Additionally to encrypting messages on the Whisper level, the protocol supports PFS specification.