EULUSDT · historical base rate

Swept the lows and reclaimed (1h) on EULUSDT

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 EULUSDT when it held

Historically, when Swept the lows and reclaimed (1h) on EULUSDT held (49 occurrences in the scanned window, 46 with a computable 24h horizon), the market reached +5% within 24h in 19 of 46 (41.3) and drew down 10%+ in 4 of 46 (8.7). Maximum favorable (MFE) and maximum adverse (MAE) excursions, both computed forward.

Outcome distribution

WHAT FOLLOWED · ALL 49 MATCHES

12 of 48 (25.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. 48 of the matches have a complete 1 hour forward; the other 1 are too recent to know.

What are MFE and MAE?

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

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

Where the next 30 minutes landed - 47 measured, 2 too recent

Forward 30-minute returns across 47 matches: 57% 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. 46 with a complete 24h.

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

Versus baseline

Historically, when any eligible EULUSDT minute in the window (baseline) held (38,101 occurrences in the scanned window, 35,939 with a computable 24h horizon), the market reached +5% within 24h in 14,500 of 35,939 (40.3) and drew down 10%+ in 5,326 of 35,939 (14.8). Maximum favorable (MFE) and maximum adverse (MAE) excursions, both computed forward.

The full record

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

Historically, when Swept the lows and reclaimed (1h) on EULUSDT over the full record held (92 occurrences in the scanned window, 89 with a computable 24h horizon), the market reached +5% within 24h in 28 of 89 (31.5) and drew down 10%+ in 4 of 89 (4.5). Maximum favorable (MFE) and maximum adverse (MAE) excursions, both computed forward.

WHAT FOLLOWED · ALL 92 MATCHES

27 of 91 (29.7%) 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. 91 of the matches have a complete 1 hour forward; the other 1 are too recent to know.

What are MFE and MAE?

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

About 1.1 a day, on 44 of 83 days: spread through the record rather than one event.

Where the next 30 minutes landed - 88 measured, 4 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#abf5e379)

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