Coinbase Pro gave Maker’s MKR token a second path to trading

Coinbase announced on May 29, 2020, that Coinbase Pro would make a second attempt to open trading in MakerDAO’s MKR governance token. The exchange planned to accept inbound MKR transfers on June 8 and begin trading on or after 9 a.m. Pacific time on June 9, provided its liquidity requirements were met.

The proposed MKR-USD and MKR-BTC order books mattered beyond the addition of another token. MKR was the governance and recapitalization asset for the Maker Protocol, which issued the dollar-targeting Dai stablecoin. A functioning dollar market on a large U.S.-based exchange could broaden access to an asset used to vote on collateral, risk and monetary parameters inside one of Ethereum’s most established decentralized-finance systems.

Coinbase’s announcement was not an immediate listing. No MKR trading began on Coinbase Pro on May 29, and the token was not yet available through Coinbase’s retail website or consumer applications.

A launch structured around liquidity

Coinbase described four stages. Transfers would open first, followed by post-only trading, limit-only trading and, if the books remained orderly, full trading. The exchange reserved the right to hold an order book at any stage or suspend its progression if market-quality thresholds were not met.

That condition was material because Coinbase Pro had already attempted a limited MKR launch in April 2019. According to Coinbase’s May 29 record, the earlier books did not attract sufficient liquidity and never advanced to executed trades. The 2020 plan was therefore a renewed market-opening process rather than MKR’s first appearance in Coinbase infrastructure.

The distinction also limits what the announcement proved. Coinbase had decided to support deposits and conditionally open order books; it had not guaranteed deep liquidity, continuous trading or retail distribution. Nor did an exchange listing independently validate Dai’s stability mechanisms or the quality of Maker governance.

Why MKR was institutionally different

Maker’s February 2020 white paper described MKR holders as the parties responsible for governing the protocol and its financial risks through polling and executive votes. Their decisions could change collateral eligibility, debt ceilings, stability fees and liquidation parameters. MKR could also be created and auctioned if protocol debt exceeded available surplus, tying the token to the system’s recapitalization design.

That made MKR unlike a token whose principal function was payments. Easier access potentially expanded the market for an asset carrying governance power and exposure to protocol risk. At the same time, putting MKR on a centralized exchange did not decentralize Coinbase or transfer control of the protocol to the exchange. It connected two different structures: a conventional order-book venue and an Ethereum-based governance system.

The market reaction and its limits

A contemporaneous Cointelegraph report, citing the Bitfinex MKR/USD market displayed through TradingView, said MKR rose from roughly $350 to $457 in about 60 minutes after the announcement. Those rounded endpoints imply an increase of approximately 30.6%. This was a single-venue, intraday observation rather than a consolidated closing price, and the timing alone cannot establish that the announcement caused every trade in the move.

For broader context, CoinMarketCap’s May 29 historical snapshot placed bitcoin at $9,439.12, down 0.87% over its displayed 24-hour window. That aggregate snapshot is not an official market close: cryptocurrency trades continuously, prices differ among venues, and the provider’s daily boundary and eligible-market methodology affect the result. The contrast nevertheless shows that the reported MKR move was asset-specific rather than part of a uniformly rising market.

Later context

Coinbase’s subsequently updated record says transfers began on June 8 and trading began on June 9. Coinbase then announced retail MKR support on June 11. Those later milestones confirm that the conditional rollout advanced, but they were not known outcomes on May 29 and should not be folded into the event-day announcement.