2.4 KiB
| layout | permalink | nav_exclude |
|---|---|---|
| default | / | true |
Specifications for Status clients
This repository contains a list of specifications for implementing Status and its various capabilities.
Spec lifecycle
Every spec has its own lifecycle that shows its maturity. We indicate this in a similar fashion to COSS Lifecycle:
Status Improvement Proposals (SIPs)
Stable
The following SIPs are stable and running in production.
-
Status Client Specification. The main specification for writing a Status client. Start here
-
Status Secure Transport Specification. How Status provide a secure transport with conversational security properties.
-
Status Whisper Mailserver Specification. How we use Whisper mailservers to provide offline inboxing.
-
Status EIPs Standards. Ethereum Improvement Proposals used in Status.
-
Status Whisper Usage Specification. How we use Whisper to do routing, metadata protection and provide 1:1/group/public chat.
-
Status Account Specification. What a Status account is and how trust is established.
-
Status Payload Specification. What the message payloads look like.
-
Status EIPs Standards. Ethereum Improvement Proposals used in Status.
Draft
The following SIPs are under consideration for standardization.
Raw
These parts are currently underspecified:
- Status Blockchain Usage Specification. How we use the Ethereum blockchain to facilitate the Web3 Browser and Wallet functionality
- Status Storage Usage Specification. How we use decentralized storage solutions to facilitate various Status features.
- Status Browser Specification. How the Status client interacts with both Web3 and Web2.
Deprecated
No deprecated specs right now.
Protocol Research
These are protocols that are currently being researched. These are designed to be useful outside of Status as well. To the extent that these protocols are used within Status clients, they will show up as SIPs in the future.
To see more on this, please visit the current home: vac protocol.