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

add abstract, intro and requirements for whisper usage

This commit is contained in:
Oskar Thoren 2019-08-29 14:07:08 +02:00
parent 863352f016
commit e92280e6ee
No known key found for this signature in database
GPG Key ID: B2ECCFD3BC2EF77E
1 changed files with 17 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
status-whisper-usage-spec.md
View File

@ -6,7 +6,19 @@
## Abstract
TBD.
Status uses [Whisper](https://eips.ethereum.org/EIPS/eip-627) to provide
privacy-preserving routing and messaging on top of DevP2P. Whisper uses topics
to partition its messages, and these are leveraged for all chat capabilities. In
the case of public chats, the channel name maps directly to its Whisper topic.
This allows allows anyone to listen on a single channel.
Additionally, since anyone can receive Whisper envelopes, it relies on the
ability to decrypt messages to decide who is the correct recipient. We do
however not rely on this property, but instead implement another secure
transport layer on top of Whisper.
Finally, we use an extension of Whisper to provide the ability to do offline
messaging.
## Table of Contents
@ -35,16 +47,15 @@ TBD.
- [Whisper V6 extensions (or Status Whisper Node)](#whisper-v6-extensions-or-status-whisper-node)
- [New RPC methods](#new-rpc-methods)
## Introduction
TBD.
In this document we detail how we use Whisper to provide for the various chat
use cases, as well how offline inboxing works.
## Requirements
TBD.
<!-- TODO: Elaborate on requirement such as devp2p and possibly Whisper, and geth/parity/nimbus gotchas. -->
An Ethereum node that is connected to peers and implements the Whisper v6
specifications.
## Design goals