Specifications for Status clients. https://specs.status.im/
Go to file
Oskar Thorén 347fbbef1f
Merge pull request #86 from status-im/lifecycle
Update spec lifecycle
2020-03-24 14:13:20 +08:00
assets Update spec lifecycle 2020-03-24 14:11:07 +08:00
CNAME add CNAME for GH pages 2020-03-23 10:58:39 +01:00
README.md Update spec lifecycle 2020-03-24 14:11:07 +08:00
_config.yml Update _config.yml 2020-03-23 12:42:44 +01:00
status-EIPs.md transpose table 2019-11-28 02:03:26 -02:00
status-account-spec.md removed profile and user chosen name 2020-02-12 15:56:40 -05:00
status-client-spec.md update bootnodes to eth.prod 2020-02-19 11:58:46 +01:00
status-group-chats-spec.md replace transit with protobuf 2020-01-21 08:39:56 +01:00
status-payloads-spec.md Apply suggestions from code review 2020-01-21 20:12:18 +01:00
status-secure-transport-spec.md Merge pull request #47 from kdeme/typos-and-fixes 2019-09-18 17:12:13 +03:00
status-session-management-spec.md Update secure transport 2019-09-12 08:31:11 +02:00
status-whisper-mailserver-spec.md Update status-whisper-mailserver-spec.md 2019-12-13 09:23:49 -08:00
status-whisper-usage-spec.md Add message confirmations spec (#74) 2019-12-16 11:40:54 +01: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

No stable specs right now. De facto a lot of the draft ones are stable and indicating this is work in progress.

Draft

The following SIPs are under consideration for standardization.

Raw

No raw specs right now.

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.