ZEC View

Zcash guides

Zcash Value Pools: Transparent and Shielded Balances

Quick Answer

A value-pool ledger reports balances under named source fields. In this local dataset, pool totals can be checked against the same provider’s supply and shielded totals, but arithmetic reconciliation is not independent chain or activation verification. The inspected provider schema names Transparent, Sprout, Sapling, Orchard, Ironwood and Lockbox.

Key Takeaways

  • Transparent and shielded balances describe different parts of network supply.
  • The shielded total includes Sprout, Sapling, Orchard and Ironwood.
  • Pool balances measure value held, not a count of users or transactions.

What is in this source-defined ledger

The inspected provider schema names Transparent, Sprout, Sapling, Orchard, Ironwood and Lockbox. These are preserved as upstream labels instead of being silently renamed or promoted to official protocol conclusions.

The source reports values in ZEC and includes dated historical observations. Ironwood appearing as a field does not prove consensus activation.

Verifying the official definition and upgrade context of every field remains a separate research requirement.

Two totals answer different questions

The shielded total in this prototype sums the named Sprout, Sapling, Orchard and Ironwood fields. Transparent and Lockbox are excluded from that numerator.

The all-pool reconciliation instead uses all six balances and compares their sum with source-reported supply. Both operations refer to one row or snapshot, in ZEC.

A shielded balance is not an address count, user count, transfer volume or privacy-quality measure.

How to reproduce a row-level check

Open the network workspace and inspect a row’s date, height, status, balances and source URL. Download the CSV audit export to retain the fields and reason for any failure.

For a complete comparable row, sum the same named fields as the displayed method and compare the result with that row’s aggregate. The local numerical tolerance is 0.000001 ZEC for arithmetic precision; it is not an independent statement about node correctness or financial materiality.

Why the history includes quarantined rows

The actual sampled provider CSV has 64 rows. Six are quarantined: five fail the pool-versus-supply check and one has missing cells.

Keeping these rows and their reasons in the audit view preserves the original evidence. Computed shielded totals are withheld for quarantined rows.

Missing dates are not interpolated, balances are not set to zero to make a chart look complete, and no provider error is silently repaired into an approved fact.

Balance changes do not identify their cause

A difference between two snapshots is not by itself evidence of adoption, ETF inflows, wallet users or an upgrade’s success. Pool migration and broader causal claims require transaction or protocol evidence that this draft has not verified.

Cross-day comparisons must preserve the original timestamps and schema; a request made today does not make an older observation current.

FAQ

Is Lockbox part of the shielded numerator here?

No. The displayed source-defined calculation excludes both Transparent and Lockbox, while retaining them in the separate all-pool reconciliation. This methodological exclusion is not a comprehensive official protocol definition.

Does an Ironwood column prove a live upgrade?

No. A provider’s schema label is not activation evidence. Network, consensus rule and activation-height sources must be checked separately.

Should quarantined history disappear?

No. The original row and failure reason remain available for audit, but it must not feed a computed valid total or be silently replaced with zero.

Sources and Methodology

Page updated: . Source observation dates remain separate.

Methodology and technical limitations

Method and limits

The data is a third-party snapshot from zecstats.org, not a project-operated node. Finite-value, recognized-field and arithmetic checks are local validation only; confidence remains source-reported. Official pool definitions, independent-node cross-check, reuse licensing and operational collection are not complete.

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