Specifications for Status clients. https://specs.status.im/
Go to file
Oskar Thorén 4961fd613a
Update status-account-spec.md
Co-Authored-By: Dean Eigenmann <7621705+decanus@users.noreply.github.com>
2020-03-27 14:36:18 +08:00
assets Update spec lifecycle 2020-03-24 14:11:07 +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 Move Account to stable 2020-03-27 14:36:16 +08:00
_config.yml Update _config.yml 2020-03-23 12:42:44 +01:00
package.json Update package.json 2020-03-26 13:32:53 +01:00
status-EIPs.md Move Status EIPs to stable 2020-03-24 14:25:08 +08:00
status-account-spec.md Update status-account-spec.md 2020-03-27 14:36:18 +08: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 Revert "Update status-payloads-spec.md" 2020-03-26 20:28:26 +08:00
status-secure-transport-spec.md Update status-secure-transport-spec.md 2020-03-27 14:26:51 +08:00
status-whisper-mailserver-spec.md Address PR comments, legal entity and bloom filter 2020-03-27 14:29:37 +08:00
status-whisper-usage-spec.md update message confirmations section 2020-03-27 14:32:33 +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.

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.