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

Move payloads to stable

This commit is contained in:
Oskar Thoren 2020-03-24 16:05:35 +08:00
parent 966e3f5aad
commit bf6218647f
No known key found for this signature in database
GPG Key ID: B2ECCFD3BC2EF77E
2 changed files with 7 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
README.md
View File

@ -27,12 +27,13 @@ The following SIPs are stable and running in production.
- [Status Account Specification](status-account-spec.md). What a Status account is and how trust is established.
- [Status Payload Specification](status-payloads-spec.md). What the message payloads look like.
### Draft
The following SIPs are under consideration for standardization.
- [Status Client Specification](status-client-spec.md). The main specification for writing a Status client. **Start here**
- [Status Payload Specification](status-payloads-spec.md). What the message payloads look like.
### Raw

8
status-payloads-spec.md
View File

@ -1,8 +1,10 @@
# Status Message Payloads Specification
> Version: 0.1 (Draft)
> Version: 0.2
>
> Authors: Adam Babik <adam@status.im>, Oskar Thorén <oskar@status.im> (alphabetical order)
> Status: Stable
>
> Authors: Adam Babik <adam@status.im>, Andrea Maria Piana <andreap@status.im>, Oskar Thorén <oskar@status.im> (alphabetical order)
## Abstract
@ -316,6 +318,6 @@ There are two ways to upgrade the protocol without breaking compatibility:
## Security Considerations
TBD.
-
## Design rationale