Zcash shielded transactions use private notes rather than publicly tracked transparent UTXOs, but not every Zcash transaction is shielded. What a transaction reveals depends on which address types and shielded pools it uses—and on the wallet’s transaction policy. A payment that crosses into a transparent address or between shielded pools can disclose information that a shielded-only payment within one pool does not.
What is the difference between a Zcash t-address and z-address?
Zcash supports transparent addresses, commonly called t-addresses, and shielded addresses, or z-addresses. The official Zcash Payment API describes transparent funds as unspent transaction outputs (UTXOs), while shielded funds are held as notes. Transparent-to-transparent transfers can use Bitcoin-compatible RPC calls; transfers involving shielded addresses use Zcash-specific RPC calls.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Cryptocurrency: Turn $20.00 In To $20,000: The Ultimate Beginner’s Guide About Blockchain Wallet,... | $2.99 | Buy on Amazon |
As an Amazon Associate I earn from qualifying purchases.
That distinction describes how value is represented and transferred; it does not mean every payment made with Zcash is private. A transparent address or transparent transaction path can expose participant and transaction details. Shielded features apply when the chosen path uses shielded addresses and pools, and the path can still disclose information when it crosses a privacy boundary.
Free tools Windows power users keep installed
One-click scans. No signup required.
How does a shielded transaction work?
At a high level, a shielded spend consumes one or more notes and creates new notes for the recipient and, when needed, change. The network checks that the transaction is valid without requiring shielded addresses to appear publicly in the transaction. That is the privacy benefit—not a guarantee that every detail of every Zcash payment is hidden.
The exact information exposed depends on the source and destination pools and the transaction policy the wallet uses. A shielded address alone does not determine the privacy of the complete transaction.
What does a Zcash shielded transaction hide?
Within a shielded path, shielded addresses are not publicly visible in transactions. ZIP 32 explains: “Shielded addresses are never publicly visible in transactions, which means that sending change back to the originating address is indistinguishable from using a change address.” Read the statement in the context of shielded transactions: it does not make a transparent participant or a pool-crossing amount private. See Zcash ZIP 32.
Whether the amount or participants are exposed depends on the transaction’s boundaries. In particular, sending from Orchard to a non-Orchard address reveals the transaction value, according to the Orchard protocol specification, ZIP 224. A wallet’s selected policy can also permit transparent senders or recipients, or amounts revealed when value moves between shielded pools.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsHow do transparent, shielded, and cross-pool paths compare?
| Transaction path | How funds are represented | Privacy boundary to notice |
|---|---|---|
| Transparent to transparent | Transparent UTXOs; the Payment API describes this path as using Bitcoin-compatible RPC calls. | It is a transparent path, not a shielded transfer. See the Payment API. |
| Shielded within one pool | Shielded notes are spent and new notes are created. | Shielded addresses are not publicly visible in transactions. The Zcash 6.12.2 FullPrivacy policy permits fully shielded transactions involving a single shielded value pool. See the 6.12.2 z_sendmany documentation. |
| Between shielded pools | Value moves from one shielded pool to another. | Pool boundaries matter: the 6.12.2 RPC documentation defines AllowRevealedAmounts for cross-pool transfers, and ZIP 224 says spending Orchard funds to a non-Orchard address reveals the transaction value. |
| Shielded and transparent participants in one transfer | The transaction includes a transparent sender or recipient as allowed by its policy. | The applicable 6.12.2 RPC policies allow options that disclose additional participant details. A shielded-capable wallet does not make every transaction shielded. |
Why do Sapling and Orchard pools matter?
Sapling and Orchard are distinct shielded pools, not one shared anonymity set. ZIP 224 explains that Orchard has a separate anonymity set from Sapling and Sprout. A new pool starts with no notes, so moving value between pools is not equivalent to keeping it within one pool. A shielded address label therefore does not tell you whether funds stay within the same pool throughout a payment.
The lightwallet protocol schema also enumerates an Ironwood pool, but that schema does not establish Ironwood’s consensus specification or confirm its Mainnet activation. See the lightwallet protocol schema.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.How do Unified Addresses affect a payment?
A Unified Address can bundle multiple receiver types, including an Orchard receiver. Orchard payment addresses do not have a standalone string encoding; they are represented through Unified Addresses. Mainnet Unified Addresses have a u1 human-readable prefix. A Unified Address can make receiver selection flexible, but its appearance alone does not establish which receiver or transaction path a wallet will use. See The Orchard Book’s keys and addresses guide.
The Zcash 6.12.2 RPC documentation says that change sent from a Unified Address is returned to the internal-only address associated with that account. That behavior is consistent with ZIP 32’s explanation that shielded change need not use a publicly distinguishable change address. See the z_sendmany documentation and ZIP 32.
What should you check in a wallet before sending?
Wallets do not necessarily expose the same privacy controls. The policy names below are from the Zcash 6.12.2 z_sendmany RPC, not universal labels or settings that every wallet provides.
- Check whether the transaction stays within one shielded pool. In the documented RPC,
FullPrivacypermits a fully shielded transaction involving a single shielded value pool. - Look for a pool-crossing warning.
AllowRevealedAmountsis the RPC policy for transfers across shielded pools, where amounts may be revealed. - Review transparent participants. The RPC includes transparent-recipient and transparent-sender options that disclose additional details, as well as
AllowFullyTransparentfor transparent inputs and outputs. - Do not assume a Unified Address guarantees a particular route. The documented
LegacyCompatpolicy behaves differently depending on whether a Unified Address is involved. Inspect the wallet’s transaction summary and privacy behavior rather than relying on the address label alone.
These policy definitions and behaviors are documented for Zcash 6.12.2’s z_sendmany RPC. They should not be treated as a claim that every wallet offers those exact choices.
One practical RPC limitation: coinbase funds
The same RPC documentation notes that when spending coinbase UTXOs, only shielded recipients are permitted and change is not allowed; the full value must be consumed. This is a documented implementation-specific payment behavior, not a general description of all Zcash transactions.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →
