This is the Celo Governance repository used for coordination by the community members.
The CGP Editors are:
- Juan Giraldo (@juanjgiraldoc)
- Maya Richardson-Brown (@Maya-R-B)
- Wade Abel (@0xzoz)
- Lorenzo Goldoni (@0xGoldo)
- Will Kraft (@willkraft)
- Eric Nakagawa (@ericnakagawa)
- Chris Wilson (@calicokittencat)
Emeritus CGP Editors are:
- Ronan McGovern (@Pinotio)
- Elizabeth Barnes (@ebethbarnes)
- Yaz Khoury (@YazzyYaz)
We regularly hold governance calls to discuss proposals. See below for a summary of past calls.
| № | Date | Agenda | Notes | Recording |
|---|---|---|---|---|
| 31 | June 14, 2023 | Agenda | Notes | Video |
| 30 | May 30, 2023 | Agenda | Notes | Video |
| 29 | April 28, 2023 | Agenda | Notes | Video |
| 28 | April 14, 2023 | Agenda | Notes | Video |
| 27 | March 24, 2023 | Agenda | Notes | Video |
| 26 | February 28, 2023 | Agenda | Notes | Video |
| 25 | January 26, 2023 | Agenda | Notes | Video |
| 24 | December 8, 2022 | Agenda | Notes | Video |
| 23 | November 17, 2022 | Agenda | Notes | Video |
| 22 | October 13, 2022 | Agenda | Notes | Video |
| 21 | August 25, 2022 | Agenda | Notes | Video |
| 20 | August 10, 2022 | Agenda | Notes | Video |
| 19 | July 21, 2022 | Agenda | Notes | Video |
| 18 | June 16, 2022 | Agenda | NA | Video |
| 17 | June 7, 2022 | Agenda | Notes | Video |
| 16 | February 24, 2022 | Agenda | Notes | Video |
| 15 | January 20, 2022 | Agenda | Notes | Video |
| 14 | November 18, 2021 | Agenda | Notes | Video |
| 13 | October 14, 2021 | Agenda | Notes | Video |
| 12 | September 23, 2021 | Agenda | Notes | Video |
| 11 | September 9, 2021 | Agenda | Notes | Video |
| 10 | August 19, 2021 | Agenda | Notes | Video |
| 9 | August 5, 2021 | Agenda | Notes | Video |
| 8 | June 17, 2021 | Agenda | Notes | Video |
| 7 | April 29, 2021 | Agenda | Notes | Video |
| 6 | April 8, 2021 | Agenda | Notes | Video |
| 5 | March 25, 2021 | Agenda | Notes | Video |
| 4 | February 4, 2021 | Agenda | NA | Video |
| 3 | January 5, 2021 | Agenda | NA | Video |
| 2 | December 3, 2020 | Agenda | NA | Video |
| 1 | November 6, 2020 | Agenda | NA | Video |
Governance is, at its core, all about how a group of people working together makes decisions. Celo has an on-chain governance mechanism for working as a community to make decisions. This documentation is designed for proposal creators and people interested in creating proposals, and it aims to give them the base of knowledge necessary for creating and championing a proposal. This article summarizes the most important details proposal creators should be aware of, and the following links provide additional details:
The following points summarize the key context for Celo governance:
What is Celo Governance?
Celo Governance is the structure and process that allows stakeholders to make changes to the Celo protocol.
Why does governance matter?
Governance allows anyone to shape the direction of the Celo community. This is vital for the operation and longevity of the protocol.
Who is involved in governance?
Key stakeholders in Celo’s governance process include: Proposal Creator, Editor, Approvers, Voters and Validators. See the Governance Process Roles section of this article below.
When and where do votes happen?
Discussions about changes to the protocol happen on forum.celo.org and are announced in the Celo Discord #celo-governance channel. Token holders can vote on on-chain proposals at celo.stake.id.
How much time is involved?
Once a proposal is submitted on Github, it can be submitted on-chain along with a deposit of 100 CELO, and community members have 28 days to signal they’d like to vote for the proposal on-chain. It will be proposed onto the chain one day later for token holders to vote on it. After seven days, if it passes, anyone will be able to introduce it on-chain.
This is an abbreviated description of the governance process and the steps needed to move the proposal through each phase. See the Governance Process and Technical Guide articles for more details.
These are the minimum steps needed to move a proposal through the governance process. There are several best practices that are strongly encouraged in order to ensure adequate community buy-in, and these are covered in the Best Practices for Proposal Creators section below.
1. Create Proposal
- Create a JSON file that would execute the changes you’re proposing if passed.
- Create a Celo Governance Proposal (CGP) with a description of the changes and submit to GitHub.
- After submitting to GitHub, CGP Editors will review the clarity and feasibility of the CGP and may reach out with feedback.
2. Submission
- Submit your proposal using the Celo Command Line Interface (Celo CLI). This includes a 100 CELO deposit.
- Locked CELO holders vote on proposals in this phase each day, and the top 3 proposals each day move on to the Approval phase.
- If your proposal is not in the top 3 on any day for 28 days, it expires and your deposit is burned. In practice, the volume of proposals is low enough that proposals generally clear this phase (i.e. not dozens of proposals per month).
3. Approval
- Withdraw your deposit using Celo CLI.
- To move on from this phase, the proposal needs to be approved by the Approvers (a 3 of 9 multi-signature address held by individuals selected by the Celo Foundation).
- Approvers have 1 day to review the proposal.
- The Approvers may reach out with questions, so be ready to communicate with them.
4. Referendum
- This is the main phase of the governance process, as it determines whether the community will adopt your proposal.
- This phase is a community vote that lasts one week, and any Locked CELO holder can vote. Their votes are weighted by the number of Locked CELO they have.
5. Execution
- The proposal creator is generally responsible for implementing the proposal when it passes the referendum.
- The proposal must be executed within 3 days of passing the referendum. The proposal is executed using the Celo CLI.
Celo governance is community-driven, and because of that, a lot of the tips below revolve around soliciting and incorporating community feedback and keeping all key stakeholders and the broader community informed and engaged throughout the process. Although individuals or small groups generally create proposals, the proposal creation process should feel less like an individual effort and more like solving a problem by working together with the broader community. To that end, we recommend following these best practices:
1. Before Drafting a Proposal
- Evaluate Whether Necessary: Before doing any work, make sure the proposal is needed and isn’t already being worked on by checking on celo.forum.org and asking on Discord. Skim through active CGP proposals and the Celo forum to ensure that the idea isn’t already being discussed or proposed and warrants its own CGP.
- Initial Community Feedback: Get high-level feedback from the community to improve and gauge your idea’s support. Create a forum post summarizing your idea and share it in the Governance section of the Celo forum to get initial feedback.
- Targeted Feedback: Reach out to stakeholders who would be impacted to get their opinion. Reach out to people with established reputations in the community for feedback (e.g. validators, cLabbers - reachable on the Discord), especially if the proposal would impact them. This can help build support among community members that will be helpful in later stages in the process.
2. Drafting a Proposal
- Create Draft Proposal: Make a GitHub account, create a fork in the governance repository, and draft a proposal. The CGP template can be found here.
- Get Community Feedback: This step should be the main feedback-gathering effort and will be crucial to finalizing your draft into a version you’re confident has broad support.
- Post the draft proposal in the Celo Forum and get feedback on the draft from the community. The Celo Forum is the main place for discussion of governance proposals.
- Let people in Discord, Celo Twitter community, and Celo Telegram groups know about the discussion in the Celo Forum and encourage them to contribute their feedback. Consider posting in #Celo-Governance, #General-Operators, and #General-Core channels in Discord. To reach Validators, send an update in the Celo Signal newsletter.
- Discuss on Governance Call: Give people a chance to discuss the proposal in real-time by discussing the proposal on a governance call. Sign up to Celo Signal and reply to a Celo Signal email to get an item on the agenda for governance calls. This will give stakeholders a final opportunity to contribute their opinion before you submit the proposal on-chain. To ensure the conversation is as effective as possible, let all active conversations (i.e., forum, Discord, etc.) know about the call.
- Pre-Vote Outreach: Give the community a heads up about the timing of the vote, so they’re ready when it happens.
3. Shepherding Proposal through Voting
- Notify Community: Engage the same groups you engaged in the pre-draft process to let them know that the vote is happening. This includes the Celo governance discord, Celo subReddit, Celo Telegram groups, validators, and other key stakeholders who the proposal would impact (see Step 2b for the full list). You can use these templates to share key information about the proposal simply:
- Engage Validators: Once voting starts, engage with validators directly via the validator channel on Discord (can use @validators to notify them) to make sure they understand the proposal, why it’s important, and when the deadline for voting is. Validators may need multiple reminders, but make sure to be respectful in your outreach.
Note: Once a proposal is submitted on-chain, the process moves pretty quickly, so #1 and #2 above happen before the proposal is submitted on-chain.
Proposal Creators
Anyone with a minimum of 100 CELO can submit a proposal for a change to the Celo network. The proposal creator is responsible for creating the proposal, getting community buy-in, and championing the proposal throughout the process.
CGP Editors
Editors review proposal drafts submitted on Github, either accepting pull requests or rejecting pull requests and providing feedback. This review is conducted to ensure the proposal draft conforms to the guidelines on Github. Editors are volunteer positions with ideally a majority filled by Celo community members outside of cLabs.
Approvers
Before a proposal is voted on, it must be approved by Approvers to ensure the proposal is in the best interests of the community and that it’s worth voting on. Nominees of the Celo Foundation serve to approve proposals via a 3 of 9 multi-sig approval.
Voters
Any wallet address that owns Locked CELO is eligible to vote on governance proposals.
Validators
Validators support the proof of stake mechanism of the Celo platform by validating blocks of transactions on the network. Validators must own at least 10,000 locked CELO tokens and be elected as validators by holders of Locked CELO.