On April 23, 2020, Coinbase introduced a signed price feed for the BTC-USD and ETH-USD markets, giving decentralized-finance applications a new way to import prices from Coinbase Pro. The Coinbase Price Oracle exposed signed data through an API, refreshed it once per minute and made its output compatible with Compound’s open-source Open Oracle contracts.
The launch mattered because lending, derivatives and collateral systems running on Ethereum could execute automatically but could not discover off-chain market prices by themselves. A bad or manipulated reference price could trigger wrongful liquidations, misprice collateral or allow an attacker to extract value. Coinbase was offering its exchange data and key-management infrastructure as an institutional input to that problem.
What Coinbase actually launched
Coinbase said any party could request the BTC-USD and ETH-USD observations, relay them on-chain and verify the signature against Coinbase’s public key. The relayer therefore did not have to be trusted to reproduce the payload faithfully. That design separated publication from transport: Coinbase signed the observation, while someone else could pay to submit it to an Ethereum contract.
The distinction is important. A valid signature proves that Coinbase produced the message; it does not prove that Coinbase’s market was immune to disorder, that its signing key could never be compromised or that its price represented every trading venue. Coinbase described three safeguards: sourcing from Coinbase Pro, rejecting observations that deviated sharply from expected volatility before signing, and using an on-chain anchor in Compound’s design to reject sufficiently divergent submissions. Those were architectural claims in Coinbase’s April 23 announcement, not an independent guarantee that losses or manipulation were impossible.
Compound’s Open Oracle repository described a broader standard in which reporters signed key-value pairs and users could post them to a blockchain. Its view layer could combine reports into aggregates such as a median. Coinbase compatibility consequently gave developers a recognizable publisher and a common message format, but a system relying only on Coinbase would still depend on one exchange and one signer.
Why the timing mattered
Oracle design was already a live security question in early 2020. DeFi protocols were combining composable smart contracts, on-chain liquidity and automated liquidations, increasing the consequences of a distorted price input. Coinbase’s move put a large centralized exchange directly into Ethereum’s developing financial infrastructure without requiring Coinbase itself to operate every consuming application.
The launch also marked a boundary between centralized data production and decentralized execution. The feed did not make Coinbase decentralized. It made Coinbase’s observations portable and cryptographically attributable, allowing a protocol to combine them with other reporters or an on-chain reference. The security gain therefore depended on how each application configured its oracle, anchors, update rules and fallback behavior.
Coinbase described the service as immediately available on April 23, 2020. Contemporaneous coverage from The Block and Decrypt independently reported the same two market pairs, Coinbase Pro sourcing and signed-data model. Neither report established usage, adoption or a measured reduction in exploits on the launch date.
What was not yet established
On April 23, compatibility with Compound’s contracts was not the same as adoption by Compound governance. No event-day record cited here shows that every DeFi protocol began using the feed, that the feed secured a particular dollar amount, or that it eliminated oracle risk. The central verifiable development is narrower: Coinbase released a signed, minute-by-minute BTC-USD and ETH-USD data service designed for on-chain use.
Later context
In August 2020, Compound governance proposal 019 described using Coinbase Oracle data with a Uniswap time-weighted average-price check. That later proposal helps explain the April launch’s practical path but should not be read back into the April 23 state of the protocol. Coinbase’s official exchange changelog later recorded the Price Oracle API as deprecated on January 1, 2025; that later endpoint status does not alter what Coinbase launched in 2020.
The complete source packet and revision history are retained with the newsroom record.
Automated systems may have assisted with source organization and drafting. Coinburn is accountable for the published text and maintains a revision record.
This article provides news and analysis, not investment, legal or tax advice. Digital assets are volatile and may result in total loss.