ETHUSDT · historical base rate

OI accelerating into liquidations on ETHUSDT

Open-interest velocity above its own 90th percentile while at least $1M of liquidation notional printed in the trailing hour.

What has happened on ETHUSDT when it held

Historically, when OI accelerating into liquidations on ETHUSDT held (184 occurrences in the scanned window, 177 with a computable 24h horizon), the market reached +5% within 24h in 43 of 177 (24.3) and drew down 10%+ in 0 of 177 (0.0). Maximum favorable (MFE) and maximum adverse (MAE) excursions, both computed forward.

Outcome distribution

WHAT FOLLOWED · ALL 184 MATCHES

161 of 184 (87.5%) reached +0% or more within 1 hour · smallest move size with matches, picked for you

Pick a window and a move size: how often did a move at least that big follow?

WINDOWMOVE SIZE

🔒 Measured after every match, never by keeping winners. 184 of the matches have a complete 1 hour forward.

What are MFE and MAE?

Why 7 days can show fewer than 1 hour: a match too recent for a complete 7 days is left out of that count entirely, even if it already reached the level within 1 hour. The two counts cover different sets of matches.

When they happened - one bar per UTC day, all 184 matches

About 5.9 a day, on 28 of 31 days: spread through the record rather than one event.

Where the next 30 minutes landed - 184 measured, 0 too recent

Forward 30-minute returns across 184 matches: 56% of them finished up.

How to read a distribution

Upside reached · 24hThe most price moved up within 24h of each occurrence: a high-water mark, never a close. 177 with a complete 24h.

Drawdown · 24hThe worst price moved against within 24h of each occurrence: the deepest point, never the close. 177 with a complete 24h.

Versus baseline

Historically, when any eligible ETHUSDT minute in the window (baseline) held (41,742 occurrences in the scanned window, 40,346 with a computable 24h horizon), the market reached +5% within 24h in 6,366 of 40,346 (15.8) and drew down 10%+ in 0 of 40,346 (0.0). Maximum favorable (MFE) and maximum adverse (MAE) excursions, both computed forward.

The full record

The same setup counted over every recorded day on ETHUSDT (2026-08-19 to 2026-09-18), growing daily.

Historically, when OI accelerating into liquidations on ETHUSDT over the full record held (184 occurrences in the scanned window, 177 with a computable 24h horizon), the market reached +5% within 24h in 43 of 177 (24.3) and drew down 10%+ in 0 of 177 (0.0). Maximum favorable (MFE) and maximum adverse (MAE) excursions, both computed forward.

WHAT FOLLOWED · ALL 184 MATCHES

161 of 184 (87.5%) reached +0% or more within 1 hour · smallest move size with matches, picked for you

Pick a window and a move size: how often did a move at least that big follow?

WINDOWMOVE SIZE

🔒 Measured after every match, never by keeping winners. 184 of the matches have a complete 1 hour forward.

What are MFE and MAE?

When they happened - one bar per UTC day, all 184 matches

About 5.9 a day, on 28 of 31 days: spread through the record rather than one event.

Where the next 30 minutes landed - 184 measured, 0 too recent

Forward 30-minute returns across 184 matches: 56% of them finished up.

How to read a distribution

Check our work: the key that re-runs this exact count (q#eb0132dc)

grammar: research_query.v2
normalization: archive_normalization.v1
feature library: feature_defs.v1
dataset revision: 8904ef0442c6f623ec772df2b59d7baf1e49aaa808b5b11ac31546605549e3bb
query hash: eb0132dc284ca62dbac3134e7afbe5c454825cd8e8658726a629181be04e9766
scanned window: 2026-08-19T00:00:00.000Z to 2026-09-18T00:00:00.000Z (UTC)

Same key, same bytes. This receipt reruns; it does not retell. When the record grows, the dataset revision changes and says so.

Re-run this yourself, over the API or from an AI agent

This is the exact search definition behind the receipt. Send it to the key-authed research API (or the MCP research tool) and compare the bytes: a cached rerun is free.

{
  "schema_version": "research_query.v2",
  "normalization_version": "archive_normalization.v1",
  "feature_version": "feature_defs.v1",
  "target": "record_occurrences",
  "where": {
    "all": [
      [
        "feature.oi_velocity_pctrank",
        "gte",
        0.9
      ],
      [
        "feature.liq_notional_usd_1h",
        "gte",
        1000000
      ],
      [
        "identity.symbol",
        "eq",
        "ethusdt"
      ],
      [
        "times.anchor_time",
        "between",
        [
          "2026-08-19T00:00:00.000Z",
          "2026-09-18T00:00:00.000Z"
        ]
      ]
    ]
  },
  "sort": [
    "times.anchor_time",
    "desc"
  ],
  "page": {
    "limit": 50,
    "cursor": null
  }
}

curl -s https://app.edgedepth.com/api/v1/research/query \
  -H 'authorization: Bearer $EDGEDEPTH_API_KEY' \
  -H 'content-type: application/json' \
  -d '{"schema_version":"research_query.v2","normalization_version":"archive_normalization.v1","feature_version":"feature_defs.v1","target":"record_occurrences","where":{"all":[["feature.oi_velocity_pctrank","gte",0.9],["feature.liq_notional_usd_1h","gte",1000000],["identity.symbol","eq","ethusdt"],["times.anchor_time","between",["2026-08-19T00:00:00.000Z","2026-09-18T00:00:00.000Z"]]]},"sort":["times.anchor_time","desc"],"page":{"limit":50,"cursor":null}}'

How to read this

Counts ship with denominators: occurrences across the eligible symbol-buckets scanned. A rate is over the occurrences with a computable horizon (present), never the total.
Absent is absent. When a feature was not warm at a minute, that bucket leaves the denominator and is reported; it is never coerced to zero.
This selects a setup, never its outcome. The grammar forbids filtering on what followed (OUTCOME_IN_PREDICATE), so the distribution below is over every occurrence, not a survivorship-picked subset.

Occurrences are observed examples in a selected archive, not a guarantee. Outcomes are computed forward from each anchor and are descriptive, never a filter and never a prediction. Nothing here is trading advice.

Everything measured on ETHUSDT right now: the ETHUSDT research page