< One-sided tape: sellersTRXUSDT · historical base rate

One-sided tape: sellers on TRXUSDT

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

What has happened on TRXUSDT when it held

Historically, when One-sided tape: sellers on TRXUSDT held (460 occurrences in the scanned window, 442 with a computable 24h horizon), the market reached +5% within 24h in 0 of 442 (0.0) and drew down 10%+ in 0 of 442 (0.0). Maximum favorable (MFE) and maximum adverse (MAE) excursions, both computed forward.

Outcome distribution

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

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

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

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

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

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

FWD_RET_30M DISTRIBUTION · 458 PRESENT · 2 ABSENT

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

Versus baseline

Historically, when any eligible TRXUSDT minute in the window (baseline) held (32,037 occurrences in the scanned window, 30,902 with a computable 24h horizon), the market reached +5% within 24h in 0 of 30,902 (0.0) and drew down 10%+ in 0 of 30,902 (0.0). Maximum favorable (MFE) and maximum adverse (MAE) excursions, both computed forward.

The full record

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

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

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

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

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

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

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

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

FWD_RET_30M DISTRIBUTION · 839 PRESENT · 2 ABSENT

Forward 30-minute returns across 839 matches: 55% of them finished up.

Reproducibility key (q#1e0daf56)

grammar: research_query.v2
normalization: archive_normalization.v1
feature library: feature_defs.v1
dataset revision: 52a43a418a97fbe3a324f7c372fa4d53967163acaa0ed33c56b78ddd897331a4
query hash: 1e0daf56e5696466a77427f2058b3dd330b47df2f60a5c1034e8b0e2e5b29a0f
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",
        "trxusdt"
      ],
      [
        "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","trxusdt"],["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 TRXUSDT right now: the TRXUSDT research page