OKExChain Improvement Proposals (KIPs) describe standards for the OKExChain platform, including core protocol specifications, client APIs, and contract standards.

1. Review KIP-1.
2. Fork the repository by clicking "Fork" in the top right.
3. Add your KIP to your fork of the repository.
4. Submit a Pull Request to OKExChain's KIPs repository.

Once your first PR is merged, we have a bot that helps out by automatically merging PRs to draft KIPs. For this to work, it has to be able to tell that you own the draft being edited. Make sure that the 'author' line of your KIP contains either your GitHub username or your email address inside.

• Draft - an KIP that is undergoing rapid iteration and changes.
• Last Call - an KIP that is done with its initial iteration and ready for review by a wide audience.
• Accepted - a Matching trading Engine KIP 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 whether to encode an KIP into their clients as part of a hard fork is not part of the KIP process. If such a decision is made, the KIP will move to final.
• Final (non- Matching trading Engine ） - an KIP that has been in Last Call for at least 2 weeks and any technical changes that were requested have been addressed by the author.
• Final (Matching trading Engine） - an KIP that the Core Devs have decided to implement and release in a future hard fork or has already been released in a hard fork.

The canonical URL for a KIP that has achieved draft status at any point is at https://github.com/okex/KIPs. For example, the canonical URL for EIP-1 is https://github.com/okex/KIPs/blob/master/KIP-1.md.