Liquidity Risk
Pronunciation: lih-KWID-ih-tee RISK
Definition
Liquidity risk includes market liquidity and funding liquidity.
Overview
How it works and why it matters
Liquidity risk is the possibility that an entity cannot meet obligations on time or must accept substantial losses to obtain required spendable assets. Crypto adds network-specific inventory, market depth, bridge delays, redemption terms and fee-asset requirements.
Important technical and operational details
Market liquidity concerns executing transactions near expected value, while funding liquidity concerns obtaining usable cash or assets in time to meet withdrawals, settlement, collateral, and operating obligations.
Depth can disappear during stress, and displayed volume may not represent executable capacity. Fragmented venues, depegs, network congestion, withdrawal limits, concentrated providers, or correlated sellers can widen spreads and delay conversion.
Organizations should map cash and asset flows, measure stressed exit capacity, diversify venues and funding, maintain buffers, set limits, and test withdrawals. Scenario analysis must include simultaneous outflows, provider failure, price gaps, and impaired collateral. Liquidity metrics should use executable size and timing rather than headline market volume.
Liquidity risk is the possibility that assets cannot be sold, converted, withdrawn, or obtained quickly enough without unacceptable loss or disruption. Liquidity is the ability to act at the required size and time, not merely the existence of a quoted market price.
Practical decision points
Liquidity risk should be tested under stress, not just measured as a current ratio. Assume a sudden burst of merchant withdrawals, a stablecoin redemption pause, a bridging delay and expensive network fees. Assess whether obligations remain payable within agreed timing under each scenario. Hold buffers in the correct settlement assets and rails, and account for assets that could be sold only with significant price impact. Separate available liquidity from collateral, reserves and customer assets that cannot lawfully be used for general obligations. A dashboard showing high total assets can disguise an imminent payment bottleneck.
Related concepts
Further reading
Example
A provider owes merchants USDC on Polygon today but holds most reserves in another network's token. Even if total holdings exceed the payouts, transfers can fail without a viable route, adequate fees and sufficient bridge capacity.
Comparison
Solvency and liquidity are not the same. A solvent balance sheet can coexist with near-term payment failure when assets are locked, illiquid or on the wrong rail.
Key Takeaway
Solvency on paper does not ensure the right assets are spendable when needed.
Sources
- NIST Documentation: Cyberframework — NIST (2026-07-30)
- FATF Documentation: Virtual Assets — FATF (2026-07-30)