Skip to main content

Community Improvement Proposals

Celo’s Improvement Proposals (CIPs) describe standards for the Celo platform, including the core protocol specifications, SDK, and contract standards. A CIP is a design document that should provide background information, a rationale for the proposal, detailed solution including technical specifications, and, if any, a list of potential risks. The proposer is responsible for soliciting community feedback and for driving consensus.

Participation in the Celo project is subject to the Code of Conduct.

Submitting CIPs

Draft all proposals following the template below and submit to the CIPs repository via a PR (pull request).

CIP template:

  • Summary: Describe your proposal in 280 characters or less.
  • Abstract: Provide a short description of the technical issue being addressed.
  • Motivation: Clearly explain why the proposed change should be made. It should layout the current Celo protocol shortcomings it addresses and why doing so is important.
  • Specification: Define and explain in detail the technical requirements for new features and/or changes proposed.
  • Rationale: Explain the reasoning behind your approach. It should cover alternative approaches considered, related work, and trade-offs made.
  • Implementation: For all proposals going through the governance process, this section should reference the code implementing the proposed change. It’s recommended to get community feedback before writing any code.
  • Risks: Highlight any risks and concerns that may affect consensus, proof-of-stake, governance, protocol economics, the stability protocol, security, and privacy.
tip

For questions, comments, and discussions please use the Celo Forum or Discord.