Published 17 Apr 2026, 12: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 Bitcoin's progression on the Daily timeframe has been promising, enabling price to maintain itself above the Double Bottom formation top of ~$73000 (blue) Bitcoin is as a result positioned for a positive Weekly Close Still, a Weekly Close just like this could precede a post-breakout retest into ~$73000 to attempt a full confirmation of the breakout However at the moment, it is the upcoming Weekly Close that will be most important to watch for After all, the last time price was at these prices in March, Bitcoin ended up producing an upside wick, which is why the Weekly Close is worth monitoring $BTC #Crypto #BitcoinView original on X ↗
Deterministic: the same prices and policy always give the same result
unscored Awaiting manual review
Only 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