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

Move Account to stable

This commit is contained in:
Oskar Thoren 2020-03-24 15:51:23 +08:00
parent 072dd83724
commit eae8a82d5f
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

@ -25,13 +25,14 @@ The following SIPs are stable and running in production.
- [Status Whisper Usage Specification](status-whisper-usage-spec.md). How we use Whisper to do routing, metadata protection and provide 1:1/group/public chat.
- [Status Account Specification](status-account-spec.md). What a Status account is and how trust is established.
### 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.
- [Status Account Specification](status-account-spec.md). What a Status account is and how trust is established.
### Raw

8
status-account-spec.md
View File

@ -1,12 +1,14 @@
# Status Account Specification
> Version: 0.1 (Draft)
> Version: 0.2
>
> Status: Stable
>
> Authors: Corey Petty <corey@status.im>, Oskar Thorén <oskar@status.im> (alphabetical order)
## Abstract
TBD.
What a Status account is and how trust is established.
## Table of Contents
@ -214,4 +216,4 @@ All messages sent are encrypted with the public key of the destination and signe
## Security Considerations
TBD.
-