From 0a49d1f17ebb35b22f114f8f0c5af65ab9712761 Mon Sep 17 00:00:00 2001 From: Adam Babik Date: Wed, 11 Sep 2019 13:08:31 +0200 Subject: [PATCH] update --- status-whisper-usage-spec.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/status-whisper-usage-spec.md b/status-whisper-usage-spec.md index 6b567e6..df5d6f1 100644 --- a/status-whisper-usage-spec.md +++ b/status-whisper-usage-spec.md @@ -155,11 +155,11 @@ Each Status Client SHOULD listen to this topic in order to receive ??? Generic discovery topic is a legacy topic used to handle all one-to-one chats. The newer implementation should rely on [Partitioned Topic](#partitioned-topic) and [Personal discovery topic](#personal-discovery-topic). -Generic discovery topic MUST be created following [Public chats](#public-chats) topic creation where `name` is equal to `contact-discovery`. +Generic discovery topic MUST be created following [Public chats](#public-chats) topic algorithm using string `contact-discovery` as a name. ### One-to-one topic -In order to listen to one-to-one messages incoming from a public key `P`, the Status Client MUST listen to a [Contact Code Topic](#contact-code-topic) created for the publickey `P`. +In order to receive one-to-one messages incoming from a public key `P`, the Status Client MUST listen to a [Contact Code Topic](#contact-code-topic) created for that public key. ### Group chat topic @@ -175,6 +175,6 @@ One-to-one messages are encrypted using asymmetric encryption. ## Whisper V6 extensions (or Status Whisper Node) -Outside of Whisper v6, there are some extensions, message codes and RPC methods that MAY be useful for client implementers. An implementation of this can be found in a fork of Whisper [here](https://github.com/status-im/whisper). +TOODO - +