Babel Finance Freezes Withdrawals as Crypto Credit Stress Spreads

Babel Finance suspended redemptions and withdrawals from its products on June 17, 2022, saying it was experiencing “unusual liquidity pressures” amid sharp cryptocurrency-market fluctuations and what it called risk events at other institutions.

The company characterized the interruption as temporary and said normal service would be announced separately. It did not provide a reopening date, quantify the assets affected or identify the counterparties with which it said it was communicating. The verified development was therefore a withdrawal freeze attributed to liquidity pressure—not a declared insolvency, bankruptcy filing or confirmed customer loss.

An institutional lender under pressure

The announcement mattered because Babel presented itself as a wholesale crypto-finance business serving institutions and wealthy accredited clients rather than a mass-market exchange. In a company-supplied financing announcement dated May 25, 2022, Babel said it served about 500 customers and limited its business to bitcoin, ether and stablecoins.

That May announcement said Babel had raised $80 million at a $2 billion valuation. It also reported an outstanding loan balance exceeding $3 billion at the end of 2021, average monthly derivatives trading volume of $800 million and more than $20 billion of structured and traded options products. Those figures describe different measurements and periods; they should not be added together or treated as a June 17 balance sheet. They were promotional, company-reported figures, not independently audited liquidity disclosures.

The contrast was nevertheless striking. A business that had announced a large financing round approximately three weeks earlier was now preventing clients from redeeming assets. The sequence illustrated that an equity valuation or recently completed capital raise did not establish that a crypto lender held enough immediately available assets to meet withdrawals under stressed conditions.

What the freeze signaled—and what it did not prove

Babel’s action followed Celsius Network’s June 12 suspension of withdrawals, swaps and transfers. By June 17, two centralized crypto-credit platforms had publicly restricted customer access within the same week. That made liquidity management and counterparty exposure central industry questions, even though the available records did not establish that the two companies had the same underlying problem.

Crypto lenders could transform client deposits into loans, trading positions or other less-liquid exposures. When customers sought assets back rapidly, a mismatch between obligations and available collateral could become visible. That is an interpretation of the business-model risk, not a finding about Babel’s internal books. Babel released no contemporaneous balance sheet, reserve attestation, maturity schedule or detailed exposure report with the notice.

The macroeconomic backdrop was also tightening. On June 15, 2022, the Federal Open Market Committee raised its federal-funds target range to 1.5%–1.75% and continued reducing Federal Reserve securities holdings. That decision supplied relevant risk-asset context, but the public evidence available on June 17 did not demonstrate that monetary policy directly caused Babel’s suspension.

The event-day record remains narrow

The strongest conclusion supported on June 17 was that Babel had stopped redemptions and withdrawals because it said it faced unusual liquidity pressure. The notice did not disclose the amount clients had requested, the value or liquidity of available collateral, the identity of affected customers, or whether every product and jurisdiction was operationally covered in the same way.

No cryptocurrency price or daily percentage move is used here. Digital assets traded continuously across venues, and a precise market claim would require a named instrument, venue, quote currency and cutoff convention. The institutional significance instead came from the operational restriction itself: customers could not access assets through the affected Babel products, while the company had not supplied a timetable or the financial detail needed to judge the duration or severity of the problem.