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

move basic assumptions from x7 to statu sspec

This commit is contained in:
Oskar Thoren 2019-08-27 16:11:36 +02:00
parent aa5f5fb23d
commit 1276f412b9
No known key found for this signature in database
GPG Key ID: B2ECCFD3BC2EF77E
2 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
status-spec.md
View File

@ -69,6 +69,9 @@ allows for TCP-based communication between nodes.
On top of this we run the RLPx-based subprotocol [Whisper
v6](https://eips.ethereum.org/EIPS/eip-627) for privacy-preserving messaging.
There MUST be an Ethereum node that is capable of discovering peers and
implements Whisper V6 specification.
## Node discovery and roles
There are four types of node roles:
@ -159,6 +162,10 @@ communicate with other Status nodes.
Once a Whisper node is up and running there are some specific settings required
to commmunicate with other Status nodes.
Worth noting is that in Whisper time MUST be synced between all nodes
participating in the given network. A clock drift between two peers larger than
20 seconds MAY result in discarding incoming messages.
### Node configuration
Whisper's Proof Of Work algorithm is used to deter denial of service and various

9
x7.md
View File

@ -37,14 +37,7 @@
* *Envelope*: encrypted message with some metadata like topic and TTL sent between Whisper nodes; a symmetric or asymmetric key is needed to decrypt it and read the payload
* *Offline message*: an expired envelope stored by a Whisper node permanently
# Basic Assumption
This protocol assumes the following:
1. There MUST be an Ethereum node that is capable of discovering peers and implements Whisper V6 specification.
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.
# Perfect Forward Secrecy (PFS)
Perfect Forward Secrecy (PFS)
Additionally to encrypting messages on the Whisper level, the protocol supports PFS specification.