LITUSDT · historical base rate

One-sided tape: buyers on LITUSDT

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

What has happened on LITUSDT when it held

Historically, when One-sided tape: buyers on LITUSDT held (362 occurrences in the scanned window, 354 with a computable 24h horizon), the market reached +5% within 24h in 115 of 354 (32.5) and drew down 10%+ in 10 of 354 (2.8). Maximum favorable (MFE) and maximum adverse (MAE) excursions, both computed forward.

Outcome distribution

WHAT FOLLOWED · ALL 362 MATCHES

2 of 361 (0.6%) reached +5% or more within 1 hour

Pick a move size and a window: how often did a move at least that big follow?

🔒 Measured after every match, never by keeping winners. 361 of the matches have a complete 1 hour forward; the other 1 are too recent to know.

What are MFE and MAE?

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

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

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

Forward 30-minute returns across 362 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. 354 with a complete 24h.

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

Versus baseline

Historically, when any eligible LITUSDT minute in the window (baseline) held (35,078 occurrences in the scanned window, 33,732 with a computable 24h horizon), the market reached +5% within 24h in 11,477 of 33,732 (34.0) and drew down 10%+ in 1,373 of 33,732 (4.1). Maximum favorable (MFE) and maximum adverse (MAE) excursions, both computed forward.

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

grammar: research_query.v2
normalization: archive_normalization.v1
feature library: feature_defs.v1
dataset revision: 98dac62d96ea00e2e3b010d474acfd4a19e1ea7b4541e366a60e7da20c67fe00
query hash: b5ef3a4278a4186699dc0399eca3a9862211dddad7d9a6d9ec4944c1a98f6ef6
scanned window: 2026-07-24T00:00:00.000Z to 2026-08-23T00: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.62
      ],
      [
        "identity.symbol",
        "eq",
        "litusdt"
      ],
      [
        "times.anchor_time",
        "between",
        [
          "2026-07-24T00:00:00.000Z",
          "2026-08-23T00: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","litusdt"],["times.anchor_time","between",["2026-07-24T00:00:00.000Z","2026-08-23T00: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 LITUSDT right now: the LITUSDT research page