Volatility Decay Overlay
Textbook volatility decay framework. Annualized 30-day realized volatility of Bitcoin daily returns, smoothed by a 365-day moving average, sliced by halving cycle and aligned by days-since-cycle-low. The multi-cycle overlay shows three successive cycles in superposition; the trend across cycles is the empirical signature of an asset whose realized volatility decays as its market capitalization matures.
What is it?
The Volatility Decay Overlay measures the annualized 30-day realized volatility of Bitcoin's daily log-returns, smoothed by a 365-day moving average. The smoothed volatility curve is then sliced by halving cycle and aligned by days-since-cycle-low - each cycle becomes its own segment, all anchored on the same horizontal origin. The multi-cycle overlay places three successive cycles in superposition on the chart so that the eye can compare the volatility trajectory at the same days-since-low across cycles. The structural reading is one of the most empirically robust observations about Bitcoin's maturation: realized volatility has historically decayed across successive halving cycles as market capitalization has grown.
How to read
The chart shows three overlaid line segments, each representing one halving cycle: cycle 4 (post-2022 low, primary line in the cycle accent color), cycle 3 (post-2018 low, terracotta), and cycle 2 (post-2015 low, teal). The horizontal axis is days-since-cycle-low (0 at the cycle low, increasing to the right); the vertical axis is the 365-day smoothed annualized realized volatility, expressed as a percentage. To read the chart: pick a horizontal position (a particular days-since-low value, e.g. day 365 = one year into the cycle) and compare the vertical heights of the three lines at that position. If the cycle-4 line sits structurally below the cycle-3 line at the same days-since-low, this is the decay reading visible at that cycle phase. The two reference zones - green low-vol regime (0-80%) and amber high-vol regime (120-250%) - provide cycle-independent reference levels for absolute volatility magnitude.
Key zones
Two cycle-independent reference zones for absolute volatility magnitude: • Low realized-vol regime (0-80%): historically associated with mature accumulation phases and late-cycle compression. Cycle 4 has spent more time in this band at any given days-since-low than cycles 2 and 3 - the empirical heart of the volatility decay observation. • High realized-vol regime (120-250%): historically associated with parabolic late-cycle expansion phases and capitulation events. The peak height of each cycle's curve in this band is a measure of that cycle's volatility intensity. The decay observation reads structurally: across cycles 2 → 3 → 4, the average curve height at any fixed days-since-low has historically declined. The chart is designed to make this decay visible at a glance - no quantitative threshold is needed to read it; the visual stacking of curves carries the structural reading.
What to observe
• Vertical stacking order at fixed days-since-low: at any horizontal position, the structural decay reading is that cycle 4 sits below cycle 3 sits below cycle 2 in vertical volatility height. Departures from this ordering at a particular cycle phase indicate atypical behavior worth investigating. • Peak volatility height per cycle: each cycle's line traces a peak at a particular days-since-low. Comparing the peak heights across cycles is a structural reading of the absolute volatility intensity contracted by Bitcoin across each successive halving expansion. • Time-to-peak per cycle: each cycle reaches its peak volatility at a different days-since-low. Comparing the time-to-peak across cycles is an observation of how each cycle has phased its volatility realization differently. • Convergence at low-vol regime: as cycles progress, the curves have historically converged toward the low-vol regime band at long days-since-low values. The compression of inter-cycle spread at long horizons is a structural reading of asset maturation. • Cycle 4 in-progress reading: cycle 4 may not yet have reached its full days-since-low extent - its line terminates at the present day's offset. The remaining horizontal extent will be filled in over time as the cycle matures. • Anchor robustness: the chart anchors on the cycle low (the lowest BTC daily close after each major bull peak) rather than on the halving date. This convention places the volatility expansion phase (post-low recovery) on the horizontal axis in a directly comparable way across cycles.
Historical context
The volatility decay framework is an empirical observation that has been consistently documented across the Bitcoin halving cycles since 2013. Cycle 1 (2009-2012, pre-halving microstructure era) is omitted from the overlay because pre-2013 daily volatility computation is dominated by sparse-trading noise that contaminates the structural decay reading. Cycles 2 (2015-2018), 3 (2018-2022), and 4 (2022-present) each provide enough daily-return density for the 30-day realized volatility computation to be reliable, and the SMA-365 smoothing absorbs short-term noise while preserving the structural decay reading. The decay observation is not specific to Bitcoin: the same pattern has been observed across multiple asset classes as their market capitalization has grown, and is a textbook reading of asset maturation. The chart is designed to expose the Bitcoin-specific instance of this universal pattern at a glance.
Expert notes
Implementation: the backend computes the annualized 30-day realized volatility from log-returns of the BTC daily close (sigma_30d × sqrt(365) × 100), then applies a 365-day SMA smoother. The smoothed series is then sliced by cycle using the documented cycle-low dates from CYCLE_BOTTOMS in halvings.py and broadcast back to the daily index for each cycle independently. The three cycle segments (cycles 2, 3, 4) are exposed via three separate compute functions (compute, compute2, compute3) so that each cycle becomes its own value-channel in the API response. The renderer aligns the three channels on the same horizontal cycle-relative axis. The choice of 30-day window for volatility and 365-day window for smoothing is a long-standing convention that balances responsiveness (30 days captures regime shifts within a quarter) and noise rejection (365 days absorbs short-term spikes that would otherwise dominate the structural reading). The chart does not display absolute calendar dates on the horizontal axis - it displays days-since-cycle-low - because the alignment-by-cycle is the entire purpose of the multi-cycle overlay.
Common mistakes to avoid
• Reading the volatility magnitude as a directional indicator: realized volatility is direction-agnostic - it measures the magnitude of returns, not their sign. A high volatility reading does not mean price will go up or price will go down; it means the magnitude of daily returns has been large. • Treating cycle 4 as still cycle 4 indefinitely: cycle 4 will eventually transition to cycle 5 (post-2026 low, when documented). Until then, the cycle 4 line on the chart terminates at the present day's days-since-low offset. • Comparing absolute volatility values across very different days-since-low positions: the chart is designed for vertical comparison at the same horizontal position. Comparing cycle 4 at day 100 to cycle 3 at day 1000 is not a structural reading; both points must be at the same days-since-low for the comparison to carry the decay observation. • Assuming the decay continues monotonically forever: the volatility decay observation is empirical, not a law. Future cycles may produce volatility regimes that depart from the decay trajectory if macro conditions or market microstructure shift materially. • Mistaking the 30-day window for a forecast horizon: the 30-day window is a backward-looking measurement window for realized volatility, not a forward-looking prediction horizon. The chart describes what has happened, not what will happen.
Programmatic access
REST API
curl -sS \
'https://api.trinityinsights.io/api/v1/cycle-intelligence/cycle-volatility-decay-overlay/history?days=90' \
-H 'X-API-Key: $TRINITY_API_KEY'MCP server
{
"tool": "get_chart_value",
"metric_id": "cycle-volatility-decay-overlay",
"timeframe": "1y"
}Required tier: pro. See the pricing grid for the tier list and the MCP documentation for multi-client configuration.
Related metrics
Institutional disclaimer
Trinity Insights is an educational and analytical tool. The metric above does not constitute investment advice. Trinity Insights is not a Crypto-Asset Service Provider (CASP) registered under MiCA Regulation (EU) 2023/1114. See the full disclaimer.