Merge pull request #90 from status-im/spec-stable/account

Move Account to stable

README.md

@@ -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
 

status-account-spec.md

@@ -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.
+In this specification we explain what Status account is, and how trust is established.
 
 ## Table of Contents
 
@@ -108,6 +110,7 @@ not do this.
 **Trust establishment deals with users verifying they are communicating with who they think they are.**
 
 ### Terms Glossary
+
 | term | description |
 | ---- | ----------- |
 | privkey | ECDSA secp256k1 private key |
@@ -214,4 +217,4 @@ All messages sent are encrypted with the public key of the destination and signe
 
 ## Security Considerations
 
-TBD.
+-