AIPs

ADAMANT Improvement Proposals (AIPs) describe standards for the ADAMANT Messenger platform, including core protocol specifications, and client APIs.

Contributing

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

AIP status terms

Draft: an AIP that is open for consideration
Accepted: an AIP that is planned for immediate adoption, i.e. expected to be included in the next hard fork
Final: an AIP that has been adopted in a previous hard fork
Deferred: an AIP that is not being considered for immediate adoption. May be reconsidered in the future for a subsequent hard fork

AIP Types

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

Standard (16)

Interface (0)

Includes improvements around client API/RPC specifications and standards.

API (2)

API endpoint specifications.

ARC (14)

Application-level standards and conventions, including URI schemes, library/package formats, and wallet formats.

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

Meta (1)

Describes a process surrounding ADAMANT or proposes a change to (or an event in) a process.