|
| 1 | +--- |
| 2 | +cgp: 231 |
| 3 | +title: Celo Infrastructure for Chain Lifecycle Operational Support (CICLOPS) Season 2 Funding Request |
| 4 | +date-created: 2026-02-19 |
| 5 | +author: 'Nauman Mustafa (@nauman)' |
| 6 | +status: DRAFT |
| 7 | +discussions-to: https://forum.celo.org/t/celo-infrastructure-for-chain-lifecycle-operational-support-ciclops-season-2-funding-request |
| 8 | +governance-proposal-id: |
| 9 | +date-executed: |
| 10 | +--- |
| 11 | + |
| 12 | +Proposal Description |
| 13 | +============================ |
| 14 | +This proposal requests $2.7M equivalent to 21,738,286 CELO at 90 day average price of $0.1242 in Season 2 funding to continue operating CICLOPS as Celo's core infrastructure coordination and support function. Following Celo's successful transition to an Ethereum Layer-2 and a full Season 1 of stable operations, Season 2 shifts the focus from transition to sustained operation, upgrades, and scaling. The funding will ensure that critical infrastructure such as wallets, indexers, oracles, explorers, data availability, and monitoring remains reliable, upgrade-ready, and aligned with cLabs' H1 2026 technical roadmap. Funds will be used exclusively to pay infrastructure vendors, with CICLOPS contributors continuing to serve in an unpaid oversight and coordination role, emphasizing reliability, cost efficiency, and operational continuity as the network evolves. |
| 15 | + |
| 16 | +Additionally, this proposal includes a transfer of 43,012,777.340972869827370586 CELO from the Governance Reserve to the Community Fund. The Community Fund currently has insufficient balance to fulfill approved and pending proposals. This transfer will replenish the Community Fund to ensure that existing approved proposals as well as future proposals can execute their approved fund claims. |
| 17 | + |
| 18 | +Read the full proposal and discussion on the [forum post](https://forum.celo.org/t/celo-infrastructure-for-chain-lifecycle-operational-support-ciclops-season-2-funding-request). |
| 19 | + |
| 20 | +Proposed Changes |
| 21 | +============================ |
| 22 | +## Transaction Descriptions |
| 23 | +1. Transfer 43,012,777.340972869827370586 CELO from Governance Reserve to Community Fund |
| 24 | + - GovernanceReserve (`0x9d65E69aC940dCB469fd7C46368C1e094250a400`) |
| 25 | + - Data: transferCollateralAsset(address collateralAsset = `0x471EcE3750Da237f93B8E339c536989b8978a438` (Celo), |
| 26 | + address payable to = `0xD533Ca259b330c7A88f74E000a3FaEa2d63B7972` (Community Fund), |
| 27 | + uint256 value = `43012777340972869827370586`) |
| 28 | + - Value: 0 |
| 29 | + |
| 30 | +2. Approve 21,738,286 CELO allowance for CICLOPS Multisig |
| 31 | + - Destination: GoldToken (`0x471EcE3750Da237f93B8E339c536989b8978a438`) |
| 32 | + - Data: increaseAllowance(spender = `0xd71efa410B6EaAB0bAc3b515B393C886BE70F09E`, value = `21738286000000000000000000`) |
| 33 | + - Value: 0 |
| 34 | + |
| 35 | +## Json Script |
| 36 | +```json |
| 37 | +[ |
| 38 | + { |
| 39 | + "contract": "ReserveProxy", |
| 40 | + "address": "0x9d65E69aC940dCB469fd7C46368C1e094250a400", |
| 41 | + "function": "transferCollateralAsset", |
| 42 | + "args": [ |
| 43 | + "0x471EcE3750Da237f93B8E339c536989b8978a438", |
| 44 | + "0xD533Ca259b330c7A88f74E000a3FaEa2d63B7972", |
| 45 | + "43012777340972869827370586" |
| 46 | + ], |
| 47 | + "value": "0" |
| 48 | + }, |
| 49 | + { |
| 50 | + "contract": "GoldToken", |
| 51 | + "address": "0x471EcE3750Da237f93B8E339c536989b8978a438", |
| 52 | + "function": "increaseAllowance", |
| 53 | + "args": [ |
| 54 | + "0xd71efa410B6EaAB0bAc3b515B393C886BE70F09E", |
| 55 | + "21738286000000000000000000" |
| 56 | + ], |
| 57 | + "value": "0" |
| 58 | + } |
| 59 | +] |
| 60 | +``` |
| 61 | + |
| 62 | +Verification |
| 63 | +============================ |
| 64 | +A human readable version of this proposal can be found using the following command (on-chain ID determined after submission): |
| 65 | + |
| 66 | +`$ celocli governance:show --proposalID xxx --node https://forno.celo.org` |
| 67 | + |
| 68 | +Risks |
| 69 | +============================ |
| 70 | +This proposal does not deploy or upgrade contracts or change network parameters so represents minimal risk to the network. |
| 71 | + |
| 72 | +The CICLOPS funding component does not transfer funds directly from the Community Fund, but rather seeks an approval to pull funds from the fund, which means that the funds will not be lost if the approval address has a typo. |
| 73 | + |
| 74 | +The Reserve-to-Community-Fund transfer (Transaction 1) moves 43,012,777 CELO to replenish the Community Fund for current and future proposals. This is a direct transfer and should be verified carefully. |
| 75 | + |
| 76 | +CELO token value fluctuation could affect execution capacity. |
| 77 | + |
| 78 | +Useful Links |
| 79 | +============================ |
| 80 | +- [Forum Post](https://forum.celo.org/t/celo-infrastructure-for-chain-lifecycle-operational-support-ciclops-season-2-funding-request) |
0 commit comments