Updated Whisper Push Notifications (markdown)

Victor Farazdagi 2017-04-11 04:35:39 +03:00
parent 7904378ea9
commit fd048aa334
1 changed files with 8 additions and 0 deletions

@ -36,6 +36,14 @@ if (!web3.shh.hasSymKey(keyname)) {
```
It is important to understand that this key is publicly known (we will use different password on our cluster, you may use your own password, see `statusd wnode --password` option). So, encryption here doesn't provide privacy - instead, it allows Notification Service capable nodes to filter requests to them (as they will be able to decrypt those messages).
Assume that we have two nodes (`Device A` and `Device B`) which have different underlying nodes:
```javascript
var web3 = new Web3();
web3.setProvider(new web3.providers.HttpProvider('http://localhost:8645')); // Device A
web3.setProvider(new web3.providers.HttpProvider('http://localhost:8745')); // Device B
```
Both nodes have Notification Protocol SymKey added, so can participate in discovery and subscription to Notification Services.
# Discovery and obtaining Subscription Key
Original workflow for discovery mechanism was introduced in: