Decentralized Cloud Standards (DCSs) describe standards for the Akash platform, including core protocol specifications, client APIs, and SDL standards.


First review DCS-1. Then clone the repository and add your DCS to it. There is a template DCS here. Then submit a Pull Request to Akash's DCS repository.

DCS status terms

DCS Types

DCSs are separated into a number of types, and each has its own list of DCSs.

Standard Track (8)

Describes any change that affects most or all Akash implementations, such as a change to the the network protocol, a change in block or transaction validity rules, proposed application standards/conventions, or any change or addition that affects the interoperability of applications using Akash. Furthermore Standard DCSs can be broken down into the following categories.

Core (5)

Improvements requiring a consensus fork, as well as changes that are not necessarily consensus critical but may be relevant to "core dev" discussions (DCS-2, DCS-8).

Interface (1)

Improvements around client API specifications and standards, and also certain language-level standards like method names (DCS-3).

Economics (2)

Improvements around Akash Economic Model with regards to Staking or Subsidy distribution (DCS-9).

Meta (4)

Describes a process surrounding Akash or proposes a change to (or an event in) a process. Process DCSs are like Standards Track DCSs but apply to areas other than the Akash protocol itself. They may propose an implementation, but not to Akash's codebase; they often require community consensus; unlike Informational DCSs, they are more than recommendations, and users are typically not free to ignore them. Examples include procedures, guidelines, changes to the decision-making process, and changes to the tools or environment used in Akash development. Any meta-DCS is also considered a Process DCS.

Informational (0)

Describes a Akash design issue, or provides general guidelines or information to the Akash community, but does not propose a new feature. Informational DCSs do not necessarily represent Akash community consensus or a recommendation, so users and implementers are free to ignore Informational DCSs or follow their advice.