BLESSUSDT · recorded history

One-sided tape: sellers on BLESSUSDT

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

Read it in context

  1. Read BLESSUSDT itself

  2. Its recorded moves

  3. Test it on BLESSUSDT, then plan it

    A tested result leads to Plan a trade, which measures what trading it would have paid after costs.

What happened in the next 24 hours?

Both moves were less common than on minutes without it.

Other minutes are the same markets and dates without this condition. Each percentage is the share of measured minutes that reached that move from the starting price.

Price touched +5% or higher

When this held
29.4% · 120 of 408 minutes
Other minutes
39.4% · 12,365 of 31,419 minutes

Price touched −10% or lower

When this held
9.6% · 39 of 408 minutes
Other minutes
17.3% · 5,429 of 31,419 minutes

Price can touch both levels within the same 24 hours.

This counts how often price touched a level, not what trading it would have paid.

Sample and counting

Rates use the 408 of 423 matches with a full 24 hours after them. The 15 newer ones are left out, not counted as zero.

Every condition is measured over the same 24 hours, whatever the length of its own reading. Other windows and move sizes shows shorter and longer windows.

When it happened
Matches per UTC day, 2026-10-04 to 2026-11-03

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

Over the full record

Every recorded day on BLESSUSDT, 2026-05-15 to 2026-08-14: reached +5% in 535 of 770 (69.5%); fell to −10% in 134 of 770 (17.4%), within 24 hours.

Other windows and move sizes
Matches that reached each move within each window. Counts first; the measured row is what each rate is over.
Move1 hour4 hours24 hours72 hours7 days
Measured422420408399361
Too recent13152462
+0.1% or more378 (89.6%)403 (96.0%)401 (98.3%)396 (99.2%)358 (99.2%)
+0.2% or more340 (80.6%)386 (91.9%)395 (96.8%)392 (98.2%)354 (98.1%)
+0.5% or more246 (58.3%)323 (76.9%)366 (89.7%)373 (93.5%)338 (93.6%)
+1% or more123 (29.1%)243 (57.9%)328 (80.4%)342 (85.7%)314 (87.0%)
+2% or more38 (9.0%)116 (27.6%)254 (62.3%)275 (68.9%)268 (74.2%)
+5% or more3 (0.7%)30 (7.1%)120 (29.4%)196 (49.1%)233 (64.5%)
+10% or more1 (0.2%)9 (2.1%)43 (10.5%)112 (28.1%)195 (54.0%)
+15% or more1 (0.2%)3 (0.7%)34 (8.3%)97 (24.3%)142 (39.3%)
+20% or more1 (0.2%)1 (0.2%)30 (7.4%)76 (19.0%)109 (30.2%)
+30% or more1 (0.2%)1 (0.2%)15 (3.7%)50 (12.5%)81 (22.4%)
+50% or more0 (0.0%)1 (0.2%)11 (2.7%)46 (11.5%)80 (22.2%)
−0.1% or lower379 (89.8%)401 (95.5%)402 (98.5%)397 (99.5%)360 (99.7%)
−0.2% or lower335 (79.4%)374 (89.0%)396 (97.1%)395 (99.0%)359 (99.4%)
−0.5% or lower245 (58.1%)327 (77.9%)385 (94.4%)387 (97.0%)356 (98.6%)
−1% or lower130 (30.8%)251 (59.8%)363 (89.0%)375 (94.0%)351 (97.2%)
−2% or lower39 (9.2%)119 (28.3%)295 (72.3%)336 (84.2%)333 (92.2%)
−5% or lower6 (1.4%)20 (4.8%)117 (28.7%)233 (58.4%)254 (70.4%)
−10% or lower1 (0.2%)3 (0.7%)39 (9.6%)133 (33.3%)173 (47.9%)
−15% or lower0 (0.0%)0 (0.0%)3 (0.7%)30 (7.5%)73 (20.2%)
−20% or lower0 (0.0%)0 (0.0%)1 (0.2%)1 (0.3%)8 (2.2%)
−30% or lower0 (0.0%)0 (0.0%)1 (0.2%)1 (0.3%)0 (0.0%)

Each window counts only matches old enough for it, so a longer window can show fewer.

Full record: other windows and move sizes
Matches that reached each move within each window. Counts first; the measured row is what each rate is over.
Move1 hour4 hours24 hours
Measured775773770
Too recent247
+1% or more414 (53.4%)607 (78.5%)724 (94.0%)
+2% or more204 (26.3%)466 (60.3%)679 (88.2%)
+5% or more25 (3.2%)161 (20.8%)535 (69.5%)
+10% or more4 (0.5%)36 (4.7%)288 (37.4%)
+15% or more2 (0.3%)16 (2.1%)166 (21.6%)
+20% or more1 (0.1%)5 (0.6%)112 (14.5%)
−1% or lower370 (47.7%)563 (72.8%)671 (87.1%)
−2% or lower166 (21.4%)391 (50.6%)594 (77.1%)
−5% or lower21 (2.7%)84 (10.9%)361 (46.9%)
−10% or lower5 (0.6%)21 (2.7%)134 (17.4%)
−15% or lower2 (0.3%)9 (1.2%)49 (6.4%)
−20% or lower0 (0.0%)0 (0.0%)20 (2.6%)

Each window counts only matches old enough for it, so a longer window can show fewer.

Distributions and daily counts
Upside reached · 24hUpside reached (MFE, 24h)The most price moved up within 24 hours of each match: a high-water mark, never a close. 408 with a complete 24 hours.
Drawdown · 24hDrawdown (MAE, 24h)The worst price moved against within 24 hours of each match: the deepest point, never the close. 408 with a complete 24 hours.
Price 30 minutes laterForward 30-minute returnForward 30-minute returns across 420 matches: close to an even split, which is what a coin flip looks like. 3 too recent.

How to read a distribution

Matches per UTC day

  • 4 Oct17 matches
  • 5 Oct18 matches
  • 6 Oct18 matches
  • 7 Oct15 matches
  • 8 Oct17 matches
  • 9 Oct17 matches
  • 10 Oct17 matches
  • 11 Oct15 matches
  • 12 Oct14 matches
  • 13 Oct14 matches
  • 14 Oct17 matches
  • 15 Oct13 matches
  • 16 Oct17 matches
  • 17 Oct16 matches
  • 18 Oct17 matches
  • 19 Oct18 matches
  • 20 Oct16 matches
  • 21 Oct15 matches
  • 22 Oct16 matches
  • 23 Oct17 matches
  • 24 Oct19 matches
  • 25 Oct18 matches
  • 26 Oct17 matches
  • 27 Oct15 matches
  • 28 Oct1 match
  • 29 Oct5 matches
  • 30 Oct1 match
  • 31 Oct8 matches
  • 1 Nov15 matches
  • 2 Nov0 matches
  • 3 Nov0 matches
How this is counted
  • Each rate counts only matches with the full window after them.
  • A minute where a reading was missing is left out and reported, not read as zero.
  • The condition picks the setup, never the outcome: a definition that filters on what followed is rejected (OUTCOME_IN_PREDICATE). Every match is measured, winners and losers alike.
  • "Other minutes" is every other eligible minute in the same market and window. It is a reference, not a control group.
  • "Reached +5%" uses the highest price inside the window (maximum favourable excursion, MFE); "fell to −10%" uses the lowest (maximum adverse excursion, MAE). Neither is the close.
  • Checked 41,713 eligible market-minutes (eligible_symbol_buckets) on BLESSUSDT, 2026-10-04 00:00 to 2026-11-03 00:00 UTC.

What are MFE and MAE?

Reproducibility key (q#307f4138)

The key that re-runs this exact count. Same key, same bytes; when the record grows, the dataset revision changes.

grammar
research_query.v2
normalization
archive_normalization.v1
feature library
feature_defs.v1
dataset revision
de0f2ef50baf530a363ce0c08cc21c068b14c0b5cf13829e8ff800ee4b3f829f
query hash
307f4138fa00024d3c605fc448a8ce0ecddd8932d3f86807dba01e8882b288aa
scanned window
2026-10-04T00:00:00.000Z to 2026-11-03T00:00:00.000Z (UTC)

Re-run over the API

The exact search definition behind this count. 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",
        "lte",
        0.38
      ],
      [
        "identity.symbol",
        "eq",
        "blessusdt"
      ],
      [
        "times.anchor_time",
        "between",
        [
          "2026-10-04T00:00:00.000Z",
          "2026-11-03T00: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","blessusdt"],["times.anchor_time","between",["2026-10-04T00:00:00.000Z","2026-11-03T00:00:00.000Z"]]]},"sort":["times.anchor_time","desc"],"page":{"limit":50,"cursor":null}}'

Past examples from the record, not a guarantee or a prediction. Nothing here is trading advice.