ZKCUSDT · recorded history

Crowd long, leaders not on ZKCUSDT

Global accounts sit at least 65% long while top traders run at least 10 points less long than the crowd.

Read it in context

Read ZKCUSDT itself
Inspect ZKCUSDT now or at a past minute
Its recorded moves
ZKCUSDT market events and replays
Test it on ZKCUSDT, then plan it
A tested result leads to Plan a trade, which measures what trading it would have paid after costs.
Edit this test in Workbench

What happened in the next 24 hours?

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: 9 of 21, too few for a rate
Other minutes: 33.5% · 6,089 of 18,203 minutes

Price touched −10% or lower

When this held: 0 of 21, too few for a rate
Other minutes: 14.5% · 2,636 of 18,203 minutes

Price can touch both levels within the same 24 hours.

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

Sample and counting

All 21 matches have a full 24 hours after them.

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.

When it happened

About 0.7 a day, on 8 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.
Move	1 hour	4 hours	24 hours	72 hours	7 days
Measured	21	21	21	21	17
Too recent	0	0	0	0	4
+0.1% or more	18	19	20	21	17
+0.2% or more	15	18	20	21	17
+0.5% or more	10	17	19	20	17
+1% or more	3	5	18	19	17
+2% or more	2	4	14	19	17
+5% or more	1	1	9	14	15
+10% or more	0	0	2	10	9
+15% or more	0	0	2	7	9
+20% or more	0	0	2	4	9
+30% or more	0	0	2	4	0
+50% or more	0	0	2	4	0
−0.1% or lower	17	19	21	21	17
−0.2% or lower	14	18	21	21	17
−0.5% or lower	7	11	20	20	17
−1% or lower	5	8	20	20	17
−2% or lower	2	2	11	12	11
−5% or lower	2	2	4	8	6
−10% or lower	0	0	0	0	3

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

Distributions and daily counts

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

Drawdown · 24hThe worst price moved against within 24 hours of each match: the deepest point, never the close. 21 with a complete 24 hours.

Price 30 minutes laterForward 30-minute returns across 20 matches: 60% of them finished up. 1 too recent.

How to read a distribution

Matches per UTC day

6 Aug2 matches
7 Aug0 matches
8 Aug0 matches
9 Aug0 matches
10 Aug0 matches
11 Aug0 matches
12 Aug0 matches
13 Aug0 matches
14 Aug0 matches
15 Aug0 matches
16 Aug3 matches
17 Aug0 matches
18 Aug6 matches
19 Aug0 matches
20 Aug0 matches
21 Aug4 matches
22 Aug2 matches
23 Aug0 matches
24 Aug0 matches
25 Aug0 matches
26 Aug0 matches
27 Aug0 matches
28 Aug1 match
29 Aug2 matches
30 Aug1 match
31 Aug0 matches
1 Sep0 matches
2 Sep0 matches
3 Sep0 matches
4 Sep0 matches
5 Sep0 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 market 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 41,761 eligible market-minutes (eligible_symbol_buckets) on ZKCUSDT, 2026-08-06 00:00 to 2026-09-05 00:00 UTC.

What are MFE and MAE?

Reproducibility key (q#88c84abf)

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: 34f116f07fb3d51d068549b18218a00d686edb1b9372c56da95228e2c10613aa
query hash: 88c84abf8727eddb6ca35ccc2eeb87b4283790093bfe61b43ff6f9d4082b6462
scanned window: 2026-08-06T00:00:00.000Z to 2026-09-05T00: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.top_global_long_skew",
        "lte",
        -0.1
      ],
      [
        "feature.global_long_ratio",
        "gte",
        0.65
      ],
      [
        "identity.symbol",
        "eq",
        "zkcusdt"
      ],
      [
        "times.anchor_time",
        "between",
        [
          "2026-08-06T00:00:00.000Z",
          "2026-09-05T00: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.top_global_long_skew","lte",-0.1],["feature.global_long_ratio","gte",0.65],["identity.symbol","eq","zkcusdt"],["times.anchor_time","between",["2026-08-06T00:00:00.000Z","2026-09-05T00:00:00.000Z"]]]},"sort":["times.anchor_time","desc"],"page":{"limit":50,"cursor":null}}'

Crowd long, leaders not on ZKCUSDT

Read it in context

Read ZKCUSDT itself

Its recorded moves

Test it on ZKCUSDT, then plan it

What happened in the next 24 hours?

Price touched +5% or higher

Price touched −10% or lower