Positions force-closed in this coin over the last 24 hours, split by side. A long liquidation is forced selling; a short liquidation is forced buying.

A liquidation is a trader being forced out of a bet because the price moved too far against them. Longs being liquidated means forced selling; shorts being liquidated means forced buying. Judge the size against what is normal for this coin: $5M is enormous for a small coin and barely noticeable for Bitcoin.

Liquidation-cascade fades are built on this: forced selling overshoots, so the sharpest bounces tend to follow the biggest one-sided prints. Long and short squeeze plays work the same mechanism in reverse, and stop-hunt reversals look for price being pushed into a cluster of stops precisely to trigger them.

Design a new strategy for RAY that trades around forced liquidations, using /api/v1/market-intelligence/liquidations?symbol=RAY live. Define what counts as a cascade, which side you take, how quickly you exit, and how you avoid being liquidated yourself. Validate on the per-event tape at /api/v1/backtesting/hl-liquidations plus /api/v1/backtesting/klines, and report the worst single loss, not just the average.

/backtesting/liquidations gives the aggregated series, and /backtesting/hl-liquidations gives the exact per-event Hyperliquid tape — every individual fill, with its venue. For the price levels where liquidations cluster, use /backtesting/snapshots?data_type=liquidation_map.

Using CryptoDataAPI, backtest the liquidation-cascade fade on RAY. Pull the per-event tape from /api/v1/backtesting/hl-liquidations and price bars from /api/v1/backtesting/klines. Define a cascade as a 5-minute bucket in the top 1% of one-sided liquidation size, then measure forward returns at 15m, 1h and 4h from taking the opposite side. Charge taker fees and report the hit rate and worst loss.

Net movement of this coin on and off centralised exchanges, across every chain we index. Coins moving ONTO an exchange are being positioned to sell; coins moving OFF are going to self-custody or staking.

Coins moving ONTO an exchange usually means someone is getting ready to sell them. Coins moving OFF usually means they are being held for longer. One large move in a single hour is often just one person shuffling funds; the same direction repeating over days is the signal worth acting on.

Exchange netflow is a well-known on-chain indicator: sustained outflows shrink the supply available to sell and tend to precede strength, while sustained inflows do the opposite. Reserve depletion strategies take positions when exchange balances fall to multi-year lows. It is a slow signal — better for framing a position over weeks than for timing an entry.

Design a new swing strategy for RAY driven by exchange flows from /api/v1/on-chain/exchange-flows/RAY. This is a slow signal, so define a holding period in days or weeks and say what invalidates the trade rather than using a tight stop. Validate against the exchange_flows block of /api/v1/backtesting/daily-snapshots/{date} plus daily bars from /api/v1/backtesting/klines, and report whether the signal survives transaction costs.

Exchange flows are archived per chain in the exchange_flows block of /backtesting/daily-snapshots/{date}. It is a daily series rather than intraday, which suits the signal — netflow is a multi-day read, not an entry trigger.

Using CryptoDataAPI, test exchange netflow as a signal for RAY. Pull the exchange_flows block from /api/v1/backtesting/daily-snapshots/{date} across the archive and daily price bars from /api/v1/backtesting/klines. Compare forward 7d and 30d returns after sustained net outflows versus sustained net inflows. Report whether the difference is large enough to trade after costs.