Methodology

How the Unstable Index is built, what it measures, and where it falls short.

This USDUS page displays the public Unstable Index dataset. Its methodology is reproduced below; the source calculates the daily readings.

What the index is

The Unstable Index is a single 0-100 reading of structural fragility in the stablecoin and crypto-collateral system. Higher means more fragile: more leverage, thinner pegs, more crowded positioning, more macro pressure. It is assembled from eight sub-indices, each built from public market and on-chain data.

What it is not. The index does not forecast the price of Bitcoin or any other asset, and it is not a trading signal. A high reading says the system is fragile, not that a crash is scheduled. Fragile systems can stay fragile for months. Nothing here is investment advice.

Leading vs. coincident

The eight sub-indices are split into two groups, and this split is the core of the design:

They are reported separately as Fragility (leading only) and Stress (coincident only), alongside the combined Overall score. A leading indicator that is still screaming on the day of the crash is not leading, so we hold those components to that standard: several of them are designed to fall as an event turns coincident.

Inputs

The eight sub-indices, their weight in the Overall score, and what feeds them.
Sub-indexTypeWeightWhat it measuresPrimary sourcesRefresh
Peg DispersionCOINCIDENT20%Supply-weighted deviation of tracked stablecoins from $1.00, supply contraction, pool imbalanceDeFiLlama, on-chain pool state, exchange spotHourly
Leverage & FundingLEADING20%Perpetual funding rates, open-interest velocity, and a "compressed spring" term: leverage building while volatility stays suppressedBinance, Bybit, Hyperliquid, DeribitHourly
Liquidation ProximityCOINCIDENT15%Positioning extremes - how crowded long or short the market is relative to a neutral baseExchange long/short account ratiosHourly
VolatilityCOINCIDENT15%DVOL level, implied-vol term structure (backwardation = acute stress), put/call ratioDeribit optionsHourly
SecurityCOINCIDENT10%Rolling 30-day USD value lost to exploits, on a logarithmic scale so a single large hack does not pin the reading at the maximumPublic incident feedsDaily
On-chain FlowsLEADING8%Aggregate USD-stablecoin net outflows and supply contraction - redemptions drain the system before prices moveDeFiLlama, chain dataDaily
NarrativeCOINCIDENT7%News severity composite: exchange halts, exploits, macro dramaCurated RSS feedsHourly
TradFi SpilloverLEADING5%MOVE index, VIX and VIX/VIX3M backwardation, 20-day dollar rate-of-change, high-yield credit spreadsYahoo Finance, FRED (St. Louis Fed)Daily

The Overall score is the weighted sum above, multiplied by a contagion amplifier that raises it when several sub-indices are stressed at the same time - a crisis in one corner is less dangerous than the same readings everywhere at once.

What stays in-house

The weights, inputs, sources and their direction are all published here - enough to judge whether the construction is sound or to argue with it. What stays in-house is the calibration inside each sub-index: the curves that turn a funding rate or a peg deviation into a 0-100 reading, and the asset-level model behind Peg Dispersion. That is the part that took the work.

Update frequency

Missing-data policy

This is where most composite indices quietly lie. If a feed goes down and the scorer defaults to zero, the index reads calm precisely when it has gone blind.

Rule: missing data must never read as "safe". Every component falls back to a neutral-to-slightly-elevated value, never to zero.

Robustness

Historical backtest on real data

In October 2026 the current construction was run day by day over real public data from April 2021 to today: Binance funding, Bybit open interest and long/short ratios, Deribit DVOL, DeFiLlama supply, prices and exploit losses, FRED VIX, dollar index and high-yield spreads. The news signal, the implied-vol term structure, the put/call ratio and the MOVE index have no public archive and sit at their neutral fallbacks, so every reading below is a lower bound on what the live index would have shown.

LevelRangeShare of days 2021-2026
LOW0-2479%
MODERATE25-3717%
ELEVATED38-493.3%
HIGH50-1000.4%
EventT−7T−1TT+1T+3Highest in the 30 days before
May 2021 deleveraging (19 May)303246413541, ELEVATED from T−8
Terra / UST (9 May 2022)212332536029
FTX (8 Nov 2022)302117392049, ELEVATED from T−28
SVB / USDC (10 Mar 2023)181615162221
Aug 2024 carry unwind (5 Aug)182219211825
Oct 2025 liquidation day (10 Oct)201514211821

Readings are the 08:00 UTC snapshot, so an event that hits later in the day shows up at T+1. Two honest misses: the SVB weekend stays LOW on on-chain data alone (daily prices understate an intraday depeg, and the replay has no news feed and no Curve pool data, both of which the live index sees), and the October 2025 liquidation day had no leverage build-up signature in these inputs at all. Beyond the named events, the ELEVATED days cluster in the leverage build-ups before the September 2021, December 2021 and March 2024 drawdowns. Across all days, a reading at MODERATE or above was followed by a 10%+ BTC drawdown within a week about twice as often as a LOW reading (26% vs 13%). ELEVATED and HIGH do not separate further on that metric, and BTC implied volatility alone (DVOL) is a stronger drawdown predictor than the composite. The index is a fragility gauge, not a forecast.

Regression suite

Every calibration change runs against a suite before it ships. Since v3.0 the suite re-scores the real daily inputs around the six events above and four calm stretches with the current scorers, and asserts both directions: the index elevates on the events, the leading signals load before them, and the calm stretches stay LOW on median and never reach ELEVATED. Earlier versions used hand-written "event-typical" input ranges; the real-data run showed those were never observed together on any single day, which is why the suite was rebuilt on real inputs. A calibration change that breaks any of these does not get deployed.

Self-backtest

The backtest measures depegs as a discount against each asset's own recent median, not against a flat $1.00 - an asset that trades at $0.998 all year is not depegging every day, and scoring it that way would manufacture flattering hit rates. Over the most recent 99-day window that yields three genuine depeg events. The index caught the systemically relevant one at a maximum score. The two misses were micro-cap assets too small to move the composite.

Known limitations

We would rather state these than have them found for us.

Changelog

Construction changes are listed here, so a move in the score can be told apart from a change in how it is measured.

Questions and corrections

If something here looks wrong, we would rather hear it. Reach us at @usdus_official. Methodology version v3.0. This page is updated when the construction changes, not when the score does.