From 38ce4ebf5576537011293a0c16c30723663f2584 Mon Sep 17 00:00:00 2001 From: kdeme Date: Wed, 18 Sep 2019 15:49:14 +0200 Subject: [PATCH] Update status-whisper-usage-spec.md Review update Co-Authored-By: Adam Babik --- status-whisper-usage-spec.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/status-whisper-usage-spec.md b/status-whisper-usage-spec.md index ea70f1b..3000a24 100644 --- a/status-whisper-usage-spec.md +++ b/status-whisper-usage-spec.md @@ -284,7 +284,7 @@ Receiving public messages depends on Whisper filters idea. Upon receiving, messa 1. Calculate a symmetric key using [`shh_generateSymKeyFromPassword`](https://github.com/ethereum/go-ethereum/wiki/Whisper-v6-RPC-API#shh_generatesymkeyfrompassword) passing public chat name as a string and save the result to `symKeyID` 2. Call [`shh_subscribe`](https://github.com/ethereum/go-ethereum/wiki/Whisper-v6-RPC-API#shh_subscribe) with criteria: - 1. `minPow` MAY be at least `0.002` + 1. `minPow` MUST be `0.002` at most 2. `topics` MUST be list of hex-encoded topics you expect messages to receive from (follow [Topic](#topic) section) 3. `allowP2P` MUST be set to `true` if offline messages are supported, otherwise can be `false`.