This proposal requests funding from the unreleased CELO treasury to support the next six months of work by Celo Core Co., the newly unified core contributor organization formed through the alignment of cLabs and the Celo Foundation.
Season 3 marks an important milestone in Celo's evolution. Earlier this year, cLabs and the Celo Foundation merged into Celo Core Co., bringing together protocol development, ecosystem growth, partnerships, communications, operations, and execution under a single organization. This structure is designed to improve coordination, increase execution velocity, and ensure that protocol development and ecosystem growth remain closely aligned around shared objectives.
The requested funding supports two primary areas of work:
This proposal covers the period from July through December 2026 and continues the community funding model established in previous seasons, with milestone-based reporting and accountability.
The first half of 2026 represented a significant transition period for the Celo ecosystem.
During this period, cLabs successfully delivered major protocol milestones including the Jovian hardfork, continued progress toward Espresso integration, improvements to network performance and security, and ongoing stewardship of ecosystem-critical infrastructure.
At the same time, the Celo Foundation continued supporting ecosystem growth through strategic partnerships, builder programs, MiniPay ecosystem expansion, industry engagement, and marketing and communications efforts that helped maintain Celo's position as one of the most actively used Ethereum Layer 2 ecosystems. To read more about the progress made over Season 2, please visit the cLabs and Celo Foundation retrospectives.
Recognizing the increasing importance of coordination between protocol development and ecosystem growth, cLabs and the Celo Foundation aligned operations under a single organization, Celo Core Co.
Season 3 represents the first funding cycle under this new operating model.
North Star: Increase number of users and make it easier and cheaper to bring money onchain
The focus of Season 3 is to grow real, organic usage of Celo and make bringing money onchain easier and cheaper, advancing our position as the leading blockchain ecosystem for real-world adoption while strengthening the foundations for long-term ecosystem sustainability. The way we will collectively work towards this north star breaks down into the following protocol and ecosystem objectives:
Protocol & Product Objectives
Ecosystem Objectives
Season 3 adopts monthly chain revenue (gross fees) as our north star metric. Unlike transaction counts or TVL, chain revenue can't be inflated by incentives or wash activity — someone has to find Celo useful enough to pay for it. It also captures quality of usage rather than volume, is less exposed to market conditions, and ties directly to long-term network sustainability: as fees grow, so does the value flowing back to the protocol and its community.
Importantly, this growth does not come at users' expense: the median cost per transaction on Celo remains sub-cent, so revenue scales with usage, not with what any individual user pays.
We've already shown this metric can move fast. Over the past season, monthly chain revenue has grown roughly 10x, to ~$125,000 per month on average, driven by increased minimum base fees, MiniPay growth, stablecoin activity, and rising organic transaction demand. Season 3 is about proving that growth compounds sustainably through payment partner onboarding, local fiat-backed stablecoins, agentic use cases, and continued MiniPay expansion, rather than one-off spikes.
Chain revenue also drives value accrual to CELO directly: as fees grow, so does the CELO purchased through the protocol's fee mechanism, aligning network usage with the long-term interests of CELO holders, a core focus of the ongoing Tokenomics Initiative.
The second half of the year is focused on big protocol upgrades, higher throughput, tighter security, better infrastructure, and research that shapes what comes next. As always, sequencing may shift as dependencies get finalized.
You can read more about the milestones and planned protocol and product development work for the second half of 2026 in the H2 Engineering Roadmap.
| Cost Category | Details | Total Cost (USD) |
|---|---|---|
| Fully Loaded Engineering Costs | Core protocol engineering, DevOps, security, product, infrastructure and tooling contributors | 838,000 |
| Infrastructure & Tooling | Cloud services, monitoring, testing, analytics, developer infrastructure | 197,000 |
| Total | 1,035,000 |
The ecosystem portion of this proposal supports the programs, partnerships, and growth initiatives required to continue expanding Celo adoption globally.
Adoption & Strategic Initiatives — Estimated Budget: 356,000. Supports ecosystem partnerships, commercial relationships, distribution channels, and integrations that expand Celo's reach and utility. This category includes work across stablecoins, payments, financial infrastructure, MiniPay ecosystem expansion, and other strategic initiatives that can drive meaningful ecosystem adoption.
Builder & Ecosystem Growth — Estimated Budget: 490,000. Supports developer onboarding, ecosystem support, builder activation, mini app growth, educational initiatives, AI infrastructure and agentic programs that help cement Celo's reputation as the leading Ethereum L2 for DAUs, and supporting builders from experimentation through production and deployment.
Marketing & Communications — Estimated Budget: 285,000. Supports ecosystem storytelling, media relations, launch coordination, educational content, community communications, and broader awareness efforts that strengthen Celo's position within the industry.
Events & Strategic Ecosystem Presence — Estimated Budget: 130,000. Maintains a focused presence at high-impact industry and developer events aligned with strategic partnerships, ecosystem growth, and business development objectives.
Regional Ecosystem Growth — Estimated Budget: 100,000. Supports regional ecosystem initiatives and contributors that extend Celo's reach into key markets while maintaining coordination with global ecosystem priorities.
| Category | Budget (USD) |
|---|---|
| Adoption & Strategic Initiatives | 356,000 |
| Builder & Ecosystem Growth | 490,000 |
| Marketing & Communications | 285,000 |
| Events & Strategic Ecosystem Presence | 130,000 |
| Regional Ecosystem Growth | 100,000 |
| Total | 1,361,000 |
Celo Core Co. is requesting $2,396,000 in funding for Season 3.
The requested budget combines the protocol development scope historically supported through cLabs funding proposals and the ecosystem growth scope historically supported through Celo Foundation funding proposals.
Final CELO-denominated amounts will be calculated using the 90 day trailing average CELO price at the time of proposal submission, consistent with previous funding proposals.
Unused funds will be returned to the Community Fund or rolled forward subject to community governance approval.
This request represents a cumulative reduction of more than 12.6% from Season 2's combined funding across cLabs and the Celo Foundation. The unification into Celo Core Co. allowed us to streamline operations and reduce overhead, and we've made deliberate, and at times difficult, decisions to run a leaner organization. We believe stewarding community funds responsibly means doing more with less, and this budget reflects that commitment while preserving full capacity to deliver on the Season 3 roadmap.
This proposal covers Season 3 (July–December 2026).
As with Season 1 and 2, Celo Core Co. will publish a Season 3 retrospective outlining outcomes, learnings, and measurable impact.
Funds will be withdrawn to a Celo Core Co. controlled multisig upon approval from the unreleased CELO treasury.
Celo Core Co. Multisig: 0xB0D0780eDDC2FA35906C0b37B9b4Dc7583C3DbB0
The multisig is a Gnosis Safe on Celo mainnet with a 3-of-5 signer threshold.
The proposal releases 31,609,499 CELO from the CeloUnreleasedTreasury to the Governance contract (the Community Fund) and increases the Celo Core Co. multisig's CELO allowance by the same amount, allowing the multisig to withdraw the funds via transferFrom.
CeloUnreleasedTreasury.release is callable only by the contract registered as EpochManager in the Registry, so — following the precedent of cgp-0207, cgp-0232, cgp-0238, and cgp-0246 — the Registry entry is temporarily pointed at Governance for the duration of the release and restored immediately afterwards.
increaseAllowance is used instead of approve so that any pre-existing CELO allowance to the multisig is preserved rather than overwritten (as of authoring, that allowance is 0).
Temporarily set Governance as EpochManager in the Registry
setAddressFor(string, address)"EpochManager", 0xD533Ca259b330c7A88f74E000a3FaEa2d63B7972 (Governance)Release 31,609,499 CELO from the unreleased treasury to Governance
release(address, uint256)Restore EpochManager in the Registry to the original address
setAddressFor(string, address)"EpochManager", 0xF424B5e85B290b66aC20f8A9EAB75E25a526725E (EpochManager)Increase the Celo Core Co. multisig CELO allowance by 31,609,499 CELO
increaseAllowance(address, uint256)[
{
"contract": "Registry",
"address": "0x000000000000000000000000000000000000ce10",
"function": "setAddressFor",
"args": ["EpochManager", "0xD533Ca259b330c7A88f74E000a3FaEa2d63B7972"],
"value": "0",
"description": "Temporarily set Governance as EpochManager in Registry"
},
{
"contract": "CeloUnreleasedTreasury",
"address": "0x7A8c7a833565fc428cdFBa20FE03fAfb178A434f",
"function": "release",
"args": [
"0xD533Ca259b330c7A88f74E000a3FaEa2d63B7972",
"31609499000000000000000000"
],
"value": "0",
"description": "Release 31,609,499 CELO from the unreleased treasury to Governance (Community Fund)"
},
{
"contract": "Registry",
"address": "0x000000000000000000000000000000000000ce10",
"function": "setAddressFor",
"args": ["EpochManager", "0xF424B5e85B290b66aC20f8A9EAB75E25a526725E"],
"value": "0",
"description": "Restore EpochManager in Registry to original address"
},
{
"contract": "GoldToken",
"address": "0x471EcE3750Da237f93B8E339c536989b8978a438",
"function": "increaseAllowance",
"args": [
"0xB0D0780eDDC2FA35906C0b37B9b4Dc7583C3DbB0",
"31609499000000000000000000"
],
"value": "0",
"description": "Increase the Celo Core Co multisig CELO allowance by 31,609,499"
}
]
Once the proposal is submitted on-chain, a human readable version can be inspected with:
$ celocli governance:show --proposalID <ID> --node https://forno.celo.org
Voters can verify that:
EpochManager entry — transaction 3 restores it to the current on-chain value (0xF424B5e85B290b66aC20f8A9EAB75E25a526725E, verifiable via Registry.getAddressForString("EpochManager")).release on the CeloUnreleasedTreasury proxy (0x7A8c7a833565fc428cdFBa20FE03fAfb178A434f, verifiable via Registry.getAddressForString("CeloUnreleasedTreasury")) with the Governance contract (0xD533Ca259b330c7A88f74E000a3FaEa2d63B7972) as recipient — funds move from the unreleased treasury into the Community Fund, not to any external party.increaseAllowance on the CELO token (0x471EcE3750Da237f93B8E339c536989b8978a438) for the Celo Core Co. multisig (0xB0D0780eDDC2FA35906C0b37B9b4Dc7583C3DbB0) — a 3-of-5 Gnosis Safe on Celo mainnet, matching the address published in the forum post.This proposal does not deploy or upgrade contracts and does not permanently change network parameters, so it represents minimal risk to the network.
EpochManager Registry entry is modified and restored within the same atomic proposal execution; no intermediate state is observable by other transactions.increaseAllowance (rather than approve) preserves any pre-existing allowance.