mirror of https://github.com/status-im/specs.git
Move Account to stable
This commit is contained in:
parent
072dd83724
commit
eae8a82d5f
|
@ -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 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
|
### Draft
|
||||||
|
|
||||||
The following SIPs are under consideration for standardization.
|
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 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 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
|
### Raw
|
||||||
|
|
||||||
|
|
|
@ -1,12 +1,14 @@
|
||||||
# Status Account Specification
|
# 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)
|
> Authors: Corey Petty <corey@status.im>, Oskar Thorén <oskar@status.im> (alphabetical order)
|
||||||
|
|
||||||
## Abstract
|
## Abstract
|
||||||
|
|
||||||
TBD.
|
What a Status account is and how trust is established.
|
||||||
|
|
||||||
## Table of Contents
|
## Table of Contents
|
||||||
|
|
||||||
|
@ -214,4 +216,4 @@ All messages sent are encrypted with the public key of the destination and signe
|
||||||
|
|
||||||
## Security Considerations
|
## Security Considerations
|
||||||
|
|
||||||
TBD.
|
-
|
||||||
|
|
Loading…
Reference in New Issue