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

Go to file

Volodymyr Kozieiev 36edf7cecb Updated link		2020-05-18 12:00:44 +03:00
assets	Update spec lifecycle	2020-03-24 14:11:07 +08:00
docs	Updated link	2020-05-18 12:00:44 +03: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	Update README.md	2020-03-31 13:30:41 +08:00
_config.yml	Update _config.yml	2020-04-02 12:17:00 +02: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

layout	permalink	nav_exclude
default	/	true

Specifications for Status clients

This repository contains a list of specifications for implementing Status and its various capabilities.

How to contribute

Create an issue for a new Status Improvement Proposal (SIP) or some bug that you'd like to address
Create a corresponding PR and ping some exisiting SIP editors for review

If you need help, ask in #protocol at Status / Discord.

Spec lifecycle

Every spec has its own lifecycle that shows its maturity. We indicate this in a similar fashion to COSS Lifecycle:

At present (March 30, 2020) this means stable specs are what is in v1 of the Status App. Drafts and raw are work in progress specs.

Status Improvement Proposals (SIPs)

The main specification for writing a Status client is 1/CLIENT.

For all full index of all specs, see specs.status.im, especially stable specs.

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.