Live condition · historical base rate

Two-thirds of the tape on one side

Taker buy ratio over the last 15 minutes has run at two-thirds or more, a persistently one-sided tape.

Firing now (provisional, current bucket)

The live read is not yet enabled. This surface reports the historical base rates below; the firing-now list turns on when the live evaluator is connected.

What has happened when it held

Historically, when Two-thirds of the tape on one side held (264,468 occurrences in the scanned window, 233,451 with a computable 24h horizon), the market reached +5% within 24h in 57,606 of 233,451 (24.7) and drew down 10%+ in 8,584 of 233,451 (3.7). Maximum favorable (MFE) and maximum adverse (MAE) excursions, both computed forward.

Outcome distribution

WHAT FOLLOWED · ALL 264,468 MATCHES

195,197 of 241,689 (80.8%) reached +0% 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. 241,689 of the matches have a complete 1 hour forward; the other 22,779 are too recent to know.

What are MFE and MAE?

Why 7 days can show fewer than 1 hour: a match too recent for a complete 7 days is left out of that count entirely, even if it already reached the level within 1 hour. The two counts cover different sets of matches.

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

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

Where the next 30 minutes landed - 220,160 measured, 44,308 too recent

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

How to read a distribution

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

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

Versus baseline

Historically, when any eligible minute in the window (baseline) held (25,670,221 occurrences in the scanned window, 23,149,181 with a computable 24h horizon), the market reached +5% within 24h in 6,941,088 of 23,149,181 (30.0) and drew down 10%+ in 1,538,452 of 23,149,181 (6.6). Maximum favorable (MFE) and maximum adverse (MAE) excursions, both computed forward.

By market

Markets where this condition occurred often enough in the window to carry its own statistically meaningful receipt:

1000BONKUSDT 1000PEPEUSDT 1000RATSUSDT 1000SHIBUSDT 4USDT AAVEUSDT ACEUSDT ADAUSDT AINUSDT AIOUSDT AKEUSDT APRUSDT APTUSDT ARBUSDT ASTERUSDT ATOMUSDT AVAXUSDT BCHUSDT BICOUSDT BLESSUSDT BLUAIUSDT BMTUSDT BNBUSDT BOMEUSDT BRUSDT BTCUSDT BTRUSDT BULLAUSDT CAPUSDT COTIUSDT COWUSDT CYSUSDT DASHUSDT DEXEUSDT DOGEUSDT DOTUSDT EDENUSDT ENAUSDT ESPORTSUSDT ESPUSDT ETHUSDT EULUSDT FARTCOINUSDT FILUSDT FLOCKUSDT GIGGLEUSDT GPSUSDT GRVTUSDT GWEIUSDT HEIUSDT HEMIUSDT HFTUSDT HOMEUSDT HYPEUSDT INJUSDT IOSTUSDT KAITOUSDT KOMAUSDT LABUSDT LAUSDT LINKUSDT LITUSDT LSKUSDT LTCUSDT MAGMAUSDT MMTUSDT MOVRUSDT NEARUSDT ONDOUSDT ONEUSDT ONGUSDT ONUSDT OPUSDT ORDIUSDT PAXGUSDT PENGUUSDT POLUSDT PORTALUSDT PROMUSDT PUMPUSDT RAYSOLUSDT RIFUSDT SEIUSDT SKRUSDT SKYAIUSDT SOLUSDT SOPHUSDT SUIUSDT SYNUSDT TACUSDT TAOUSDT TIAUSDT TRUMPUSDT TRXUSDT TUSDT UAIUSDT UBUSDT UNIUSDT USELESSUSDT VELVETUSDT VTHOUSDT VVVUSDT WIFUSDT WLDUSDT WLFIUSDT XLMUSDT XMRUSDT XRPUSDT ZAMAUSDT ZECUSDT ZKCUSDT ZROUSDT

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

grammar: research_query.v2
normalization: archive_normalization.v1
feature library: feature_defs.v1
dataset revision: 8904ef0442c6f623ec772df2b59d7baf1e49aaa808b5b11ac31546605549e3bb
query hash: 63f07b1c23cc6ed6b41a82580ab45d4c3c8352a037bbd0add86a19c974bb39b4
scanned window: 2026-08-19T00:00:00.000Z to 2026-09-18T00: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.taker_buy_ratio_15m",
        "gte",
        0.66
      ],
      [
        "times.anchor_time",
        "between",
        [
          "2026-08-19T00:00:00.000Z",
          "2026-09-18T00: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.66],["times.anchor_time","between",["2026-08-19T00:00:00.000Z","2026-09-18T00: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.