Fed cut rates near zero while bitcoin remained around $5,400

At 5:00 p.m. EDT on March 15, 2020, the Federal Reserve lowered its target range for the federal funds rate to 0%–0.25% and directed the purchase of at least $500 billion in Treasury securities and $200 billion in agency mortgage-backed securities over the coming months. The unscheduled intervention changed the monetary backdrop confronting bitcoin only days after a severe, market-wide rush for liquidity.

The policy announcement did not produce an immediately measurable bitcoin breakout. CoinMarketCap’s March 15 end-of-day snapshot placed bitcoin at $5,392.31, up 3.32% over 24 hours but down 33.99% over seven days. Bitcoin’s estimated market capitalization was $98.53 billion. Ether was $125.21, up 1.25% over 24 hours and down 39.70% over seven days.

Those observations establish market position, not causation. CoinMarketCap records its daily close at 23:59 UTC, about three hours after the Fed’s 21:00 UTC release. Its 24-hour and seven-day comparisons therefore began well before the policy announcement, and its price represented an aggregation across selected markets rather than an executable quote or official closing auction.

An emergency monetary reset

The March 15 action reduced the target range by 100 basis points from the range in effect entering the weekend. It was the Federal Reserve’s second unscheduled rate reduction during March 2020 and arrived before the meeting that had been scheduled for March 17–18.

The accompanying implementation instructions made the scale more concrete. Beginning March 16, the Federal Reserve Bank of New York’s trading desk was to conduct operations needed to maintain the new rate range, expand Treasury and mortgage-security holdings by at least $700 billion in total, and continue overnight and term repurchase operations to support dollar funding markets. The Board also reduced the primary credit rate by 1.5 percentage points to 0.25%, effective March 16.

The monetary-policy vote was 9–1. Cleveland Fed President Loretta Mester supported the other measures but preferred a federal-funds target range of 0.50%–0.75%. That dissent underscored how far the majority was prepared to move before conventional U.S. markets reopened.

Why bitcoin’s response mattered

Bitcoin’s fixed issuance schedule made central-bank balance-sheet expansion central to one influential case for the asset: unlike dollars, new bitcoin could not be created through a monetary-policy decision. March 15 supplied unusually vivid evidence for that contrast, but it did not validate the stronger claim that bitcoin was already functioning as a dependable crisis hedge.

The event-day data pointed to a more cautious conclusion. Bitcoin was modestly higher over CoinMarketCap’s trailing 24-hour window, yet it remained roughly one-third below its level seven days earlier. Ether and many other crypto assets had suffered similarly large weekly losses. During the initial pandemic liquidity shock, digital assets were trading inside the wider scramble for dollars rather than remaining insulated from it.

The Fed’s intervention still mattered for crypto because it altered interest rates, dollar liquidity and the prospective supply of central-bank reserves—the macro variables against which bitcoin’s scarcity argument was commonly evaluated. It also created a testable divide between narrative and observation: monetary expansion could strengthen a long-term thesis without generating an immediate price response.

What was knowable on March 15

The verified record supports three narrow conclusions. The Fed moved its policy rate close to zero; it committed to at least $700 billion of Treasury and agency-mortgage purchases; and bitcoin ended CoinMarketCap’s UTC measurement day near $5,400 after an exceptionally damaging week.

It does not show that the Fed caused bitcoin’s 24-hour gain, that the March sell-off had ended, or that future monetary expansion would raise cryptocurrency prices. Those questions required later market observations that were unavailable on March 15 and should not be inserted into the event-day record.