Hi @Dappsoverapps, thank you for submitting your updated post and for your continued interest in contributing to the Celo ecosystem. We would like to clarify a few important points regarding your request to present on today’s governance call.
First, this proposal appears to be materially the same initiative that was previously submitted and reviewed in August. At that time, your team was already scheduled to present but did not attend the call. When the request was made again thirty days ago, we explained that the proposal needed to be brought into alignment with the required template before being considered for inclusion in a governance call agenda.
The template and structure are still not fully aligned with the required format. Calls serve as the venue for reviewing proposals that are ready for community discussion, and we cannot add items that do not meet the basic submission standards. This is not meant to block contribution, it is simply part of ensuring that governance follows consistent and predictable processes.
Second, this proposal sits outside the defined scope for Season 1 Intent. The Ecosystem Growth budget for Season 1 has already been fully allocated to proposals that were reviewed, approved, and are currently being executed. The Community Fund is not intended to reopen mid-season for additional allocations. Predictability is important for governance planning, and shifting budget cycles ad hoc would undermine that stability.
Of course, Celo governance is permissionless. Anyone may choose to submit a proposal on chain. However, being able to submit does not mean that a proposal will receive alignment signals from governance reviewers when it falls outside the current season parameters.
Our recommendation remains that you explore whether this initiative fits within existing ecosystem programs. Prezenti has specific filters tied to Season 1 Intent. If those do not apply to your use case, there are alternative builder oriented initiatives such as CeloPG and Proof of Ship which are designed to support projects like this in a more suitable and structured way.
Hi everyone, quick update regarding the Governance Call that was originally planned for today.
Due to the Devconnect events currently taking place and the Thanksgiving week ahead, we will postpone the call to ensure active participation from contributors and teams across the ecosystem.
The next Governance Call is now scheduled for 4 December.
Unfortunately, this proposal will not be available for presentation in this call. Kindly request it again for the next call once you meet the requirements of at least seven (7) days posted in the forum and allow discussion and let other user have enough time to read it and digest it so they can bring up meaningful questions during the governance presentation call.
It would be great if you could follow the same format as the other proposers. You can find more details in this forum post.
If it makes sense, I would like to ask for a 5 minutes slot on the next CGC to make a call for the Celo governance community to participate on decentralizing the Recy Network governance.
It would greatly help us on creating more resilience and scalability on building a world free of waste pollution.
The main aim for the Governance call is to present and discuss Celo governance Proposals.
That’s said, we would be more than happy to give you a bit of space, if there is still some time inside our 1-hour call after we discuss both items in today’s agenda.
I feel sure that at one time someone has suggested an ultra small fee, like 0.00001 in compliance with new rules regarding crypto protocols to accrue to the token value and utility as Ginsburg implores. I implore it too. If not, it seems that centralized stocks will eat our lunch not to mention our heart. Ginsburg may not be a technical guy and I for sure am not. That’s why we implore the Celo team and not he and I directly to get to this critical issue. It takes more than a burn. Please put together a ultra small fee for a vote. Thanks.
To add topics to the agenda, post a comment below.
FYI We have added
