Updated Whisper Push Notifications (markdown)

Victor Farazdagi 2017-04-12 04:54:09 +03:00
parent 39169de843
commit 8f367b0b39
1 changed files with 1 additions and 1 deletions

@ -2,7 +2,7 @@
It is crucial to understand what is **Whisper Notification Service** is designed for:
- to augment Whisper/5 functionality, by allowing clients to subscribe to arbitrary node that has service enabled
- once subscribed, client receives randomly generated symmetric key (`SubscriptionKey`), which is used to control subscription (say, manage blacklists). Among other things, the key can be used to trigger notification, by-passing any black/white lists
- once subscribed, client receives randomly generated symmetric key (`SubscriptionKey`), which is used to control subscription (say, generating chat keys).
- using `SubscriptionKey`, new chat sessions can be initiated (yielding yet another SymKey - `ChatKey`). By sharing that key with others, you will have a common secret that can be used to trigger notifications.
- everywhere possible, Whisper protocol itself was used. For example, discovery mechanism is nothing more but Whisper message exchanges between parties. The same goes for notification sending. The aim was to keep the Service as slim as possible