Saturday 26 September 2026 · data as of the 26 Sep · 11:45 check · all times UTCPractice only · no trades are placed

Receipts

What crypto analysts said, what the market showed when they said it, and what happened next.

All calls · @Cryptoguruu_12's record

@Cryptoguruu_12 on PROM

Waiting for a price backfilled

25 Sep · 16:32
$PROM BREAKOUT... BUYERS ARE TAKING OVER #PROM is showing strong 1H bullish momentum after breaking above the recent consolidation around $5.60. The latest candle is pushing into the $5.85 resistance area with strong buying pressure. LONG TRADE SETUP Entry: $5.75 – $5.85 TP1: $6.00 TP2: $6.20 TP3: $6.40 SL: $5.60 Buy & Trade $PROM
8 levels on one axis

Levels against price

$5.60support $5.60invalidation $5.75entry $5.85resistance $5.85entry $6.00target $6.20target $6.40target
Linear price axis, $5.55 to $6.45.

8 levels stated

PROM bull

Written as
“$PROM”
Conviction
firm
Kind
forward call
Status
Waiting for a price

Stated invalidation. “SL: $5.60”

Levels exactly as written; the reading is shown where it isn't obvious
RoleLevel as writtenTimeframe
support $5.60 —
resistance $5.85 —
entry $5.75 —
entry $5.85 —
target $6.00 —
target $6.20 —
target $6.40 —
invalidation $5.60 —
3 reasons stated

Why the analyst said it

  • strong 1H bullish momentum
  • breaking above the recent consolidation around $5.60
  • strong buying pressure

Not checked: there is no priced market evidence from the moment this was posted.

no snapshot

At posting backfilled

Collected before tracking began. Posting-time evidence does not exist for this post.

last check 26 Sep · 11:45

Since posting Waiting for a price

Waiting for the first observed price.

Monitoring from
—
Baseline
not yet observed
Horizon ends
09 Oct · 16:32
Last check
26 Sep · 11:45

Monitoring began after the post. If price crossed a level before then, the crossing was not observed and its order is unknown, so it is not counted.

What was observed

  1. 26 Sep · 09:39No price: RYO market data unavailable

Checked every quarter-hour; a move between checks can be missed.

sha256

Where this came from

source x_api · sha256 401b1ad6a1c028b8… · claim 2103523135605936298#0