Is Zcash Private? Transparent vs Shielded Transactions

How shielded privacy works

ZIP 224 defines Orchard as a shielded protocol with its own pool, spending keys and payment addresses. Its motivation discusses how Sprout and Sapling differ from the Orchard design, including proving-system setup considerations.

That is positive evidence for a protocol-specific privacy design. It is not evidence that every transaction involving ZEC uses Orchard, that every wallet has the same capabilities, or that an endpoint cannot reveal information outside the protocol.

The narrower question is which claim the source supports, not whether a product name sounds private.

Check the transfer, not only the receiving string

ZIP 316 defines receivers for particular transfer protocols and bundles receiver information in Unified Addresses. It explicitly allows a wallet to support Unified Addresses while supporting a subset of payment methods.

As a result, a format-support claim and a transaction-privacy claim have different scopes. This guide does not inspect real addresses or transfers; readers examining public documentation should look for the named receiver, transfer operation, release and platform rather than infer all of them from the address-format label.

Incoming and full disclosure are different

The same source defines viewing keys for payments to an address and, for Full Viewing Keys, payments from it. Incoming Viewing Keys can be derived from Full Viewing Keys.

These distinctions make it inappropriate to say that all payment information is always invisible to everyone. A holder may intentionally provide viewing access, and the scope of that access depends on the key and protocol.

This explanation does not recommend sharing a key and provides no key-upload or account-validation interface.

Revision and implementation boundaries

The pinned ZIP 316 header separates Revision 0 Active, Revision 1 Withdrawn and Revision 2 Draft. Later proposed requirements cannot be presented as universally deployed wallet behavior.

A protocol document at an immutable commit is reproducible source evidence, while a running release or device test would be implementation evidence. The local wallet database intentionally lists only source-stated capabilities and publisher warnings; it is not a security audit or a complete interoperability matrix.

What this answer deliberately does not claim

There is no blanket promise of complete anonymity, no probability that a transaction can or cannot be traced, and no claim about a particular person. Source-defined network balances do not supply those missing measurements.

Nor does a short protocol explanation prove operational safety, resistance to endpoint compromise or a correct configuration on an untested device. Those are separate questions that require appropriate evidence and expert review, not an expanded interpretation of the word shielded.

FAQ