Loading…
Published 16 Apr 2026, 13:58 UTC · fetched 20 Oct 2026, 05:28 UTC
Rekt Capital
@rektcapital
Quoting · 15 Apr 2026, 13:29 UTC · context given to the AI
#BTC Bitcoin is now pressing beyond the resistance of the Double Bottom formation Bitcoin would need to Weekly Close and/or post-breakout retest the top of the Double Bottom (blue $72810) to confirm a breakout And in fact if Bitcoin fully confirms a breakout from this Double Bottom, a Measured Move could see price rally to ~$81000-$82500 But given where Bitcoin is in the market cycle however, it's likely price will develop a macro market structure that will appear sufficiently bullish only to ultimately fail over time There are a number of ways Bitcoin could see this current overall cluster fail to generate sustained bullish momentum The failure could occur by virtue of rejecting from the Double Bottom resistance, by failed post-breakout retest to register a fake-breakout, or by falling short of a Measured Move once the breakout is confirmed $BTC #Crypto #Bitcoin#BTC Looking at this on the Daily timeframe, Bitcoin is struggling to breach the ~$74800 Daily resistance (black) If Bitcoin wants to Weekly Close above the Weekly resistance ($72810, blue), then price would need to hold the blue level as support on any upcoming dip The last time Bitcoin rejected from the black resistance in mid-March, price also lost the blue level as support Which is why a Daily Close below the blue level after any upcoming dip could see price drop back into the blue-blue Weekly Range The retest of the blue level on the Daily timeframe will literally be pivotal $BTC #Crypto #BitcoinView original on X ↗
Deterministic: the same prices and policy always give the same result
r = 77388.01 / 73790.19 − 1 = +4.88%d × r = -4.88% (neutral only if the price is unchanged) → incorrectOnly the end-of-horizon price counts. A brief move followed by a reversal is not a success. Read the methodology
Uses only text available at publication time
Think the interpretation or outcome is wrong? Sign in with X to request a correction, so reviewers know who is asking.
Sign in to request a correction