Scenario Analysis for Crypto Assets

Build scenarios around transmission paths

A crypto stress scenario is more useful when it describes a path from an event to an exposure, rather than assigning a dramatic price target. Start by naming the asset or position, the market used to value it, and the assumptions about liquidity, access, and time. Token prices, protocol function, and a centralized venue’s ability to process withdrawals are separate parts of the analysis.

These are conditional exercises, not predictions. Wider spreads, delayed transfers, or reduced access may accompany a repricing, depending on the asset, venue, network, and event. State each assumption; do not treat one past episode as a template.

Trace drawdowns through liquidity and collateral

Model a price decline alongside exit conditions. A quoted mark may not be available for a large order when depth shifts or trading is concentrated. Use ranges for execution discounts and exit time, not screen price alone.

On leverage, a decline interacts with platform-specific collateral, maintenance, and liquidation rules; execution may differ from a chosen stop. Name the contract, margin asset, platform terms, and possible gaps.

• Price shock and duration, with the reference market identified
• Spread or depth deterioration and assumed exit size
• Collateral value, margin rule, and liquidation process if applicable
• Network congestion or withdrawal delays as separate assumptions

Separate stablecoin pressure from redemption access

Stablecoin designs differ in backing, redemption access, disclosures, and transfer mechanics. Distinguish a secondary-market price deviation from any direct redemption route, whose terms and holder eligibility depend on the product.

A stablecoin shock may affect collateral and trading pairs, depending on the venue and protocol. Do not assume immediate liquidation at a quoted value or direct redemption for every holder; mark timing and counterparties as uncertain.

Map failures by layer, not by headline

Exchange interruption, custody failure, and protocol exploit create different exposures. A centralized venue manages customer accounts under its terms; self-custody depends on keys and network access. An application contract issue does not establish chain failure.

Identify affected assets, decision authority, and any documented recovery path. A pause or governance response is system-specific. Include connected lending or bridging only when the dependency is established.

Add a macro shock without claiming a single cause

Rates, currency conditions, or risk appetite may coincide with crypto moves; correlation varies by asset and period, and does not establish cause. Describe the shock and keep venue access and network performance as separate assumptions.

Use scenario results to identify fragile assumptions, such as one venue remaining open or collateral retaining a stable value. Record the data limits and revisit the case when exposure or market structure changes. This is educational information, not individualized investment, tax, legal, or accounting advice.