Skip to main content

CIPs

Overview​

As a decentralized network, major changes to the Conflux protocol need to reach consensus before they can be enacted. Such changes are proposed in the form of a Conflux Improvement Proposal, or CIP for short. After a CIP is discussed, the specification is finalized, and popular support is achieved, a set of CIPs is implemented and rolled out as a network upgrade, also known as a hard fork.

The process of submitting a CIP is described in CIP-1. CIPs have the following stages:

[ IDEA ] -> [ DRAFT ] -> [ LAST CALL ] -> [ ACCEPTED ] -> [ FINAL ]

For more details, please refer to CIP-1.

Highlighted CIPs​

Below are some of the most impactful CIPs since the launch of the Conflux mainnet.

  • CIP-23: Typed structured data hashing and signing. This CIP defined Conflux signature standards, based on Ethereum’s EIP-712.
  • CIP-37: Introduce Base32 Checksum Addresses. The Core Space address format that you’re familiar with from Fluent and other wallets was defined in CIP-37.
  • CIP-40: Reduce block base reward to 2 CFX. In the first hard fork upgrade after mainnet launch, the block base reward was reduced from 7 CFX to 2 CFX. This was also the first CIP that was confirmed in a governance vote.
  • CIP-43: Introduce Finality via Voting Among Staked. This CIP introduced the idea of the hybrid PoW-PoS consensus, implemented in the Hydra hard fork.
  • CIP-90: A Space Fully EVM compatible. The other major update in the Hydra hard fork was the introduction of Conflux eSpace, defined in this CIP.
  • CIP-94: On-chain DAO Vote for Chain Parameters. On-chain mechanism for community governance, to be rolled out in an upcoming network upgrade.

How can I submit a CIP?​

If you want to submit a Conflux Improvement Proposal, you should start by copying the CIP Markdown template and filling some basic information in the preamble, such as the title of this CIP, the list of authors, and the type of the change that. you are proposing. After this, you can proceed to fill all the sections: Simple Summary, Abstract, Motivation, Specification, Rationale, Backwards Compatibility, Test Cases, Implementation, Security Considerations. Once your CIP draft is ready for its initial publication, submit it to the CIPs GitHub repository in a new PR.

Next steps​

Once your CIP draft has been submitted, the CIP editors will review it and address any editorial issues. At this point, you should share the CIP with the Conflux community, start a discussion, find and address issues, and work to achieve popular support for the proposed change or improvement.