Crypto Volatility Cycles
Crypto volatility clusters: quiet periods often give way to expansion, and high-volatility episodes can persist before normalising. Understanding the regim
Reading progress — saved on this device
Learning objectives
- Distinguish realised, implied and intraday volatility.
- Explain volatility clustering and why simple mean-reversion assumptions can fail.
- Adapt sizing and execution to changing volatility regimes.
What it is
Realised volatility measures variability in observed returns. Implied volatility is backed out from option prices and reflects the market price of future uncertainty under option-pricing assumptions.
Crypto trades continuously, so annualisation conventions often use 365 days for daily returns. Consistency matters more than the convention itself when comparing series.
Volatility is regime-dependent. Calm periods can persist, but shocks, liquidations and event risk can produce abrupt expansion and positive feedback through leverage.
How it works
Volatility clustering means large moves tend to be followed by more large moves and small moves by more small moves. This violates the intuition that each day's volatility is independent.
Leverage can amplify volatility: falling prices trigger liquidations, forced orders move the market further, and option hedging can add flows around large moves.
Implied volatility can trade above realised volatility because option sellers demand compensation for jump and tail risk. The spread is not free carry; short-volatility positions can experience convex losses.
Position sizing should generally contract when expected or realised volatility rises if the trader wants a stable risk budget.
Analysis framework
| Check | Why it matters | What to verify |
|---|---|---|
| Realised volatility | Measures recent movement | Use a consistent return frequency and lookback. |
| Implied volatility | Prices future uncertainty | Compare option maturities and skew, not one headline IV. |
| Leverage | Can amplify expansion | Track open interest, funding and liquidation levels. |
| Sizing | Controls risk through regimes | Scale positions to volatility and liquidity rather than fixed notional. |
Cross-checks and limitations
Volatility regime detection should use more than one lookback. A short window reacts quickly but can overreact to one event; a long window is stable but slow. Comparing, for example, 7-day and 30-day realised volatility can reveal whether a new shock is lifting near-term movement above the background regime.
Liquidity and volatility are also endogenous. As order-book depth falls, the same order creates more price impact; larger moves then cause market makers to widen spreads further. This feedback means volatility targeting should be accompanied by liquidity limits rather than assuming price standard deviation captures all execution risk.
Worked example and thought exercise
A strategy normally trades £100,000 notional when daily volatility is 2%. If daily volatility doubles to 4%, keeping notional unchanged roughly doubles first-order price-risk exposure. A volatility-targeting approach might cut notional toward £50,000, all else equal.
If 30-day realised volatility is 45% annualised while one-month implied volatility is 70%, the option market is charging a large uncertainty premium—but the difference can be justified by event or jump risk.
Thought exercise: why can selling options after volatility has risen sharply still be dangerous even if you expect volatility eventually to fall?
Common mistakes and practical workflow
- Treating volatility as constant.
- Assuming low volatility means low downside risk.
- Annualising short samples mechanically without caveats.
- Selling implied volatility simply because it exceeds recent realised volatility.
Practical workflow
- Measure realised volatility across several horizons.
- Compare with implied volatility and event calendar where options exist.
- Review leverage/liquidation conditions.
- Adjust position size, stop distance and execution tactics to the regime.
- Stress jump scenarios that standard deviation does not capture.
Knowledge checkpoint
- What is the difference between realised and implied volatility?
- What does volatility clustering mean?
- Why can low realised volatility precede high risk?
- How should a stable risk budget respond when volatility doubles?
FAQs
❓ Does high volatility predict lower prices?
No. Volatility measures magnitude, not direction.
❓ Is implied volatility a forecast?
It embeds option prices and risk premia; it should not be read as a pure point forecast.
❓ Why use 365 in crypto annualisation?
Crypto trades every day, though the convention must be stated and used consistently.
❓ Can volatility remain high for weeks?
Yes. Clustering means elevated volatility can persist after shocks.
Summary
Volatility is a changing state variable, not a constant. Good cycle analysis separates realised from implied volatility, recognises clustering and leverage feedback, and adapts sizing and execution rather than extrapolating calm conditions.
Want this in a personalised order?
Take the crypto assessment and get a custom path of 10 modules matched to what you already know. Free, no card required.
Build my path →