
Bitcoin enters historical bottom window after supply-in-loss crossed 50% on June 5
CryptoQuant’s RCV Z-score at -2.35 adds a second late-bear signal, but datasets disagree on the 50% trigger.
Bitcoin has moved into a historically defined “bottom window” after a key onchain stress metric crossed a prior-cycle threshold on June 5. A separate cost-basis compression model is also printing deeply negative readings, though the supply-in-loss trigger depends on which dataset a trader uses.
Key Takeaways
- Bitcoin’s supply held at an unrealized loss crossed the 50% threshold on June 5, a level that has historically preceded macro bottoms within 101 days in prior cycles.
- Forty-two days had passed by July 17, putting the current cycle’s post-trigger stretch among the longest historical examples cited.
- CryptoQuant’s supply-in-loss reading sat at 46% on July 17, creating a live discrepancy versus the >50% framing used to start the countdown.
- CryptoQuant’s realized cap variance model printed a standardized Z-score of -2.35, described as the bottom 6% of its historical range and tied to strong forward 12-month returns in prior sub -2.0 regimes.
Supply-in-Loss Crossed 50% on June 5—A Historical Countdown Marker
K33 Research flagged that more than half of Bitcoin supply was held at an unrealized loss on June 5, treating the 50% line as a regime marker that has historically started a countdown toward a macro bear-market bottom.
The metric, “supply in loss,” tracks the share of coins whose onchain cost basis sits above the current market price. In K33’s historical framing, once supply in loss clears 50%, Bitcoin’s macro bottom has arrived no more than 101 days later.
That framing matters because it converts a vague “late bear” narrative into a time-bounded window. It does not, by itself, pin a date or price for the low.
How Long Past Cycles Stayed in the “Bottom Window”
K33’s cited examples show wide dispersion after the 50% trigger. The 2022 bear-market bottom arrived 13 days later, while 2018 took 23 days. The outlier was 2014, when Bitcoin continued to decline for 101 days after the threshold was hit.
As of July 17, 42 days had elapsed since the June 5 trigger. That makes the current window the second-longest among the historical examples referenced, which keeps timing risk open-ended inside the historical max rather than implying an immediate bottom.
K33 also argued that returns over the year following the supply-in-loss >50% phenomenon “tend to be very solid.” That is constructive for longer-horizon positioning, but it does not remove the possibility of additional downside inside the window.
CryptoQuant’s RCV Z-Score Hits -2.35 as Cost-Basis Compression Deepens
A second signal is coming from CryptoQuant’s realized cap variance (RCV) model, which compares realized cap against market cap to gauge how stretched or compressed investor cost basis is versus current valuation.
CryptoQuant described the RCV model as sitting in the bottom 6% of its historical range, with the standardized RCV Z-score at -2.35. Contributor Crazzyblockk summarized the interpretation bluntly: “When that variance compresses into deeply negative z-score territory, the emotional premium built during rallies has largely been priced out. The metric doesn’t read narrative, it reads the distribution of capital.”
CryptoQuant also tied extended time below a -2.0 Z-score to strong forward returns, stating: “Every prior stretch where the model spent extended time below a -2.0 z-score, late 2018, mid-2022, early 2015, preceded forward twelve-month returns north of 75%.” The historical anchor for how extreme the model can get was November 2018, when “-4.68 in November 2018, landed almost exactly on Bitcoin’s cycle bottom near $3,792.”
Signals Traders Can Track Next: Supply-in-Loss and Time Spent Below -2.0
The first practical issue is the trigger itself. CryptoQuant’s supply-in-loss reading was 46% as of July 17, which conflicts with the >50% threshold used to start K33’s June 5 countdown. For traders using 50% as a timing tool, the dataset and sampling choice is not a footnote. It is the signal.
Next is the clock. If June 5 is treated as the start point, day-count versus the historically cited 101-day maximum becomes the cleanest way to frame “late” versus “still room.”
On the cost-basis side, the real-time variable is persistence. CryptoQuant’s own claim hinges on whether the RCV Z-score remains below -2.0 for an extended stretch, and whether it trends toward more extreme readings relative to the cited -4.68 trough.
What These Onchain Regime Signals Do—and Don’t—Confirm Yet
I treat these as regime flags, not timing calls. The threshold that matters is the 50% supply-in-loss line, but the packet already shows why traders get chopped up by “clean” onchain triggers. One dataset says the market crossed it on June 5, another prints 46% on July 17. If the trigger condition depends on the feed, the tradeable edge is in consistency, not in the headline.
CryptoQuant’s -2.35 RCV Z-score looks more like a sentiment catalyst than a fundamental shift. The real test is whether the market stays in that compressed cost-basis regime long enough to resemble prior sub -2.0 stretches, and whether the June 5 window can be tracked cleanly on a single dataset without the signal moving underfoot.