< One-sided tape: sellersNEARUSDT · historical base rate

One-sided tape: sellers on NEARUSDT

Taker buy ratio over the last 15 minutes has run at 0.38 or less: a persistently seller-heavy tape.

What has happened on NEARUSDT when it held

Historically, when One-sided tape: sellers on NEARUSDT held (386 occurrences in the scanned window, 371 with a computable 24h horizon), the market reached +5% within 24h in 67 of 371 (18.1) and drew down 10%+ in 4 of 371 (1.1). Maximum favorable (MFE) and maximum adverse (MAE) excursions, both computed forward.

Outcome distribution

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

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

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

🔒 COMPUTED FORWARD, NEVER A FILTER · DENOMINATOR 385 = 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 386 - ALL 386, NOT THE PAGE

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

FWD_RET_30M DISTRIBUTION · 386 PRESENT · 0 ABSENT

Forward 30-minute returns across 386 matches: 56% of them finished up.

Versus baseline

Historically, when any eligible NEARUSDT minute in the window (baseline) held (36,107 occurrences in the scanned window, 34,891 with a computable 24h horizon), the market reached +5% within 24h in 5,528 of 34,891 (15.8) and drew down 10%+ in 543 of 34,891 (1.6). Maximum favorable (MFE) and maximum adverse (MAE) excursions, both computed forward.

The full record

The same setup counted over every recorded day on NEARUSDT (2026-05-15 to 2026-07-31), growing daily.

Historically, when One-sided tape: sellers on NEARUSDT over the full record held (662 occurrences in the scanned window, 647 with a computable 24h horizon), the market reached +5% within 24h in 149 of 647 (23.0) and drew down 10%+ in 12 of 647 (1.9). Maximum favorable (MFE) and maximum adverse (MAE) excursions, both computed forward.

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

2 OF 661 (0.3%) REACHED ≥ +5% WITHIN 1H

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

🔒 COMPUTED FORWARD, NEVER A FILTER · DENOMINATOR 661 = 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 662 - ALL 662, NOT THE PAGE

About 8.5 a day, on 55 of 78 days: spread through the record rather than one event.

FWD_RET_30M DISTRIBUTION · 662 PRESENT · 0 ABSENT

Forward 30-minute returns across 662 matches: 56% of them finished up.

Reproducibility key (q#a5cfac63)

grammar: research_query.v2
normalization: archive_normalization.v1
feature library: feature_defs.v1
dataset revision: 52a43a418a97fbe3a324f7c372fa4d53967163acaa0ed33c56b78ddd897331a4
query hash: a5cfac63c9ec91a762669ca140e95e48276dfaa9aa0c64b727139fa2ba44cd97
scanned window: 2026-07-01T00:00:00.000Z to 2026-07-31T00: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",
        "lte",
        0.38
      ],
      [
        "identity.symbol",
        "eq",
        "nearusdt"
      ],
      [
        "times.anchor_time",
        "between",
        [
          "2026-07-01T00:00:00.000Z",
          "2026-07-31T00: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","lte",0.38],["identity.symbol","eq","nearusdt"],["times.anchor_time","between",["2026-07-01T00:00:00.000Z","2026-07-31T00: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 NEARUSDT right now: the NEARUSDT research page