mirror of https://github.com/status-im/specs.git
39 lines
1.7 KiB
Markdown
39 lines
1.7 KiB
Markdown
# 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](status-client-spec.md). The main specification for writing a Status client.
|
|
- [Status Secure Transport Specification](status-secure-transport-spec.md). How Status provide a secure transport with conversational security properties.
|
|
- [Status Payload Specification](status-payloads-spec.md). What the message payloads look like.
|
|
- [Status Account Specification](status-account-spec.md). What a Status account is and how trust is established.
|
|
- [Status Whisper Usage Specification](status-whisper-usage-spec.md). How we use Whisper to do routing, metadata protection and provide 1:1/group/public chat.
|
|
- [Status Whisper Mailserver Specification](status-whisper-mailserver-spec.md). How we use Whisper mailservers to provide offline inboxing.
|
|
|
|
|
|
## 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](https://specs.vac.dev).
|