ZEC View

Zcash guides

Zcash Supply: Circulating ZEC and Issuance

Quick Answer

Observed supply and scheduled subsidy answer different questions. The network workspace reports a provider’s dated ZEC observations; the supply calculator sums a pinned reference subsidy rule in integer zatoshis. Neither is silently labeled independently verified circulating supply. A provider-reported supply value describes that provider’s measurement at a height and timestamp.

Key Takeaways

  • Issued supply and a market provider’s circulating supply can differ.
  • The reference calculator models scheduled issuance, not an observed current total.
  • Compare supply figures only with their date and denominator definition.

Choose the question before choosing a number

A provider-reported supply value describes that provider’s measurement at a height and timestamp. A scheduled subsidy sum describes the amount permitted by a chosen reference algorithm over a specified height range.

Circulating supply additionally requires an explicit definition of excluded funds and supporting evidence. This prototype has no independent node or approved circulating-supply methodology.

A field called supply is therefore displayed with its source, units, method and review state rather than treated as interchangeable with every other total.

The reference rule is versioned

The retrieved mainnet parameters define slow start and the Blossom transition. The reference calculator preserves slow-start integer arithmetic, spacing-ratio height scaling and halving right-shift rounding.

Its output unit is zatoshi, with any ZEC display conversion explicitly separate. The source version matters: draft NU7 changes are not merged into this reference schedule just because a proposal exists.

The halving guide links to the same pinned algorithm and parameter sources.

What the golden comparisons actually establish

A local C++ harness compiles the retrieved GetBlockSubsidy and Halving functions with the relevant reference parameters. Sixteen boundary/range comparisons match the TypeScript calculator.

This is cross-language function parity, not a complete-node compilation, observed block-by-block issuance audit or validation of every future consensus change. Height endpoints, integer rounding and cumulative output are covered; full live Supply Simulator verification remains incomplete.

Hypothetical output is intentionally isolated

A separate scenario accepts user-entered assumptions and labels its result hypothetical. It is not an on-chain rule change, activation prediction, current circulating value or forecast of market price.

The reference and scenario results must stay in different panels and cannot overwrite each other. A reader can inspect exact reference calculations without JavaScript; interactive scenario behavior needs JavaScript and sends no input to a server.

How to compare evidence without mixing dates

Use the network workspace to record one provider observation’s height, as-of, retrieval date, units and source status. Use the reference calculator to choose a height or bounded range and preserve its rule version.

A difference does not automatically identify a reconciliation error: units, cumulative/range meaning, issuance versus circulation and protocol context must first be comparable. Missing observations remain missing and quarantined rows are not used to construct a replacement supply curve.

FAQ

Can I call the cumulative reference result circulating supply?

No. It is a scheduled subsidy sum under a specific reference rule. Observed issuance and circulation need separate definitions and evidence.

Do sixteen golden comparisons prove a fully running node?

No. They compare compiled original functions with local TypeScript at selected boundaries/ranges; they are not node synchronization or live-chain validation.

Does a hypothetical scenario change the reference schedule?

No. The hypothetical panel is isolated and is never promoted to an active rule or observed supply value.

Sources and Methodology

Page updated: . Source observation dates remain separate.

zcash-src-chainparams-cpp

Source checked: 2026-10-01T16:25:34.040474+00:00

Source version and supporting details
  • Mainnet nSubsidySlowStartInterval=20000; Blossom nActivationHeight=653600.

558f686599586f55def3db86955d74d3be44605e
06392f1604c1fe643f7bb5ebd6b504a771cc78458b5945e16199d1167cbd26ba

zcash-src-consensus-params-h

Source checked: 2026-10-01T16:25:33.899983+00:00

Source version and supporting details
  • Pre/post Blossom target spacing and halving interval constants.

558f686599586f55def3db86955d74d3be44605e
3f5f0824bbee0f3b799282db913908425a412c97bdb036e53f3f1d3336086ada

zcash-src-consensus-params-cpp

Source checked: 2026-10-01T16:25:33.765933+00:00

Source version and supporting details
  • Halving height scaling, slow-start subsidy and GetBlockSubsidy integer right shift.

558f686599586f55def3db86955d74d3be44605e
673d3c7dbd81b7c33e472798aeb19d4e6c18b5b16b54c99f0e420ba0c7d6d0a7

Methodology and technical limitations

Method and limits

Sources are pinned zcashd consensus functions and mainnet parameters plus separately labeled third-party network observations. Official active-rule cross-check, node verification and a complete circulating-supply definition are still open. This page provides reproducible arithmetic and measurement boundaries, not a completed live simulator or investment recommendation.

Source dates describe the referenced observation or document, not a live price. How data is checked · Corrections