87cab77f20
Image content type for chat messages |
||
|---|---|---|
| assets | ||
| docs | ||
| .remarkrc | ||
| .travis.yml | ||
| CNAME | ||
| README.md | ||
| _config.yml | ||
| default.html | ||
| home.html | ||
| package.json | ||
| post.html | ||
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.