status-im
/
specs
mirror of https://github.com/status-im/specs.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

move data sync clients to status spec

This commit is contained in:
Oskar Thoren 2019-08-27 15:12:50 +02:00
parent 630d38e47a
commit 66da37dd9c
No known key found for this signature in database
GPG Key ID: B2ECCFD3BC2EF77E
2 changed files with 4 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
status-spec.md
View File

@ -219,7 +219,10 @@ Transport Spec](status-secure-tansport-spec.md) for more.
## Payloads and clients ## Payloads and clients
<!-- TODO: Provide outlink for payloads --> On top of secure transport, we have various types of data sync clients and
payload formats for things like 1:1 chat, group chat and public chat. These have
various degrees of standardization. Please refer to [Initial Message Payload
Specification](x8.md) for more details.
## Design Rationale ## Design Rationale

9
x4.md
View File

@ -1,12 +1,3 @@
Data Sync Clients
Data Sync Clients specify a format of payloads exchanged between clients communicating using the Status Protocol. The robust and well-defined format is required in order to provide some security guarantees, for example, clients should not display messages that do not conform to the format, and allow the clients to upgrade the protocol safely in the future.
The well-defined format also makes it possible to support multiple types of conversations as well as multiple types of content.
Please refer to [Initial Message Payload Specification](x8.md) for more details.
# Data Sync Layer # Data Sync Layer
[MVDS](https://specs.vac.dev/mvds.html) is used for 1:1 and group chats, however it is currently not in use for public chats. [MVDS](https://specs.vac.dev/mvds.html) is used for 1:1 and group chats, however it is currently not in use for public chats.