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:32:02 +03:00
parent e715cd9846
commit 322814122a
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
Whisper-Push-Notifications.md

@ -21,9 +21,9 @@ The crux here is how to allow `DeviceB` to trigger notifications on `DeviceA`, a
- some node over there, will be able to decrypt your broadcast (the only one that has `Chat SymKey`)
- once decrypted, wnode will go over list of device IDs previously registered for this Chat, and send notifications requests to FCM using those IDs (only 1 request for one-on-one chats, `n-1` requests for group of `n` chats - that's we do not notify ourselves)
- So, messages are never exposed, and they are routed in parallel. Notifications are also encrypted (by Chat SymKey), so are not exposed to eavesdropper. This means we are not compromising on darkness. The following info gets exposed though:
- by registering device ID with a given chat session we expose it to `wnode`
- we expose our PubKeys (wnodes need message to be signed, so that you PubKey can be filtered out, and notification by you towards yourself is avoided)
- we may expose some critical information in body of notification message (highly not advised!).
- by registering device ID with a given chat session we expose it to `wnode`
- we expose our PubKeys (wnodes need message to be signed, so that you PubKey can be filtered out, and notification by you towards yourself is avoided)
- we may expose some critical information in body of notification message (highly not advised!).
# Communication Protocol