4USDT · recorded history

Crowd long, leaders not on 4USDT

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

Read it in context

  1. Read 4USDT itself

  2. Its recorded moves

  3. Test it on 4USDT, then plan it

    A tested result leads to Plan a trade, which measures what trading it would have paid after costs.

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
19 of 29, too few for a rate
Other minutes
70.1% · 10,252 of 14,624 minutes

Price touched −10% or lower

When this held
9 of 29, too few for a rate
Other minutes
41.9% · 6,123 of 14,624 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 29 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
Matches per UTC day, 2026-08-06 to 2026-09-05

About 0.9 a day, on 10 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
Measured2929292929
Too recent00000
+0.1% or more2829292929
+0.2% or more2728282828
+0.5% or more2627272727
+1% or more2125272727
+2% or more1421242426
+5% or more210192125
+10% or more0171423
+15% or more0061322
+20% or more004819
+30% or more000415
+50% or more000213
+100% or more00006
−0.1% or lower2629292929
−0.2% or lower2528282929
−0.5% or lower1825282929
−1% or lower1623272829
−2% or lower1016242829
−5% or lower26162224
−10% or lower1391115
−15% or lower0141013
−20% or lower000610
−30% or lower00004

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. 29 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. 29 with a complete 24 hours.
Price 30 minutes laterForward 30-minute returnForward 30-minute returns across 29 matches: 62% of them finished up. 0 too recent.

How to read a distribution

Matches per UTC day

  • 6 Aug1 match
  • 7 Aug1 match
  • 8 Aug5 matches
  • 9 Aug6 matches
  • 10 Aug2 matches
  • 11 Aug1 match
  • 12 Aug0 matches
  • 13 Aug0 matches
  • 14 Aug0 matches
  • 15 Aug0 matches
  • 16 Aug0 matches
  • 17 Aug0 matches
  • 18 Aug0 matches
  • 19 Aug0 matches
  • 20 Aug0 matches
  • 21 Aug0 matches
  • 22 Aug0 matches
  • 23 Aug8 matches
  • 24 Aug2 matches
  • 25 Aug0 matches
  • 26 Aug1 match
  • 27 Aug2 matches
  • 28 Aug0 matches
  • 29 Aug0 matches
  • 30 Aug0 matches
  • 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 4USDT, 2026-08-06 00:00 to 2026-09-05 00:00 UTC.

What are MFE and MAE?

Reproducibility key (q#8d0bb4a9)

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
8d0bb4a94edea5a64e7f2ac5a11789a4c3b2a6c3af422752e48d9047e7df8949
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",
        "4usdt"
      ],
      [
        "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","4usdt"],["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}}'

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