| layout | permalink | nav_exclude |
|---|---|---|
default |
/ |
true |
This repository contains a list of specifications for implementing Status and its various capabilities.
You can read about how to build this project here.
- 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 existing SIP editors for review
If you need help, ask in #protocol at Status / Discord.
Become familiar with the specification style guidelines to understand how you should write or amend specifications.
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.
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.
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.
The site is built in Our Jenkins CI based off of master branch.