SOLUSDT · historical base rate

OI accelerating into liquidations on SOLUSDT

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

What has happened on SOLUSDT when it held

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

Outcome distribution

WHAT FOLLOWED · ALL 71 MATCHES

68 of 71 (95.8%) 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. 71 of the matches have a complete 1 hour forward.

What are MFE and MAE?

Why 72 hours can show fewer than 1 hour: a match too recent for a complete 72 hours 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 71 matches
704MATCHES PER UTC DAY · MAX 7 ON 2026-08-21427761426412213141122321208-2408-3109-0709-142026-08-19 TO 2026-09-18 · 31 UTC DAYS · ZERO DAYS KEEP THEIR SLOT

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

Where the next 30 minutes landed - 71 measured, 0 too recent
≥ +0: 31 OF 711810863455975≤−100−2−1−0.5−0.2−0.1<00++0.1+0.2+0.5+1+2≥+400

Forward 30-minute returns across 71 matches: close to an even split, which is what a coin flip looks like.

How to read a distribution
Upside reached · 24hUpside reached (MFE, 24h)The most price moved up within 24h of each occurrence: a high-water mark, never a close. 69 with a complete 24h.
Drawdown · 24hDrawdown (MAE, 24h)The worst price moved against within 24h of each occurrence: the deepest point, never the close. 69 with a complete 24h.

Versus baseline

Historically, when any eligible SOLUSDT minute in the window (baseline) held (42,585 occurrences in the scanned window, 41,156 with a computable 24h horizon), the market reached +5% within 24h in 11,844 of 41,156 (28.8) and drew down 10%+ in 84 of 41,156 (0.2). Maximum favorable (MFE) and maximum adverse (MAE) excursions, both computed forward.

The full record

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

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

WHAT FOLLOWED · ALL 71 MATCHES

68 of 71 (95.8%) 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. 71 of the matches have a complete 1 hour forward.

What are MFE and MAE?

Why 72 hours can show fewer than 1 hour: a match too recent for a complete 72 hours 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 71 matches
704MATCHES PER UTC DAY · MAX 7 ON 2026-08-21427761426412213141122321208-2408-3109-0709-142026-08-19 TO 2026-09-18 · 31 UTC DAYS · ZERO DAYS KEEP THEIR SLOT

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

Where the next 30 minutes landed - 71 measured, 0 too recent
≥ +0: 31 OF 711810863455975≤−100−2−1−0.5−0.2−0.1<00++0.1+0.2+0.5+1+2≥+400

Forward 30-minute returns across 71 matches: close to an even split, which is what a coin flip looks like.

How to read a distribution
Check our work: the key that re-runs this exact count (q#a3ec44e4)
grammar
research_query.v2
normalization
archive_normalization.v1
feature library
feature_defs.v1
dataset revision
8904ef0442c6f623ec772df2b59d7baf1e49aaa808b5b11ac31546605549e3bb
query hash
a3ec44e40d5c3eba2d4eacf1d88cd503dead0a3765f8773281630c5bdb169e18
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",
        "solusdt"
      ],
      [
        "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","solusdt"],["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 SOLUSDT right now: the SOLUSDT research page