All calls · @Finora_EN's record
@Finora_EN on RESOLV
Not scored The account was retired from collection, so its calls are kept on file but not followed backfilled
✅ $RESOLV 3.5x volume confirms the 4.3% move as continuation - my bias is bullish here on the 1h — structure already printed a higher high above 0.02025 and daily is aligned, so I treat this volume spike as continuation, not a trap, while weekly and BTC remain bearish (counter-trend vs those higher frames, so I demand a clean pullback confirmation before adding) - I expect price to tag the 0.02128 liquidity first, then stretch toward 0.02200 if that wick holds; a shallow dip into 0.02042–0.02015 (the unfilled imbalance under the spike) is the zone I want for longs - wait for a 5m/15m bullish engulfing or MSS off that 0.02042–0.02015 pocket, or a pin that sweeps 0.02015 then reclaims — do not chase the 0.02092 print after RSI 78.7 - take-profits in order: 0.02128, then 0.02200 - place protection beyond the structure flip / last HL — a 1h close below 0.01902 flips my bias to bearish 📊 Flow: OI $2.5M (+16.2% 24h) · funding +0.0050% · taker 1.38× Want the full breakdown with entry and exit levels? Free AI analysis →
Levels against price
RESOLV bull
- Written as
- “$RESOLV”
- Conviction
- firm
- Kind
- forward call
- Status
- Not scored
Stated invalidation. “a 1h close below 0.01902 flips my bias to bearish”
| Role | Level as written | Timeframe |
|---|---|---|
| target | 0.02128 | — |
| target | 0.02200 = $0.022 | — |
| entry | 0.02042–0.02015 = $0.02015–$0.02042 | — |
| invalidation | 0.01902 | 1h |
Why the analyst said it
my bias is bullish here on the 1h
structure already printed a higher high above 0.02025 and daily is aligned
I treat this volume spike as continuation, not a trap
the unfilled imbalance under the spike
Not checked: there is no priced market evidence from the moment this was posted.
At posting backfilled
Collected before tracking began. Posting-time evidence does not exist for this post.
Since posting Not scored
Not scored: the account was retired from collection, so its calls are kept on file but not followed.
- Monitoring from
- —
- Baseline
- not yet observed
- Horizon ends
- 28 Sep · 07:32
- Last check
- 26 Sep · 09: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.
Where this came from
source x_api · sha256 c8f7061951ebf480… · claim 2103749652696715695#0