status-im/status-go
2
0
Fork 0
mirror of https://github.com/status-im/status-go.git synced 2025-02-06 11:56:01 +00:00
Code Issues Projects Releases Wiki Activity

Updated Whisper Push Notifications (markdown)

Victor Farazdagi 2017-04-11 04:13:48 +03:00
parent 4ac2c359e0
commit be5afc2d3b
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
Whisper-Push-Notifications.md

@ -2,7 +2,8 @@
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, 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, manage blacklists). Among other things, the key can be used to trigger notification, by-passing any black/white lists
- 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
## High-Level Overview of the process