HFTUSDT · recorded history

Swept the lows and reclaimed (1h) on HFTUSDT

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

Read it in context

  1. Read HFTUSDT itself

  2. Its recorded moves

  3. Test it on HFTUSDT, 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
8 of 27, too few for a rate
Other minutes
36.2% · 13,579 of 37,482 minutes

Price touched −10% or lower

When this held
1 of 27, too few for a rate
Other minutes
5.9% · 2,200 of 37,482 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 27 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-07-09 to 2026-08-08

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

Over the full record

Every recorded day on HFTUSDT, 2026-05-15 to 2026-08-08: reached +5% in 20 of 77 (26.0%); fell to −10% in 3 of 77 (3.9%), within 24 hours.

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 hours
Measured272727
Too recent000
+1% or more122027
+2% or more01024
+5% or more018
+10% or more002
+15% or more001
−1% or lower51421
−2% or lower1516
−5% or lower016
−10% or lower011
−15% or lower011
−20% or lower011

Each window counts only matches old enough for it, so a longer window can show fewer.

Full record: 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 hours
Measured777777
Too recent111
+1% or more25 (32.5%)49 (63.6%)66 (85.7%)
+2% or more2 (2.6%)27 (35.1%)53 (68.8%)
+5% or more1 (1.3%)4 (5.2%)20 (26.0%)
+10% or more0 (0.0%)0 (0.0%)10 (13.0%)
+15% or more0 (0.0%)0 (0.0%)4 (5.2%)
+20% or more0 (0.0%)0 (0.0%)2 (2.6%)
−1% or lower30 (39.0%)49 (63.6%)68 (88.3%)
−2% or lower4 (5.2%)18 (23.4%)55 (71.4%)
−5% or lower0 (0.0%)2 (2.6%)23 (29.9%)
−10% or lower0 (0.0%)1 (1.3%)3 (3.9%)
−15% or lower0 (0.0%)1 (1.3%)1 (1.3%)
−20% or lower0 (0.0%)1 (1.3%)1 (1.3%)

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

How to read a distribution

Matches per UTC day

  • 9 Jul4 matches
  • 10 Jul0 matches
  • 11 Jul1 match
  • 12 Jul2 matches
  • 13 Jul1 match
  • 14 Jul0 matches
  • 15 Jul0 matches
  • 16 Jul0 matches
  • 17 Jul2 matches
  • 18 Jul1 match
  • 19 Jul1 match
  • 20 Jul1 match
  • 21 Jul1 match
  • 22 Jul1 match
  • 23 Jul0 matches
  • 24 Jul0 matches
  • 25 Jul0 matches
  • 26 Jul1 match
  • 27 Jul1 match
  • 28 Jul0 matches
  • 29 Jul5 matches
  • 30 Jul2 matches
  • 31 Jul2 matches
  • 1 Aug0 matches
  • 2 Aug0 matches
  • 3 Aug1 match
  • 4 Aug0 matches
  • 5 Aug0 matches
  • 6 Aug0 matches
  • 7 Aug0 matches
  • 8 Aug0 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 HFTUSDT, 2026-07-09 00:00 to 2026-08-08 00:00 UTC.

What are MFE and MAE?

Reproducibility key (q#1a579065)

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
28acee8d0f123e535c8ba6325acd308c76bd0d511704f22e105e4b7842b6cb92
query hash
1a5790652ccf307a50bd699851a0c44be683cca2adc3020caef091f8bdf6a9c7
scanned window
2026-07-09T00:00:00.000Z to 2026-08-08T00: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.candle_sweep_reclaim_1h",
        "eq",
        "bullish"
      ],
      [
        "identity.symbol",
        "eq",
        "hftusdt"
      ],
      [
        "times.anchor_time",
        "between",
        [
          "2026-07-09T00:00:00.000Z",
          "2026-08-08T00: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","hftusdt"],["times.anchor_time","between",["2026-07-09T00:00:00.000Z","2026-08-08T00: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.