| Paper | Celo Whitepaper: A Multi-Asset Cryptographic Protocol for Decentralized Social Payments |
|---|---|
| Author | cLabs Team (as identified in the cited draft) |
| Version | Draft v0.25 |
| Project | Celo |
| License | Not stated in the Celo paper listing |
| Official paper | Read the Celo paper (PDF) |
This page is an educational summary, not a verbatim reproduction or investment advice. CryptoGloss does not claim authorship of the source paper.
The cLabs Team’s draft v0.25 proposes a multi-asset protocol for mobile-centered social payments. It starts from two obstacles to everyday crypto payments: hard-to-use addresses and purchasing-power volatility. Its main ideas are an address-based way to find a recipient’s public key and a reserve-supported design for stable-value assets. This is a historical protocol proposal, not a description of every feature in today’s Celo network.
What the paper set out to solve
The paper asks how a payment system could feel closer to sending value to a person in a contact list while keeping settlement and ownership on a blockchain. It also considers how a payment currency could be less exposed to the price swings of a volatile crypto asset. The proposed system combines lightweight identity, payment flows, reserve management, and governance. The authors present these as a design to evaluate; the proposal alone does not show that the design achieved broad adoption or stable purchasing power in practice.
Address-based encryption: a lookup, not a replacement for keys
In the paper’s address-based encryption design, a familiar identifier such as a phone number can be associated with a user’s public key in a shared registry. The recipient still creates and controls cryptographic keys. A phone number does not become a private key, and it cannot sign a transaction on the user’s behalf. The registry is intended to help a sender discover the right public key and reduce the need to exchange long hexadecimal addresses manually.
The proposal uses attestations to support the association between an identifier and a key. It also discusses hashing and adding a secret “pepper” to make harvesting identifiers harder. That is a privacy measure, not a guarantee of anonymity: phone numbers have a predictable format, and a public mapping can create risks if an identifier is guessed, reused, or taken over. The paper itself describes the tension between convenient lookup and protecting address privacy.
Stable-value assets and the reserve
The paper’s monetary design aims to reduce purchasing-power volatility through stable-value assets, an elastic supply mechanism, and a shared reserve. It describes reserve composition, price discovery, and governance as parts of the system. The basic idea is to adjust supply and use reserve assets in response to market conditions, rather than claim that a token’s value is fixed by software alone.
A target price is not the same as a guaranteed redemption at that price. The design depends on market demand, liquidity, reserve quality and valuation, and the rules governing changes to supply and reserves. Those dependencies can shift risk among holders, reserve assets, and the protocol; they do not remove risk. The details in this draft should not be treated as a complete account of later Celo stablecoin products or their current operation.
Governance is part of the design
The paper gives governance a role in maintaining the protocol, responding to reserve conditions, and improving the system. That flexibility can support changes to the monetary design, but it also means outcomes depend on who can make decisions, how those decisions are implemented, and whether users and markets continue to trust them. Reading the reserve mechanism without its governance assumptions would leave out an important part of the proposal.
How to read the paper today
The cited document is marked Draft v0.25. It is useful for understanding an earlier Celo design, but it is not a current network specification or security audit. Celo launched its Layer 1 mainnet in April 2020 and completed its transition to an Ethereum Layer 2 in March 2025, according to Celo’s current history documentation. The official Celo paper library also lists Plumo: An Ultralight Blockchain Client as a separate paper; Plumo is not a section of this multi-asset social-payments draft.
In short, this paper is best read as a proposal about convenient payment addressing, stable-value monetary design, and protocol governance. For current chain architecture and services, use current Celo documentation alongside the historical draft.
Related Terms
See Also
- The Dai Stablecoin System (MakerDAO Whitepaper)
- Ethereum: A Next-Generation Smart Contract Platform
- Optimism: Scalable Smart Contracts on Ethereum
Sources
- Celo Whitepaper: A Multi-Asset Cryptographic Protocol for Decentralized Social Payments, Draft v0.25 (PDF) — primary source for the proposed address-based encryption, stable-value assets, reserve, and governance design.
- Celo Whitepapers & Research — official catalog that identifies this paper and lists Plumo as a separate work.
- Celo Docs: Our History — official timeline for the 2020 Layer 1 launch and March 2025 Layer 2 transition.
- Celo Docs: Discover Celo — current introduction describing Celo as an Ethereum Layer 2.