Did Bitcoin always rise after a halving?
In all four completed seasons, the major high selected by BtcCal was observed after the halving. Four cases, however, cannot establish that the halving caused a rise or that the next season will follow the same path.
The table separates the CoinGecko close on halving day from a later TradingView BTC Index daily-candle high. Both the date and price basis differ, so this is a limited before-and-after comparison.
- Completed halvings
- 4
- Halving-day closes available
- 3 seasons
- Observed high positions
- D+366 to D+548
Four historical outcomes are not a repeatable rule
In BtcCal's confirmed cycle data, the major high coordinates for Seasons 1–4 all fall in positive territory after the halving. That describes where selected observations occurred; it does not mean price rose continuously from the halving. Every path included substantial advances and declines, and the time to the selected high varied.
A halving is a protocol event that lowers new issuance. Market price reflects demand, liquidity, macroeconomic conditions, market structure, and other factors. The two can be placed on the same timeline, but the timeline alone does not prove that one was the sole cause of the other.
Compare completed halvings with their later observed highs
The halving-day value is the downloaded CoinGecko BTC/USD daily close. The high is a candle-wick observation made by BtcCal on the TradingView INDEX:BTCUSD UTC daily chart. Where both prices exist, the multiple simply divides the observed high by the halving-day close.
| Season | Low coordinate | Halving-day close | Observed high | BTC Index intraday high | Versus halving close |
|---|---|---|---|---|---|
| Season 1 Confirmed | D-377 | — · before CSV coverage |
D+366 |
$1,242 | — |
| Season 2 Confirmed | D-542 | $650.32 |
D+526 |
$19,804 | 30.45× |
| Season 3 Confirmed | D-513 | $8,602 |
D+548 |
$68,998 | 8.02× |
| Season 4 Confirmed | D-516 | $64,976 |
D+534 |
$126,219 | 1.94× |
A close and an intraday high are not the same price basis
A close is the end-of-day reference value, while an intraday high is the extreme reached at some point during that day. The providers also differ: the CoinGecko BTC/USD snapshot and the TradingView BTC Index do not represent one identical series. The two columns should not be joined as if they were precise start and end values from a single dataset.
Separate slower issuance from market-price outcomes
The value that changes immediately at the target block is the block subsidy. New issuance falls by half, but existing supply, trading demand, liquidity, leverage, and external economic conditions are not fixed by that event.
This comparison records where selected highs occurred after past halvings. It does not calculate a future price, target, or time to buy or sell.
Two sources and the calculation boundary
Halving dates and coordinates come from BtcCal's cycle data, while closes are read from the static CoinGecko CSV during generation. When a newly verified CSV or cycle observation is applied, the table is rebuilt through the same shared calculation logic.
- CoinGecko Bitcoin historical data CSV · close snapshot 2013-04-28–2026-08-09 · Verified 2026-08-10
- TradingView BTCUSD Index chart · UTC daily intraday lows and highs · Verified 2026-08-10
- How TradingView calculates the BTC Index
Limits of sample size and market context
Only four halvings are complete, and the first halving predates the current CoinGecko snapshot, so it has no halving-day close for this comparison. The number of comparable seasons is smaller still. Market size, trading infrastructure, regulation, and macroeconomic conditions differed across seasons, so they are not independent repetitions of one experiment.
BtcCal applies a published rule to select cycle highs, but another index, timezone, or price basis may produce a different date or price. A historical range is not a forecasting rule for the next season.
Content updated