RIFUSDT · historical base rate

Swept the lows and reclaimed (1h) on RIFUSDT

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

Historically, when Swept the lows and reclaimed (1h) on RIFUSDT held (63 occurrences in the scanned window, 62 with a computable 24h horizon), the market reached +5% within 24h in 38 of 62 (61.3) and drew down 10%+ in 26 of 62 (41.9). Maximum favorable (MFE) and maximum adverse (MAE) excursions, both computed forward.

Outcome distribution

WHAT FOLLOWED · ALL 63 MATCHES

31 of 63 (49.2%) 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. 63 of the matches have a complete 1 hour forward.

What are MFE and MAE?

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

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

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

Forward 30-minute returns across 63 matches: 65% 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. 62 with a complete 24h.

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

Versus baseline

Historically, when any eligible RIFUSDT minute in the window (baseline) held (36,961 occurrences in the scanned window, 35,576 with a computable 24h horizon), the market reached +5% within 24h in 20,864 of 35,576 (58.6) and drew down 10%+ in 12,979 of 35,576 (36.5). Maximum favorable (MFE) and maximum adverse (MAE) excursions, both computed forward.

The full record

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

Historically, when Swept the lows and reclaimed (1h) on RIFUSDT over the full record held (102 occurrences in the scanned window, 101 with a computable 24h horizon), the market reached +5% within 24h in 61 of 101 (60.4) and drew down 10%+ in 39 of 101 (38.6). Maximum favorable (MFE) and maximum adverse (MAE) excursions, both computed forward.

WHAT FOLLOWED · ALL 102 MATCHES

53 of 102 (52.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. 102 of the matches have a complete 1 hour forward.

What are MFE and MAE?

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

About 1.3 a day, on 47 of 81 days: spread through the record rather than one event.

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

Forward 30-minute returns across 102 matches: 63% of them finished down.

How to read a distribution

Check our work: the key that re-runs this exact count (q#cdb00489)

grammar: research_query.v2
normalization: archive_normalization.v1
feature library: feature_defs.v1
dataset revision: a52c6390738e56734585b736b0a1c739bca72cac3f87cca21db6d03ebdd35d64
query hash: cdb00489850e88c62a23388bedd2aec5a0649502254246a850db3dd002664eb7
scanned window: 2026-07-04T00:00:00.000Z to 2026-08-03T00: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",
        "rifusdt"
      ],
      [
        "times.anchor_time",
        "between",
        [
          "2026-07-04T00:00:00.000Z",
          "2026-08-03T00: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","rifusdt"],["times.anchor_time","between",["2026-07-04T00:00:00.000Z","2026-08-03T00: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 RIFUSDT right now: the RIFUSDT research page