MMTUSDT · historical base rate

Swept the lows and reclaimed (1h) on MMTUSDT

The last completed one-hour candle swept prior lows and closed back above them: the "bullish" sweep and reclaim formation on the hourly.

What has happened on MMTUSDT when it held

Historically, when Swept the lows and reclaimed (1h) on MMTUSDT held (45 occurrences in the scanned window, 44 with a computable 24h horizon), the market reached +5% within 24h in 21 of 44 (47.7) and drew down 10%+ in 7 of 44 (15.9). Maximum favorable (MFE) and maximum adverse (MAE) excursions, both computed forward.

Outcome distribution

WHAT FOLLOWED · ALL 45 MATCHES

15 of 45 (33.3%) reached +1% 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. 45 of the matches have a complete 1 hour forward.

What are MFE and MAE?

When they happened - one bar per UTC day, all 45 matches

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

Where the next 30 minutes landed - 45 measured, 0 too recent

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

How to read a distribution

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

Drawdown · 24hThe worst price moved against within 24h of each occurrence: the deepest point, never the close. 44 with a complete 24h.

Versus baseline

Historically, when any eligible MMTUSDT minute in the window (baseline) held (37,081 occurrences in the scanned window, 35,643 with a computable 24h horizon), the market reached +5% within 24h in 18,633 of 35,643 (52.3) and drew down 10%+ in 5,563 of 35,643 (15.6). Maximum favorable (MFE) and maximum adverse (MAE) excursions, both computed forward.

The full record

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

Historically, when Swept the lows and reclaimed (1h) on MMTUSDT over the full record held (88 occurrences in the scanned window, 87 with a computable 24h horizon), the market reached +5% within 24h in 44 of 87 (50.6) and drew down 10%+ in 8 of 87 (9.2). Maximum favorable (MFE) and maximum adverse (MAE) excursions, both computed forward.

WHAT FOLLOWED · ALL 88 MATCHES

37 of 88 (42.0%) reached +1% 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. 88 of the matches have a complete 1 hour forward.

What are MFE and MAE?

When they happened - one bar per UTC day, all 88 matches

About 1 a day, on 43 of 85 days: spread through the record rather than one event.

Where the next 30 minutes landed - 88 measured, 0 too recent

Forward 30-minute returns across 88 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#c11da1af)

grammar: research_query.v2
normalization: archive_normalization.v1
feature library: feature_defs.v1
dataset revision: 2f157bbdb91d341d09d9341ea73c8ceeeeee8acbe51e910f3b77fb76954ba6be
query hash: c11da1afe2ce96bff909e1edd045a53aa7dfb376f0e24f16c48c9f629e36b3b3
scanned window: 2026-07-08T00:00:00.000Z to 2026-08-07T00: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.candle_sweep_reclaim_1h",
        "eq",
        "bullish"
      ],
      [
        "identity.symbol",
        "eq",
        "mmtusdt"
      ],
      [
        "times.anchor_time",
        "between",
        [
          "2026-07-08T00:00:00.000Z",
          "2026-08-07T00: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.candle_sweep_reclaim_1h","eq","bullish"],["identity.symbol","eq","mmtusdt"],["times.anchor_time","between",["2026-07-08T00:00:00.000Z","2026-08-07T00: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 MMTUSDT right now: the MMTUSDT research page