RIFUSDT · recorded history

One-sided tape: sellers on RIFUSDT

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

Read it in context

Read RIFUSDT itself
Inspect RIFUSDT now or at a past minute
Its recorded moves
RIFUSDT market events and replays
Test it on RIFUSDT, then plan it
A tested result leads to Plan a trade, which measures what trading it would have paid after costs.
Edit this test in Workbench

What happened in the next 24 hours?

Reaching +5% was less common than without it; falling to −10% was about as common as 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: 46.2% · 104 of 225 minutes
Other minutes: 60.8% · 23,196 of 38,134 minutes

Price touched −10% or lower

When this held: 31.1% · 70 of 225 minutes
Other minutes: 36.5% · 13,908 of 38,134 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 225 of 238 matches with a full 24 hours after them. The 13 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

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

Over the full record

Every recorded day on RIFUSDT, 2026-05-15 to 2026-08-03: reached +5% in 270 of 519 (52.0%); fell to −10% in 154 of 519 (29.7%), 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.
Move	1 hour	4 hours	24 hours
Measured	237	235	225
Too recent	1	3	13
+1% or more	113 (47.7%)	164 (69.8%)	196 (87.1%)
+2% or more	54 (22.8%)	106 (45.1%)	171 (76.0%)
+5% or more	6 (2.5%)	40 (17.0%)	104 (46.2%)
+10% or more	0 (0.0%)	11 (4.7%)	65 (28.9%)
+15% or more	0 (0.0%)	6 (2.6%)	41 (18.2%)
+20% or more	0 (0.0%)	6 (2.6%)	23 (10.2%)
−1% or lower	134 (56.5%)	190 (80.9%)	209 (92.9%)
−2% or lower	54 (22.8%)	140 (59.6%)	202 (89.8%)
−5% or lower	8 (3.4%)	41 (17.4%)	152 (67.6%)
−10% or lower	2 (0.8%)	11 (4.7%)	70 (31.1%)
−15% or lower	2 (0.8%)	6 (2.6%)	42 (18.7%)
−20% or lower	1 (0.4%)	3 (1.3%)	31 (13.8%)

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.
Move	1 hour	4 hours	24 hours
Measured	531	529	519
Too recent	2	4	14
+1% or more	288 (54.2%)	397 (75.0%)	458 (88.2%)
+2% or more	132 (24.9%)	281 (53.1%)	411 (79.2%)
+5% or more	18 (3.4%)	89 (16.8%)	270 (52.0%)
+10% or more	0 (0.0%)	21 (4.0%)	162 (31.2%)
+15% or more	0 (0.0%)	7 (1.3%)	107 (20.6%)
+20% or more	0 (0.0%)	7 (1.3%)	79 (15.2%)
−1% or lower	294 (55.4%)	414 (78.3%)	476 (91.7%)
−2% or lower	129 (24.3%)	312 (59.0%)	449 (86.5%)
−5% or lower	11 (2.1%)	88 (16.6%)	308 (59.3%)
−10% or lower	2 (0.4%)	13 (2.5%)	154 (29.7%)
−15% or lower	2 (0.4%)	6 (1.1%)	86 (16.6%)
−20% or lower	1 (0.2%)	3 (0.6%)	47 (9.1%)

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

Distributions and daily counts

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

Drawdown · 24hThe worst price moved against within 24 hours of each match: the deepest point, never the close. 225 with a complete 24 hours.

Price 30 minutes laterForward 30-minute returns across 237 matches: close to an even split, which is what a coin flip looks like. 1 too recent.

How to read a distribution

Matches per UTC day

4 Jul11 matches
5 Jul8 matches
6 Jul4 matches
7 Jul3 matches
8 Jul8 matches
9 Jul9 matches
10 Jul9 matches
11 Jul12 matches
12 Jul11 matches
13 Jul11 matches
14 Jul14 matches
15 Jul6 matches
16 Jul9 matches
17 Jul12 matches
18 Jul12 matches
19 Jul17 matches
20 Jul18 matches
21 Jul12 matches
22 Jul0 matches
23 Jul0 matches
24 Jul0 matches
25 Jul7 matches
26 Jul5 matches
27 Jul6 matches
28 Jul3 matches
29 Jul5 matches
30 Jul4 matches
31 Jul9 matches
1 Aug13 matches
2 Aug0 matches
3 Aug0 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,761 eligible market-minutes (eligible_symbol_buckets) on RIFUSDT, 2026-07-04 00:00 to 2026-08-03 00:00 UTC.

What are MFE and MAE?

Reproducibility key (q#98a9b091)

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: a52c6390738e56734585b736b0a1c739bca72cac3f87cca21db6d03ebdd35d64
query hash: 98a9b091c51f40660a6386faad4a48e4bdbee574186d6be6e6f83d898ce3b2b9
scanned window: 2026-07-04T00:00:00.000Z to 2026-08-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",
        "rifusdt"
      ],
      [
        "times.anchor_time",
        "between",
        [
          "2026-07-04T00:00:00.000Z",
          "2026-08-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","rifusdt"],["times.anchor_time","between",["2026-07-04T00:00:00.000Z","2026-08-03T00:00:00.000Z"]]]},"sort":["times.anchor_time","desc"],"page":{"limit":50,"cursor":null}}'

One-sided tape: sellers on RIFUSDT

Read it in context

Read RIFUSDT itself

Its recorded moves

Test it on RIFUSDT, then plan it

What happened in the next 24 hours?

Price touched +5% or higher

Price touched −10% or lower

Over the full record