Bitcoin jumped as the Fed made asset purchases open-ended

The verified development

On March 23, 2020, the Federal Reserve replaced quantified minimums for Treasury and agency mortgage-backed-securities purchases with a commitment to buy “in the amounts needed” to restore market functioning and transmit monetary policy. The announcement, released at 8:00 a.m. EDT, also added agency commercial mortgage-backed securities and introduced facilities aimed at corporate credit and asset-backed securities.

Bitcoin reacted sharply around the announcement. CoinDesk’s Bitcoin Price Index reported that BTC rose from $5,860 at 12:00 UTC—the release time—to $6,628 within an hour. That is a 13.1% increase calculated from the two reported index levels. The move did not hold in full: CoinDesk recorded bitcoin at $6,383 at its publication time, up 5.14% over the preceding 24 hours. Those observations describe one index and two specific windows, not a universal bitcoin price across every exchange.

Why the Fed decision mattered to crypto

The Federal Open Market Committee’s wording was the institutional development. On March 15, 2020, the Fed had specified purchases of at least $500 billion in Treasury securities and at least $200 billion in agency mortgage-backed securities. On March 23, it replaced those quantified minimums with an open-ended, needs-based commitment. The same package contemplated as much as $300 billion in new financing through programs supported by $30 billion of Treasury equity.

For bitcoin markets, the decision arrived during an acute global rush for cash. Bitcoin and gold had both fallen heavily between early March and March 23, weakening the simple claim that either asset would automatically protect holders during a liquidity shock. Their immediate rise alongside stock-index futures after the Fed statement showed that bitcoin was trading within the broader macro scramble, not outside it.

The policy also sharpened an argument already familiar in crypto: an asset with a programmed issuance path could look different beside a central bank willing to expand its balance sheet without a preset purchase limit. That was an interpretation available on March 23, 2020, not a demonstrated valuation model. The Fed was targeting market function, employment, prices and credit transmission; it was not announcing a cryptocurrency policy or directly purchasing bitcoin.

What can and cannot be inferred

The timing supports a contemporaneous association between the 8:00 a.m. EDT announcement and the one-hour bitcoin jump reported by CoinDesk. It does not prove that the Fed action alone caused every trade. Bitcoin trades continuously on fragmented venues, and the CoinDesk Bitcoin Price Index is a composite benchmark rather than an official closing auction. Differences in constituents, timestamp conventions and liquidity can produce different highs, lows and daily returns.

Nor did the rebound establish bitcoin as a safe haven. At CoinDesk’s report time, part of the initial gain had already reversed. A one-hour reaction can reflect changing dollar expectations, short covering, cross-asset positioning or thin liquidity as well as longer-term monetary views. The evidence available on March 23 supported a market response; it did not identify the complete order-flow mechanism.

The event-day conclusion

March 23, 2020 marked a consequential junction between emergency monetary policy and digital-asset trading. The primary record establishes that the Fed made asset purchases open-ended and launched additional credit support. The contemporaneous market record establishes that bitcoin briefly surged after the release, then surrendered part of the move.

The significance was not that one policy announcement settled bitcoin’s inflation-hedge or safe-haven case. It was that a decentralized asset with a programmed supply schedule was being repriced in real time against an extraordinary expansion of central-bank support. On the evidence available on March 23, that contrast mattered to market narrative, while the price data still required narrow, benchmark-aware interpretation.