Celo Started Its Mainnet Release Candidate on Earth Day

Celo’s first mainnet release candidate began operating on April 22, 2020, moving the mobile-focused payments protocol from test networks into a persistent proof-of-stake network intended to become its main chain.

Celo’s launch plan assigned the genesis block a timestamp of 16:00 UTC. Genesis validators were instructed to have their nodes ready so block production could begin once the network reached quorum. The plan also called for deployment of Celo’s core contracts and ReleaseGold contracts for validator awards.

An April 28 report from validator operator Staked subsequently confirmed that Release Candidate 1, or RC1, went live at noon Eastern time on April 22. The Celo Foundation’s 2020 annual report later described the same Earth Day gathering of community validators as a successful mainnet launch.

A mainnet candidate, not an unrestricted network

The terminology needs qualification. On April 22, Celo described RC1 as a network that could graduate into mainnet if it survived a controlled ramp-up without a restart-worthy defect. The event therefore established genesis and block production, but it did not make every planned protocol function immediately available.

Validator elections and epoch rewards remained scheduled to be unfrozen through governance proposals at the beginning of May. Voter rewards and ordinary transfers of Celo Gold, then abbreviated cGLD, were expected to remain restricted until another governance step planned for May 18. Activation of the stability protocol was scheduled still later.

Those restrictions meant April 22 was not a conventional public token-market launch. Holders could not infer an unrestricted cGLD market price from the network’s genesis, and the reviewed sources provide no reliable event-day price, trading-volume or market-capitalization measurement. The central development was technical and institutional: independent operators had started maintaining a persistent ledger under a staged governance process.

The possibility of restarting RC1 was explicit. Celo said a new build would be created if defects prevented the candidate from graduating. That contingency distinguished the event from promotional claims that every component of the platform was complete at genesis.

The design being tested

Celo was being developed as a social-payments protocol designed around mobile access. Its white paper proposed mappings between telephone numbers and public keys so users could locate payment recipients without exchanging long hexadecimal addresses. It also described stable-value assets backed by a reserve and governed through elastic supply rules.

Those features framed why the network mattered, but they should not be mistaken for proven April 22 adoption. Genesis demonstrated that validators could start the chain and support its core contracts. It did not establish that phone-number-based payments were secure at scale, that a stable asset would hold its target value or that the governance system would remain broadly distributed.

The launch also represented a different security model from proof-of-work networks such as Bitcoin. Celo’s roadmap depended on registered validator groups, token-based elections and protocol rewards. During the initial ramp, foundation voting and scheduled governance proposals played substantial roles in forming that operating set. The network’s long-term decentralization therefore remained an objective to be tested, not an accomplished event-day fact.

Later clarification

Celo governance records show that the proposal enabling voter rewards and Celo Gold transfers passed on May 18, 2020. The Celo Foundation later treated April 22 as the mainnet’s launch date, while other records describe May 18 as RC1’s graduation.

Both descriptions can be reconciled: the persistent chain began at genesis on April 22, while transfer and governance restrictions were removed in stages. The defensible event-date conclusion is that Celo successfully started its mainnet candidate—not that every promised payment, stability or decentralization feature was already fully operational.