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

Updated Whisper Push Notifications (markdown)

Victor Farazdagi 2017-04-13 08:25:02 +03:00
parent dd1c094b47
commit eb9769c815
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Whisper-Push-Notifications.md

@ -11,7 +11,7 @@ It is crucial to understand what is **Whisper Notification Service** is designed
[![image](https://cloud.githubusercontent.com/assets/188194/24991150/72bb9f44-2021-11e7-80c0-39699e8aeaae.png)](https://cloud.githubusercontent.com/assets/188194/24991150/72bb9f44-2021-11e7-80c0-39699e8aeaae.png)
The crux here is how to allow `DeviceB` to trigger notifications on `DeviceA`, all this w/o knowing much of which wnode is used, or details of `DeviceA`. And `Chat SymKey` solves this issue elegantly (the beauty is that it works for both one-on-one and group chats, all you need to ensure is share `ChatID` and `Chat SymKey` so that newcomers can add their devices to subscribers list).
The crux here is how to allow `DeviceB` to trigger notifications on `DeviceA`, all this w/o knowing much of which wnode is used, or details of `DeviceA`. And `Chat SymKey` solves this issue elegantly (the beauty is that it works for both one-on-one and group chats, all you need to ensure is share a secret, namely `Chat SymKey`, so that newcomers can add their devices to subscribers list).
**Important Notes:**
- `Device A` starts the protocol by broadcasting using Discovery Protocol SymKey. However, `statusd wnode` command (that is used to start notification-enabled wnodes) also supports using asymmetric keys to kick off the process. For further details, see examples below.