Skip to content

← Cycle intelligence

Demand vs Issuance

Public-domain supply-shock framework comparing daily Bitcoin protocol issuance (USD per day) against an on-chain proxy for daily net demand (the 7-day smoothed change in realized cap, USD per day). The chart juxtaposes the two flows on the same axis to expose post-halving supply-shock regimes and demand-side acceleration phases.

Tier proCycle intelligencedemandissuancesupply-shockpropost-halvingon-chain-flow

What is it?

Demand vs Issuance is a public-domain supply-shock framework that juxtaposes daily Bitcoin protocol issuance against a daily on-chain proxy for net demand. Issuance is the deterministic protocol output (subsidy_sum_24h × price, in USD per day), representing the new supply hitting the market each day. The demand-side proxy is the seven-day smoothed change in realized cap, also in USD per day - realized-cap delta is a clean on-chain proxy for the marginal dollar flow into the network at the current cost basis. The chart juxtaposes the two flows on the same axis to expose post-halving supply-shock regimes (where issuance halves) and demand-side acceleration phases (where realized-cap delta expands).

How to read

The chart shows two daily series on the same USD-per-day axis. The issuance series is rendered as the primary histogram bar (one bar per day, height = subsidy_sum_24h × price for that day). The demand-side proxy is overlaid as a secondary histogram bar with a contrasting color (one bar per day, height = realized_cap.diff() rolling-7d-mean). When the demand bar exceeds the issuance bar, the network is in a net-demand regime where dollar inflow exceeds new supply. When the issuance bar exceeds the demand bar, the network is in a supply-dominant regime. The most useful visual indication is the asymmetry between the two flows over multi-week windows: persistent demand > issuance has historically aligned with bull-expansion regimes; persistent issuance > demand has historically aligned with bear-distribution regimes. The post-halving structural break is visible as a step-down in the issuance bars at each halving event.

Key zones

Two structural regimes readable from the chart: • Net-demand regime (demand > issuance): the on-chain dollar flow into the network exceeds the daily protocol-issued supply. Historically associated with bull-expansion phases where mainstream demand absorbs new supply with room to spare. • Net-supply regime (issuance > demand): the on-chain dollar flow into the network is below the daily protocol-issued supply. Historically associated with bear-distribution phases where mainstream demand recedes and miners must rely on accumulated reserves to fund operations. • Post-halving step-down: each halving event causes a deterministic 50% reduction in the issuance bar height. This protocol-level supply-shock has historically preceded bull-expansion regimes by 6-18 months across past cycles, as the supply reduction takes time to translate into spot-price acceleration. • Demand surge episodes: a sudden multi-week expansion in the demand-proxy bar (realized-cap delta surge) has historically marked institutional accumulation episodes. The reading is most useful when sustained over multi-week windows; single-day spikes are typically UTXO-batching artifacts (large coinbase moves, exchange consolidations) rather than structural demand.

What to observe

• Persistent crossings between regimes: a multi-week period where demand consistently exceeds issuance (or vice versa) is the cleanest structural read. Single-day crossings are noise; multi-week crossings are regime indications. • Rate of demand-proxy expansion: a steepening realized-cap delta (acceleration of demand) is informational even before the bar reaches issuance parity. Acceleration changes precede regime crossings. • Issuance step-downs at halving events: the halving causes a deterministic 50% drop in the issuance bar. Compare the demand bar's response in the months following each halving - a sustained demand expansion that meets the post-halving issuance has historically preceded bull-expansion regimes. • Cross-cycle issuance asymmetry: across multiple completed inter-halving windows, the absolute issuance USD has trended structurally lower (subsidy halves while price grows on log axis). The cumulative issuance per cycle is structurally smaller in BTC terms, larger in USD terms - a base-effect compounding signature. • Cross-source corroboration: combine the on-chain demand proxy with macro liquidity context (M2 expansion, ETF approval windows) for full cross-context reading. The on-chain proxy captures all network participants but is one input among several.

Historical context

The supply-shock framework has been a long-established analytical pattern in cycle-aware Bitcoin analysis since the post-2012 halving era. Each completed inter-halving window has displayed a recognizable post-halving supply-reduction pattern in the issuance bars: an instantaneous 50% step-down at the halving block, then a structurally lower issuance plateau until the next halving. The on-chain demand proxy (realized-cap delta) reflects the network's marginal dollar flow at the current cost basis - a measure that captures all network participants regardless of their custody venue. Across past cycles, sustained periods of demand > issuance have aligned with the bull-expansion phases observed in the 12-24 months following each halving event. The chart is most informative at multi-week aggregation: daily volatility in the demand proxy is dominated by UTXO-batching artifacts that average out over weekly windows.

Expert notes

Methodology choice (estimation): the canonical industry framing of demand-vs-issuance is sometimes presented as etf_inflow + otc_estimated - etf_outflow versus daily protocol issuance. ETF flow data is not directly observable from a full-node Bitcoin series, and OTC flow is itself estimation-only - both depend on third-party aggregator series. This implementation uses the on-chain realized-cap delta (7-day smoothed) as the demand-side proxy, which is mathematically defensible and uses 100% public on-chain data with no third-party aggregator dependency. Realized-cap delta IS the dollar flow into the network at the current cost basis: when investors buy BTC and move it on-chain, the moved UTXOs re-price at the current spot, increasing realized cap; the converse mechanism applies on selling. The realized-cap proxy is strictly stronger than aggregator-only ETF flow series since it captures all network participants (ETFs + OTC + individual investors + miners + corporates) rather than a single venue category. The 7-day smoothing dampens UTXO-batching noise while preserving the structural weekly-cadence reading.

Common mistakes to avoid

• Reading single-day crossings as regime changes: single-day demand-vs-issuance crossings are dominated by UTXO-batching noise (coinbase moves, exchange consolidations). Multi-week sustained crossings are the structural read. • Treating the demand proxy as pure demand: the on-chain realized-cap delta captures dollar flow at the current cost basis from all network participants. It is a proxy, not a clean demand measurement - large UTXO consolidations can transiently inflate it without representing new demand. • Comparing absolute USD values across very early cycles and recent cycles on a linear scale: the issuance bar in USD terms grows across cycles as the spot price compounds (subsidy halves while price grows on log axis). Use log-scale or relative comparisons for cross-cycle readings. • Inferring price direction from the regime crossing: regime crossings are correlated with directional regimes historically, but they are not deterministic price triggers - past patterns may not recur, and Bitcoin cycle 5 may behave differently from prior cycles. • Confusing the demand proxy with ETF flow: the realized-cap delta captures all on-chain network flow at the current cost basis. ETF flow is a small subset (institutional spot ETFs only, post-2024). The two metrics are correlated but distinct - the on-chain proxy is structurally broader.

Programmatic access

REST API

curl -sS \
  'https://api.trinityinsights.io/api/v1/cycle-intelligence/cycle-demand-vs-issuance/history?days=90' \
  -H 'X-API-Key: $TRINITY_API_KEY'

MCP server

{
  "tool": "get_chart_value",
  "metric_id": "cycle-demand-vs-issuance",
  "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.