PUMPUSDT · historical base rate

One-sided tape: sellers on PUMPUSDT

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

What has happened on PUMPUSDT when it held

Historically, when One-sided tape: sellers on PUMPUSDT held (375 occurrences in the scanned window, 360 with a computable 24h horizon), the market reached +5% within 24h in 126 of 360 (35.0) and drew down 10%+ in 9 of 360 (2.5). Maximum favorable (MFE) and maximum adverse (MAE) excursions, both computed forward.

Outcome distribution

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

2 OF 374 (0.5%) REACHED ≥ +5% WITHIN 1H

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

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

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

FWD_RET_30M DISTRIBUTION · 374 PRESENT · 1 ABSENT

Forward 30-minute returns across 374 matches: 57% of them finished up.

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

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

Versus baseline

Historically, when any eligible PUMPUSDT minute in the window (baseline) held (36,526 occurrences in the scanned window, 35,278 with a computable 24h horizon), the market reached +5% within 24h in 12,640 of 35,278 (35.8) and drew down 10%+ in 834 of 35,278 (2.4). Maximum favorable (MFE) and maximum adverse (MAE) excursions, both computed forward.

The full record

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

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

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

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

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

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

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

FWD_RET_30M DISTRIBUTION · 716 PRESENT · 2 ABSENT

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

Reproducibility key (q#0e88a1e2)

grammar: research_query.v2
normalization: archive_normalization.v1
feature library: feature_defs.v1
dataset revision: ce3b6253b51706f7a4c0e4a553e0dd67fcf76395dd1a8717eccda70dad520d60
query hash: 0e88a1e2d258e0cd52fdb0717cb9bd65cd132fd4fca46fe4c26fb99592ae8beb
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",
        "lte",
        0.38
      ],
      [
        "identity.symbol",
        "eq",
        "pumpusdt"
      ],
      [
        "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","lte",0.38],["identity.symbol","eq","pumpusdt"],["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 PUMPUSDT right now: the PUMPUSDT research page