Celo Core Contracts Release 13

Proposal Key Aspects

  • Receiver Entity: Celo Governance
  • Status: DRAFT
  • Title: Celo Core Contracts Release 13
  • Author(s): cLabs Primitives Team
  • Type of Request: **Smart Contract Changes
  • Funding Request: N/A

Summary

This is a routine Core Contracts release following the standard release process. This release removes code that is no longer used with Celo as an L2.

Motivation

This proposal reduces gas usage of commonly called Core Smart Contracts. Removing code also helps with readability and maintenance, limiting the surface for attack.

Specification

The contracts will match the latest contract release, as described here.

Metrics and KPIs

N/A

Current Status

Ready to be submitted on-chain.

Timeline and Milestones

To be submitted on chain as soon as the off-chain governance process is completed.

Detailed Budget

N/A

Payment Terms

N/A

Team

N/A

Additional Support/Resources

Audit report to be uploaded as soon as completed.

3 Likes

Thanks @martinvol and team for the proposal, at my end this proposal is fulfilling all the requirements:

  • Post a proposal in the Celo Forum and leave it for discussion at least for seven (7) days.
  • Present Proposal in a Governance Call and address the feedback received: Proposal was presented during Celo Governance Call #70 | Jun 26th, 2025

With the above said, from my end the proposal is ready to move into the voting phase when proposer wants to move forward or consider is appropriate.


:bangbang: Remember Current Celo Governance Overview & Procedures

To proceed to the submission and voting phase at least two Celo Governance Guardians must post explicitly that the proposal fulfills the requirements to be able to move into the Voting Stage in the proposal thread on the Celo Forum.


Remember next steps

  • Submission of PR to Celo Governance Repository
    Proposers needs to fork the Celo Governance Repository and add a PR including the proposal .md file and json file.
  • Approval of PR by Celo governance Guardians and merge into main branch of Celo Governance Repository.
    Celo Guardians are responsible for conducting a comprehensive review of every Pull Request (PR) to ensure that there is complete alignment and consistency between the final proposal posted in the forum post and the specific files that are being requested to be merged.
    This review process is strictly technical in nature, focusing solely on verifying the authenticity and good faith of the proposers. It does not involve any personal opinions or biases regarding the merits or content of the proposal itself. To maintain the integrity of the Celo Governance repository, it is mandatory to obtain approval from a minimum of two Governance Guardians for each PR before it can be merged into the main branch.
  • OnChain Submission of Proposal
    After PR is merged into main Governance Repo the proposers needs to fork locally the Celo Governance Repository and submit the proposal onchain using the guidelines described in the Celo Docs.

CC: Governance Working Group (@annaalexa @Wade @0xGoldo)

1 Like

Thanks @martinvol. Confirming as a governance guardian, the criteria has been met as per @0xj4an-work post and this proposal is ready to move forward to the next stage.