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

Go to file

Oskar Thoren 03c22ad0b8 fmt		2019-08-29 12:49:20 +02:00
README.md	status-spec -> status-client-spec	2019-08-29 12:34:26 +02:00
status-account-spec.md	Account spec toc, fmt, rfc like	2019-08-29 12:37:02 +02:00
status-client-spec.md	remove dup	2019-08-29 12:35:34 +02:00
status-payloads-spec.md	payloads spec formatting, rfc etc	2019-08-29 12:42:43 +02:00
status-secure-transport-spec.md	secure transport a bit fmt, still mess tho	2019-08-29 12:45:43 +02:00
status-whisper-usage-spec.md	fmt	2019-08-29 12:49:20 +02:00

README.md

Specifications for Status clients

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

Current state

As of August 2019, we are currently in the process of documenting current specifications. We are als implementing an isolated reference library for them. These specifications are expected to be frozen at the Status V1 launch and be used as a reference point for client implementers and security audits.

Status Improvement Proposals (SIPs)

Accepted

No accepted SIPs right now.

Draft

The following SIPs are under consideration for standardization.

Status Client Specification. The main specification for writing a Status client.
Status Secure Transport Specification. How Status provide a secure transport with conversational security prperties.
Status Payload Specification. What the message payloads look like.
Status Account Specification. What a Status account is and how trust is established.
Status Whisper Usage Specification. How we use Whisper to do routing, metadata protection and provide 1:1/group/public chat.

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.