- Date: 2020-05-11
- Author(s): @githubhandle
- Status: DRAFT|PROPOSED|EXECUTED|EXPIRED
- DRAFT = Feedback collection
- PROPOSED = The governance proposal was submitted to the network
- EXECUTED = The governance proposal was executed on the network
- EXPIRED = The governance proposal expired
- Governance Proposal ID #: [if submitted]
- Date Executed: [if executed]
CGP - Celo Governance Proposal
Pick a four digit number subsequent to the latest PR raised and name your file that with the suffic P (for pending). Eg. if the latest PR to the CGP folder was [0034], then your PR should be [0035P].
Describe the issue that motivates this CGP. It should indicate all parameters that are being changed and why doing so is important.
Explain what benefits the enhancement this change will bring. To the extent possible, enumerate use cases affected by this CGP.
Once the proposal is successfully proposed on chain, update this file so that the title number matches the proposal ID.
Fill out the following template for each transaction in the proposal
- Description of transaction 1
- Destination: A human readable description of the address and method being called
- Data: A human readable description of the transaction data
- Value: How much cGLD is being sent, and why?
An explanation of how voters can verify that this CGP does what it intends to do. Can be left as “TODO” until the proposal is made. Include things like CLI commands to run and pointers to code.
Highlight any risks and concerns that may affect consensus, proof-of-stake, governance, protocol economics, the stability protocol, security, and privacy.
- Optional section
- Links to related CIPs or other documents (eg. if this is a proposal to point to a new instance of a smart contract that was updated)