CIPs Gitter RSS

Community Improvement Proposals (CIPs) describe standards for the Genesis platform, including core protocol specifications, APIs, and contract standards.

Contributing

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

CIP status terms

  • Draft - a CIP that is open for consideration and is undergoing rapid iteration and changes.
  • Last Call - a CIP that is done with its initial iteration and ready for review by a wide audience.
  • Accepted - a core CIP that has been in Last Call for at least 2 weeks and any technical changes that were requested have been addressed by the author. The process for Core Devs to decide when and how to encode a CIP into the software is not part of the CIP process. If such a decision is made, the CIP will move to final.
  • Final - a CIP that has been in Last Call for at least 2 weeks and any technical changes that were requested have been addressed by the author.

CIP Types

Community Improvement Proposals describe any change that affects most or all Genesis implementations, such as a change to the the community guidelines, proposed application standards/conventions, or any change or addition that affects the interoperability of applications using Genesis. Furthermore CIPs can be broken down into the following four categories.

Core (2)

Improvements to the core community documents, requiring changes to a core community document, or adding a new core community document. The core commnuity documents can be found here: FIXME.

Governance (0)

Includes improvements around governance for Genesis, including governance contracts, community organization, and foundation. They may propose an implementation, but not to Genesis's codebase; they often require community consensus; hey 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 Genesis development.

Standards (0)

Includes platform-level and application-level standards and conventions, including contract standards such as token standards for in-game items, software development standards, URI schemes, API standards, etc.

GameDev (0)

Describes a Genesis game design or development issue, across game mechanics, lore, art, economy, software, etc.