< Crowd long, leaders notARBUSDT · historical base rate

Crowd long, leaders not on ARBUSDT

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

What has happened on ARBUSDT when it held

Historically, when Crowd long, leaders not on ARBUSDT held (25 occurrences in the scanned window, 25 with a computable 24h horizon), the market reached +5% within 24h in 4 of 25 (16.0) and drew down 10%+ in 0 of 25 (0.0). Maximum favorable (MFE) and maximum adverse (MAE) excursions, both computed forward.

Outcome distribution

WHAT FOLLOWED - ALL 25 MATCHES, FROM THE PER-SCAN SUMMARY

0 OF 25 (0.0%) REACHED +5% WITHIN 1H

METRIC MFE_1H · CHIPS RE-READ THE SUMMARY, NEVER RE-QUERY

🔒 COMPUTED FORWARD, NEVER A FILTER · DENOMINATOR 25 = MATCHES WITH A COMPLETE 1H HORIZON

OCCURRENCES PER DAY · UTC · SUM 25 - ALL 25, NOT THE PAGE
MAX 7 · 2026-07-1307-0607-1307-2007-272026-07-01 TO 2026-07-31 · 31 UTC DAYS · ZERO DAYS KEEP THEIR SLOT

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

FWD_RET_30M DISTRIBUTION · 25 PRESENT · 0 ABSENT
≥ +5: 0 OF 25000012119200000≤-20-20..-15-15..-10-10..-5-5..-2-2..-1-1..00..+1+1..+2+2..+5+5..+10+10..+15+15..+20≥+20

Forward 30-minute returns across 25 matches: 56% of them finished down.

Upside reached (MFE, 24h)Drawdown (MAE, 24h)

Versus baseline

Historically, when any eligible ARBUSDT minute in the window (baseline) held (38,691 occurrences in the scanned window, 37,191 with a computable 24h horizon), the market reached +5% within 24h in 5,380 of 37,191 (14.5) and drew down 10%+ in 48 of 37,191 (0.1). Maximum favorable (MFE) and maximum adverse (MAE) excursions, both computed forward.

The full record

The same setup counted over every recorded day on ARBUSDT (2026-05-15 to 2026-07-31), growing daily.

Historically, when Crowd long, leaders not on ARBUSDT over the full record held (25 occurrences in the scanned window, 25 with a computable 24h horizon), the market reached +5% within 24h in 4 of 25 (16.0) and drew down 10%+ in 0 of 25 (0.0). Maximum favorable (MFE) and maximum adverse (MAE) excursions, both computed forward.

WHAT FOLLOWED - ALL 25 MATCHES, FROM THE PER-SCAN SUMMARY

0 OF 25 (0.0%) REACHED +5% WITHIN 1H

METRIC MFE_1H · CHIPS RE-READ THE SUMMARY, NEVER RE-QUERY

🔒 COMPUTED FORWARD, NEVER A FILTER · DENOMINATOR 25 = MATCHES WITH A COMPLETE 1H HORIZON

OCCURRENCES PER DAY · UTC · SUM 25 - ALL 25, NOT THE PAGE
MAX 7 · 2026-07-13MAY 15JUN 01JUL 012026-05-15 TO 2026-07-31 · 78 UTC DAYS · ZERO DAYS KEEP THEIR SLOT

About 0.3 a day, on 6 of 78 days: spread through the record rather than one event.

FWD_RET_30M DISTRIBUTION · 25 PRESENT · 0 ABSENT
≥ +5: 0 OF 25000012119200000≤-20-20..-15-15..-10-10..-5-5..-2-2..-1-1..00..+1+1..+2+2..+5+5..+10+10..+15+15..+20≥+20

Forward 30-minute returns across 25 matches: 56% of them finished down.

Reproducibility key (q#5bc7afac)
grammar
research_query.v2
normalization
archive_normalization.v1
feature library
feature_defs.v1
dataset revision
52a43a418a97fbe3a324f7c372fa4d53967163acaa0ed33c56b78ddd897331a4
query hash
5bc7afac60548b54bb64fb4fc82f0a14c7dfe1f318216ff1367dc525f0ed461f
scanned window
2026-07-01T00:00:00.000Z to 2026-07-31T00: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 over the API or MCP

This is the exact research_query.v2 definition behind the receipt. Send it to the key-authed research API (or the MCP research tool) and diff 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",
        "arbusdt"
      ],
      [
        "times.anchor_time",
        "between",
        [
          "2026-07-01T00:00:00.000Z",
          "2026-07-31T00: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","arbusdt"],["times.anchor_time","between",["2026-07-01T00:00:00.000Z","2026-07-31T00: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 ARBUSDT right now: the ARBUSDT research page