Skip to content

Latest commit

 

History

History
18 lines (12 loc) · 1.49 KB

README.md

File metadata and controls

18 lines (12 loc) · 1.49 KB
Raw

Casper Enhancement Proposals

CEPs are proposals for improvements to the Casper node, related crates or the surrounding ecosystem. Anyone is free to submit a CEP, but please read the following section on how to create a great proposal:

How to create a CEP

Any CEP starts out with an idea. Some ideas are small enough to be exhaustively discussed in a short Slack conversation before making it into a pull request, there is no need to create a CEP for these. However, after some initial vetting, discussion should be moved into the CEP format using the following process:

  1. Fork the CEP repo at casper-network/ceps.
  2. Create a new branch for your CEP on your private repo, name it accordingly, e.g. my-new-proposal.
  3. Copy the 0000-template.md from the root to text/0000-my-new-proposal.md.
  4. Edit the file, creating the first draft of the CEP.
  5. Once the proposal is ready to be discussed, create a pull request to the CEP repo at casper-network/ceps. This PR will have a number, which is the official CEP number.
  6. Add one commit immediately that updates the file name and links inside the CEP with the assigned number. Afterwards, add a "Rendered" link pointing to the branch-latest file via GitHub on your CEPs branch for easier reading (e.g. https://github.com/yourgitusername/CEPs/blob/my-new-proposal/text/1234-my-new-proposal.md)

History

CEPs were introduced using CEP0001.