ZECUSDT · historical base rate

Swept the lows and reclaimed (1h) on ZECUSDT

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

Historically, when Swept the lows and reclaimed (1h) on ZECUSDT held (44 occurrences in the scanned window, 43 with a computable 24h horizon), the market reached +5% within 24h in 6 of 43 (14.0) and drew down 10%+ in 0 of 43 (0.0). Maximum favorable (MFE) and maximum adverse (MAE) excursions, both computed forward.

Outcome distribution

WHAT FOLLOWED - ALL 44 MATCHES, FROM THE PER-SCAN SUMMARY

0 OF 44 (0.0%) REACHED ≥ +5% WITHIN 1H

METRIC MFE_1H · CHIPS RE-READ THE SUMMARY, NEVER RE-QUERY

🔒 COMPUTED FORWARD, NEVER A FILTER · DENOMINATOR 44 = MATCHES WITH A COMPLETE 1H HORIZON

OCCURRENCES PER DAY · UTC · SUM 44 - ALL 44, NOT THE PAGE

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

FWD_RET_30M DISTRIBUTION · 44 PRESENT · 0 ABSENT

Forward 30-minute returns across 44 matches: 64% of them finished down.

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

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

Versus baseline

Historically, when any eligible ZECUSDT minute in the window (baseline) held (38,461 occurrences in the scanned window, 37,029 with a computable 24h horizon), the market reached +5% within 24h in 10,490 of 37,029 (28.3) and drew down 10%+ in 120 of 37,029 (0.3). Maximum favorable (MFE) and maximum adverse (MAE) excursions, both computed forward.

The full record

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

Historically, when Swept the lows and reclaimed (1h) on ZECUSDT over the full record held (104 occurrences in the scanned window, 103 with a computable 24h horizon), the market reached +5% within 24h in 32 of 103 (31.1) and drew down 10%+ in 5 of 103 (4.9). Maximum favorable (MFE) and maximum adverse (MAE) excursions, both computed forward.

WHAT FOLLOWED - ALL 104 MATCHES, FROM THE PER-SCAN SUMMARY

3 OF 104 (2.9%) REACHED ≥ +5% WITHIN 1H

METRIC MFE_1H · CHIPS RE-READ THE SUMMARY, NEVER RE-QUERY

🔒 COMPUTED FORWARD, NEVER A FILTER · DENOMINATOR 104 = MATCHES WITH A COMPLETE 1H HORIZON

OCCURRENCES PER DAY · UTC · SUM 104 - ALL 104, NOT THE PAGE

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

FWD_RET_30M DISTRIBUTION · 104 PRESENT · 0 ABSENT

Forward 30-minute returns across 104 matches: 62% of them finished down.

Reproducibility key (q#d86bd264)

grammar: research_query.v2
normalization: archive_normalization.v1
feature library: feature_defs.v1
dataset revision: ce3b6253b51706f7a4c0e4a553e0dd67fcf76395dd1a8717eccda70dad520d60
query hash: d86bd264f8f1429110f198b5893ded2ca0ae626bc4ad3655a96b99d899889bef
scanned window: 2026-07-02T00:00:00.000Z to 2026-08-01T00: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 over the API or MCP

This is the exact research_query.v2 definition behind the receipt. Send it to the key-authed research API (or the MCP research tool) and diff 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",
        "zecusdt"
      ],
      [
        "times.anchor_time",
        "between",
        [
          "2026-07-02T00:00:00.000Z",
          "2026-08-01T00: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","zecusdt"],["times.anchor_time","between",["2026-07-02T00:00:00.000Z","2026-08-01T00: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 ZECUSDT right now: the ZECUSDT research page