BANKUSDT · historical base rate

One-sided tape: buyers on BANKUSDT

Taker buy ratio over the last 15 minutes has run at 0.62 or more: a persistently buyer-heavy tape.

What has happened on BANKUSDT when it held

Historically, when One-sided tape: buyers on BANKUSDT held (172 occurrences in the scanned window, 171 with a computable 24h horizon), the market reached +5% within 24h in 85 of 171 (49.7) and drew down 10%+ in 5 of 171 (2.9). Maximum favorable (MFE) and maximum adverse (MAE) excursions, both computed forward.

Outcome distribution

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

6 OF 171 (3.5%) REACHED ≥ +5% WITHIN 1H

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

🔒 COMPUTED FORWARD, NEVER A FILTER · DENOMINATOR 171 = MATCHES WITH A COMPLETE 1H HORIZON (1 ABSENT: TOO CLOSE TO THE RECORD EDGE FOR 1H - NEVER TRUNCATED, NEVER AN IMPLIED ZERO)

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

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

FWD_RET_30M DISTRIBUTION · 171 PRESENT · 1 ABSENT

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

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

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

Versus baseline

Historically, when any eligible BANKUSDT minute in the window (baseline) held (39,379 occurrences in the scanned window, 37,911 with a computable 24h horizon), the market reached +5% within 24h in 27,888 of 37,911 (73.6) and drew down 10%+ in 12,423 of 37,911 (32.8). Maximum favorable (MFE) and maximum adverse (MAE) excursions, both computed forward.

The full record

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

Historically, when One-sided tape: buyers on BANKUSDT over the full record held (813 occurrences in the scanned window, 812 with a computable 24h horizon), the market reached +5% within 24h in 307 of 812 (37.8) and drew down 10%+ in 70 of 812 (8.6). Maximum favorable (MFE) and maximum adverse (MAE) excursions, both computed forward.

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

16 OF 812 (2.0%) REACHED ≥ +5% WITHIN 1H

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

🔒 COMPUTED FORWARD, NEVER A FILTER · DENOMINATOR 812 = MATCHES WITH A COMPLETE 1H HORIZON (1 ABSENT: TOO CLOSE TO THE RECORD EDGE FOR 1H - NEVER TRUNCATED, NEVER AN IMPLIED ZERO)

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

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

FWD_RET_30M DISTRIBUTION · 812 PRESENT · 1 ABSENT

Forward 30-minute returns across 812 matches: close to an even split, which is what a coin flip looks like.

Reproducibility key (q#96837aeb)

grammar: research_query.v2
normalization: archive_normalization.v1
feature library: feature_defs.v1
dataset revision: ce3b6253b51706f7a4c0e4a553e0dd67fcf76395dd1a8717eccda70dad520d60
query hash: 96837aeba6395016c7da63e5f2c50cd69503dc01fee82f5b99201dfa31661e6d
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.taker_buy_ratio_15m",
        "gte",
        0.62
      ],
      [
        "identity.symbol",
        "eq",
        "bankusdt"
      ],
      [
        "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.taker_buy_ratio_15m","gte",0.62],["identity.symbol","eq","bankusdt"],["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 BANKUSDT right now: the BANKUSDT research page