mirror of https://github.com/status-im/specs.git
Update status-whisper-usage-spec.md
This commit is contained in:
Dean Eigenmann
GitHub
parent
54f4b7def2
commit
a92aaa5093
|
|
@ -10,11 +10,6 @@
|
|||
- [Terminology](#terminology)
|
||||
- [Basic Assumption](#basic-assumption)
|
||||
- [Protocol Overview](#protocol-overview)
|
||||
- [Payload](#payload)
|
||||
- [Content types](#content-types)
|
||||
- [Message types](#message-types)
|
||||
- [Clock vs Timestamp and message ordering](#clock-vs-timestamp-and-message-ordering)
|
||||
- [Replies](#replies)
|
||||
- [Whisper adapter](#whisper-adapter)
|
||||
- [Whisper node configuration](#whisper-node-configuration)
|
||||
- [Keys management](#keys-management)
|
||||
|
|
@ -91,65 +86,6 @@ Offline messaging describes how the protocol handles delivering messages when on
|
|||
|
||||
The protocol does not specify additional things like peers discovery, running Whisper nodes, underlying p2p protocols etc.
|
||||
|
||||
# Payload
|
||||
|
||||
Payload is an array of bytes exchanged between peers. In the case of this protocol, the payload is encoded using [transit format](https://github.com/cognitect/transit-format). It is a text-based format so even encoded version is easily readable by humans.
|
||||
|
||||
Payload contains the following fields:
|
||||
1. text `string`
|
||||
2. content type `enum { text/plain }` (more in [Content types](#content-types))
|
||||
3. message type `enum { public-group-user-message, user-message, group-user-message }` (more in [Message types](#message-types))
|
||||
4. clock `int64`
|
||||
5. timestamp `int64`
|
||||
6. content `struct { chat-id string, text string }`
|
||||
|
||||
Example of a valid encoded payload:
|
||||
|
||||
```
|
||||
["~#c4",["abc123","text/plain","~:public-group-user-message",154593077368201,1545930773682,["^ ","~:chat-id","testing-adamb","~:text","abc123"]]]
|
||||
```
|
||||
|
||||
As you can see, the message is an array and each index value has its meaning:
|
||||
* 0: `c4` is a decoder handler identification for the current payload format. Identifications allow to register handlers for many different types of payload
|
||||
* 1: array which items correspond to the described payload fields above
|
||||
|
||||
For more details regarding serialization and deserialization please consult [transit format](https://github.com/cognitect/transit-format) specification.
|
||||
|
||||
## Content types
|
||||
|
||||
Content types are required for a proper interpretation of incoming messaages. Not each message is a plain text but may carry a different information.
|
||||
|
||||
The following content types MUST be supported:
|
||||
* `text/plain` identifies a message which content is a plain text
|
||||
* `sticker` TODO
|
||||
* `status` TODO
|
||||
* `command` TODO
|
||||
* `command-request` TODO
|
||||
* `emoji` TODO
|
||||
|
||||
TODO: select which are required and which are client-specific.
|
||||
|
||||
## Message types
|
||||
|
||||
Message types are required to decide how a particular message is encrypted (more in [Whisper > Message encryption](#message-encryption)) and what metadata needs to be attacjed (more in [Whisper > Topic](#topic)) when passing a message to the transport layer.
|
||||
|
||||
The following messages types MUST be supported:
|
||||
* `public-group-user-message` is a message to the public group
|
||||
* `user-message` is a private message
|
||||
* `group-user-message` is a message to the private group.
|
||||
|
||||
## Clock vs Timestamp and message ordering
|
||||
|
||||
`timestamp` MUST be Unix time calculated when the message is created. Because the peers in the Whisper network should have synchronized time, `timestamp` values should be fairly accurate among all Whisper network participants.
|
||||
|
||||
`clock` SHOULD be calculated using the algorithm of [Lamport timestamps](https://en.wikipedia.org/wiki/Lamport_timestamps). When there are messages available in a chat, `clock`'s value is calculated based on the last received message in a particular chat: `last-message-clock-value + 1`. If there are no messages, `clock` is initialized with `timestamp`'s value.
|
||||
|
||||
`clock` value is used for the message ordering. Due to the used algorithm and distributed nature of the system, we achieve casual ordering which might produce counterintuitive results in some edge cases. For example, when one joins a public chat and sends a message before receiving the exist messages, their message `clock` value might be lower and the message will end up in the past when the historical messages are fetched.
|
||||
|
||||
## Replies
|
||||
|
||||
TBD
|
||||
|
||||
# Whisper adapter
|
||||
|
||||
Whisper in version 6 has been chosen as an messages exchange protocol because it was designed as an off-chain communication layer for the Ethereum nodes. It supports e2e encryption and uses epidemic spread to route data to all members of the network. It also provides [darkness to some extent](https://github.com/ethereum/go-ethereum/wiki/Achieving-Darkness).
|
||||
|
|
|
|||
Loading…
Reference in New Issue