Halving Clock Wave
Cycle model in protocol time: h = block height / 210,000, one halving cycle = exactly one unit. A public power-law framework provides the trend - refitted by least squares on Trinity full-node data at every sync, never frozen - and a damped harmonic wave traces the cycle path around it, framed by two bands. The price axis is root-scaled (price^(1/n)), which turns the power law into a literal straight line without a log axis. Historically the bands have contained roughly five days out of six.
What is it?
This chart measures Bitcoin's cycle in protocol time rather than calendar time. The clock is the blockchain itself: h = block height / 210,000, so one halving cycle equals exactly one unit, by construction. On that clock, a public power-law framework describes the long-term trend - and Trinity refits its two parameters by least squares on self-hosted full-node data at every synchronization, so the trend is never a frozen constant. Around the trend, a damped harmonic wave traces the typical cycle path: its amplitude shrinks by a fixed factor with each completed cycle. Two bands frame the wave path, with a floor excluding extreme lows. The price axis uses a root scale - every value is raised to the power 1/n - which turns the power-law trend into a literal straight line without any logarithmic axis.
How to read
Read the banner first: it states where the price sits inside the wave (above the path, around it, in the lower band zone), the dollar level of the path and of the trend for the hovered day, the current h reading, and the estimated distance to the next halving. On the canvas, the straight green line is the trend; the gold line is the wave path - the chart's signature; the orange and cyan lines are the upper and lower bands, with a light fill between them. Dashed full-height verticals mark each halving (H1, H2, …) at its real date; the next one is drawn from the recent block pace and labelled as estimated. The veiled area on the right extends trend, path and bands beyond the last data day: that is the projection, drawn dashed. Zoom with the mouse wheel and drag to pan - every timeframe from one year to the full history is available, and the full history is the default.
Key zones
Above the upper band: the price runs ahead of what the framework describes as a typical cycle stretch - historically rare and associated with late expansion phases. Upper band zone: elevated but historically visited in every cycle. Around the wave path: the price tracks the framework's typical rhythm. Lower band zone: compressed readings, historically frequent in the quarters following a cycle peak. Below the lower band floor: historically exceptional - the floor was calibrated precisely to exclude capitulation extremes. Across the full history, the two bands have contained roughly five days out of six; the remaining days sit outside, mostly below during deep bear phases.
What to observe
Two positions matter, and they are distinct: where the price sits relative to the wave path, and where the wave itself sits in its own phase - rising toward its crest or falling toward its trough. The wave crests roughly a quarter of a cycle after each halving, which is the framework's formalisation of the delayed post-halving expansion. Watch the damping: each completed cycle has oscillated with a smaller amplitude than the one before, and whether that contraction continues is the framework's central open question. Extended stays outside the bands, in either direction, are the strongest indication that the market is departing from the pattern of previous cycles.
Historical context
Four halvings have been observed - November 2012, July 2016, May 2020 and April 2024 - and the chart marks each at its real date, cross-checked against the node's own data. Across those cycles, the major peaks and troughs have formed inside or near the bands, with the deepest capitulations touching the band floor. The oscillation amplitude has contracted from cycle to cycle, which is exactly what the damping term encodes. The trend fit uses the framework's own window, starting a third of the way into the first cycle, so the earliest chaotic months of trading do not distort the slope.
Expert notes
The block height is reconstructed from the node's halving-countdown series rather than from a cumulative block count: the cumulative was measured to drift by thousands of blocks over the full history (orphan blocks), while the countdown reconstruction is exact and is cross-asserted against the canonical halving dates at every sync. The trend refit is ordinary least squares on log10(price) versus log10(h) - deliberately the simplest defensible estimator, recomputed daily, with guard rails that abort the sync rather than publish a fit outside plausible bounds. The wave parameters themselves (period, phase correction, damping factor, band offsets) are the published framework's constants and are transmitted to the chart with the data: the front end holds no model constant of its own, which is what allows the chart to keep evolving - including past future halvings - without a code change. Statistical honesty requires saying it plainly: the wave is fitted on four observed oscillations, the damping is a hypothesis rather than a law, and a framework this compact can fit the past well while failing the future.
Common mistakes to avoid
Treating the projection as a forecast: the veiled area extends a descriptive framework at the recent block pace; it is not a price target and carries no probability. Treating band coverage as a guarantee: five days out of six is a historical frequency, not a bound on the future. Confusing the root scale with a log scale: the axis shows dollars at positions spaced by price^(1/n) - straightness of the trend is a property of the transform, not evidence of inevitability. Reading the straight trend as a promise of appreciation: a power law fitted on the past says nothing binding about what comes next. Assuming the damping must continue: a future cycle with a larger amplitude would contradict the framework, and the chart would show exactly that.
Programmatic access
REST API
curl -sS \
'https://api.trinityinsights.io/api/v1/cycle-intelligence/metrics/cycle-halving-clock-wave/data?timeframe=90d' \
-H 'X-API-Key: $TRINITY_API_KEY'MCP server
{
"tool": "get_chart_value",
"metric_id": "cycle-halving-clock-wave",
"timeframe": "1y"
}Required tier: pro. See the pricing grid for the tier list and the MCP documentation for multi-client configuration.
Related metrics
Institutional disclaimer
Trinity Insights is an educational and analytical tool. The metric above does not constitute investment advice. Trinity Insights is not a Crypto-Asset Service Provider (CASP) registered under MiCA Regulation (EU) 2023/1114. See the full disclaimer.