Specifications for Status clients. https://specs.status.im/

Go to file

Oskar Thoren 7f6e022926 explicit layouts		2020-03-30 13:34:21 +08:00
assets	Update spec lifecycle	2020-03-24 14:11:07 +08:00
specs	explicit layouts	2020-03-30 13:34:21 +08:00
.remarkrc	Update .remarkrc	2020-03-26 13:41:42 +01:00
.travis.yml	adds remark	2020-03-26 13:30:37 +01:00
CNAME	add CNAME for GH pages	2020-03-23 10:58:39 +01:00
README.md	Re order readme	2020-03-27 15:27:24 +08:00
_config.yml	Update _config.yml	2020-03-23 12:42:44 +01:00
default.html	explicit layouts	2020-03-30 13:34:21 +08:00
home.html	explicit layouts	2020-03-30 13:34:21 +08:00
package.json	Update package.json	2020-03-26 13:32:53 +01:00
post.html	explicit layouts	2020-03-30 13:34:21 +08:00

README.md

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.