Condition · recorded history

Liquidations arriving in cascades

The cascade clustering index is above 0.6: liquidations are arriving in bursts rather than independently.

What is a liquidation?

Recorded window: 5 Oct 2026 to 3 Nov 2026 (UTC). Counted 4 Nov 2026 at 08:13 UTC.

Read it in context

  1. On one market

    Each market page compares that market with its own minutes, not with every market at once.

  2. Test it, then plan it

    Narrow it to your markets and dates in the Workbench. A tested result leads to Plan a trade, which measures what trading it would have paid after costs.

By market

Results vary by market. Compare a market before drawing a conclusion.

How results varied by market

Range across 3 markets with at least 30 measured: reached +5% within 24 hours in 0 of 43 on BTCUSDT (0%) to 28 of 32 on QUSDT (88%).

Every market pooled, without context

What happened in the next 24 hours?

Both moves were more common than on minutes without it.

Other minutes are the same markets and dates without this condition. Each percentage is the share of measured minutes that reached that move from the starting price.

Price touched +5% or higher

When this held
44.4% · 405 of 912 minutes
Other minutes
23.4% · 2,579,968 of 11,015,494 minutes

Price touched −10% or lower

When this held
27.9% · 254 of 912 minutes
Other minutes
8.9% · 980,578 of 11,015,494 minutes

Price can touch both levels within the same 24 hours.

Every matching minute counts, so one long run adds many near-identical minutes. Busy markets weigh most.

Every condition is measured over the same 24 hours, whatever the length of its own reading. Other windows and move sizes shows shorter and longer windows.

This counts how often price touched a level, not what trading it would have paid.

Sample and counting

Rates use the 912 of 954 matches, pooled across 523 markets, with a full 24 hours after them. The 42 newer ones are left out, not counted as zero.

When it happened
Matches per UTC day, 2026-10-05 to 2026-11-04

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

Other windows and move sizes
Matches that reached each move within each window. Counts first; the measured row is what each rate is over.
Move1 hour4 hours24 hours72 hours7 days
Measured920920912864715
Too recent34344290239
+0.1% or more847 (92.1%)869 (94.5%)880 (96.5%)839 (97.1%)701 (98.0%)
+0.2% or more797 (86.6%)839 (91.2%)867 (95.1%)832 (96.3%)696 (97.3%)
+0.5% or more667 (72.5%)754 (82.0%)816 (89.5%)793 (91.8%)673 (94.1%)
+1% or more518 (56.3%)645 (70.1%)762 (83.6%)752 (87.0%)645 (90.2%)
+2% or more328 (35.7%)474 (51.5%)652 (71.5%)681 (78.8%)596 (83.4%)
+5% or more129 (14.0%)237 (25.8%)405 (44.4%)479 (55.4%)437 (61.1%)
+10% or more64 (7.0%)122 (13.3%)237 (26.0%)313 (36.2%)304 (42.5%)
+15% or more34 (3.7%)73 (7.9%)161 (17.7%)225 (26.0%)234 (32.7%)
+20% or more18 (2.0%)40 (4.3%)114 (12.5%)171 (19.8%)185 (25.9%)
+30% or more6 (0.7%)21 (2.3%)75 (8.2%)121 (14.0%)135 (18.9%)
+50% or more3 (0.3%)9 (1.0%)39 (4.3%)80 (9.3%)97 (13.6%)
+100% or more1 (0.1%)4 (0.4%)14 (1.5%)30 (3.5%)41 (5.7%)
+200% or more0 (0.0%)2 (0.2%)5 (0.5%)15 (1.7%)18 (2.5%)
+400% or more0 (0.0%)1 (0.1%)3 (0.3%)5 (0.6%)6 (0.8%)
−0.1% or lower859 (93.4%)882 (95.9%)894 (98.0%)853 (98.7%)711 (99.4%)
−0.2% or lower808 (87.8%)859 (93.4%)884 (96.9%)845 (97.8%)708 (99.0%)
−0.5% or lower681 (74.0%)783 (85.1%)853 (93.5%)832 (96.3%)707 (98.9%)
−1% or lower534 (58.0%)680 (73.9%)807 (88.5%)811 (93.9%)704 (98.5%)
−2% or lower343 (37.3%)491 (53.4%)696 (76.3%)753 (87.2%)687 (96.1%)
−5% or lower130 (14.1%)251 (27.3%)439 (48.1%)583 (67.5%)601 (84.1%)
−10% or lower51 (5.5%)119 (12.9%)254 (27.9%)370 (42.8%)443 (62.0%)
−15% or lower31 (3.4%)66 (7.2%)158 (17.3%)252 (29.2%)305 (42.7%)
−20% or lower18 (2.0%)43 (4.7%)106 (11.6%)177 (20.5%)220 (30.8%)
−30% or lower8 (0.9%)17 (1.8%)48 (5.3%)101 (11.7%)118 (16.5%)
−50% or lower1 (0.1%)6 (0.7%)14 (1.5%)31 (3.6%)52 (7.3%)

Each window counts only matches old enough for it, so a longer window can show fewer.

Distributions and daily counts
Upside reached · 24hUpside reached (MFE, 24h)The most price moved up within 24 hours of each match: a high-water mark, never a close. 912 with a complete 24 hours.
Drawdown · 24hDrawdown (MAE, 24h)The worst price moved against within 24 hours of each match: the deepest point, never the close. 912 with a complete 24 hours.
Price 30 minutes laterForward 30-minute returnForward 30-minute returns across 918 matches: close to an even split, which is what a coin flip looks like. 36 too recent.

How to read a distribution

Matches per UTC day

  • 5 Oct32 matches
  • 6 Oct24 matches
  • 7 Oct46 matches
  • 8 Oct75 matches
  • 9 Oct26 matches
  • 10 Oct23 matches
  • 11 Oct15 matches
  • 12 Oct38 matches
  • 13 Oct62 matches
  • 14 Oct25 matches
  • 15 Oct54 matches
  • 16 Oct24 matches
  • 17 Oct23 matches
  • 18 Oct27 matches
  • 19 Oct16 matches
  • 20 Oct18 matches
  • 21 Oct21 matches
  • 22 Oct20 matches
  • 23 Oct58 matches
  • 24 Oct35 matches
  • 25 Oct19 matches
  • 26 Oct24 matches
  • 27 Oct28 matches
  • 28 Oct15 matches
  • 29 Oct60 matches
  • 30 Oct62 matches
  • 31 Oct23 matches
  • 1 Nov18 matches
  • 2 Nov29 matches
  • 3 Nov14 matches
  • 4 Nov0 matches
How this is counted
  • Each rate counts only matches with the full window after them.
  • A minute where a reading was missing is left out and reported, not read as zero.
  • The condition picks the setup, never the outcome: a definition that filters on what followed is rejected (OUTCOME_IN_PREDICATE). Every match is measured, winners and losers alike.
  • "Other minutes" is every other eligible minute in the same markets and window. It is a reference, not a control group.
  • "Reached +5%" uses the highest price inside the window (maximum favourable excursion, MFE); "fell to −10%" uses the lowest (maximum adverse excursion, MAE). Neither is the close.
  • Checked 22,531,148 eligible market-minutes (eligible_symbol_buckets) on 523 markets, 2026-10-05 00:00 to 2026-11-04 00:00 UTC.
  • These counts pool every market, so markets that match often weigh more. Each market page compares that market with its own reference.
  • Live status is not connected yet, so this page is recorded history only.

What are MFE and MAE?

Reproducibility key (q#7678e940)

The key that re-runs this exact count. Same key, same bytes; when the record grows, the dataset revision changes.

grammar
research_query.v2
normalization
archive_normalization.v1
feature library
feature_defs.v1
dataset revision
4c8759ecac07743825c50afc1bb652dde9ccd3548dc4129f7df55196697e7242
query hash
7678e94059929b9596d9a7b0dc7b3ab91430e7f679f514d30b0ca5203f6622ca
scanned window
2026-10-05T00:00:00.000Z to 2026-11-04T00:00:00.000Z (UTC)

Re-run over the API

The exact search definition behind this count. 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.cascade_clustering_index",
        "gte",
        0.6
      ],
      [
        "times.anchor_time",
        "between",
        [
          "2026-10-05T00:00:00.000Z",
          "2026-11-04T00: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.cascade_clustering_index","gte",0.6],["times.anchor_time","between",["2026-10-05T00:00:00.000Z","2026-11-04T00:00:00.000Z"]]]},"sort":["times.anchor_time","desc"],"page":{"limit":50,"cursor":null}}'

Past examples from the record, not a guarantee or a prediction. Nothing here is trading advice.