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-13 08:25:41 +03:00
parent eb9769c815
commit 78ddd0a99e
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

@ -14,7 +14,7 @@ It is crucial to understand what is **Whisper Notification Service** is designed
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). 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:** **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. - `Device A` can start 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.
- It is important to understand that notification request messages go *along* the normal communication i.e. - It is important to understand that notification request messages go *along* the normal communication i.e.
- on `DeviceA` you send encrypted message to `DeviceB` (so, only `DeviceB` can open envelope) - on `DeviceA` you send encrypted message to `DeviceB` (so, only `DeviceB` can open envelope)
- once done, you need to send a broadcast message encrypting it with `Chat SymKey` - once done, you need to send a broadcast message encrypting it with `Chat SymKey`