Zcash Shielded Supply and Pool Balances

Define the numerator before using the percentage

The current provider schema supplies Sprout, Sapling, Orchard and an upstream label Ironwood. We preserve those exact labels and sum their balances for a source-defined shielded total.

We do not treat the presence of an Ironwood field as proof that a consensus upgrade has activated. Transparent and Lockbox are excluded from this numerator, but remain in the separate all-pool reconciliation.

Official protocol validation of the upstream schema is still open.

Use the same snapshot for the denominator

A percentage is numerator divided by source-reported total supply, times 100. Both must refer to the same snapshot and height.

Mixing a pool balance from yesterday with a supply total from today would describe no single observation. The dashboard exposes its as-of, retrieved-at, units and method so readers can distinguish them.

The HTTP request date does not replace the observation date.

Two reconciliation checks, not independent verification

The shielded sum is checked against the provider’s shieldedTotal field. All source-defined pool balances are separately checked against its supply total.

These checks catch missing fields and internal inconsistency. They do not establish that the provider used a correct node, that its interpretation matches consensus, or that redistribution is permitted.

Confidence stays source-reported, even when arithmetic passes.

What happened in the real historical snapshot

The sampled CSV contains 64 original days. Only 58 rows pass the local schema and arithmetic checks; six are quarantined.

Five rows have pool-versus-supply differences and one has an empty balance/supply observation. Those source values are retained for audit but not silently interpolated or used as valid computed totals.

This is a concrete reason to inspect row-level status instead of trusting a smooth graph.

FAQ