Zcash Hardware Wallets: Transparent and Shielded Support

Start with the transaction type, not the coin logo

A hardware wallet can list Zcash as a supported asset while supporting only transparent transactions. Trezor’s knowledge base explicitly separates t-address support from shielded z-address support.

Holding keys offline and concealing public transaction information are different properties. Do not interpret a ZEC logo, coin listing or generic security statement as support for Orchard, Sapling, Unified Addresses or shielded change.

What the Trezor documentation establishes

The vendor describes adding a Zcash account in Trezor Suite, then explicitly states that Trezor devices only support public transactions using t-addresses and that shielded z-address transactions are not compatible. We preserve that vendor statement with a check time and text hash.

The page does not supply a firmware/version matrix; this guide cannot certify every device model or a newly released firmware. A shielded implementation proposal is not a released capability.

Ledger: do not turn incomplete evidence into a blanket verdict

The previously fetched Ledger support pages returned HTTP 200 but no usable explanatory text, so they cannot establish current address or transaction support. A separate developer repository describes Sapling support and a work-in-progress app; that is not proof of a current Ledger app-store release, Orchard support, or compatibility with any particular device and companion wallet.

Ledger’s current consumer release, device matrix and shielded-app integration remain unverified here. We therefore do not claim either universal shielded support or that every Ledger workflow is transparent-only.

Verification checklist before choosing a device

Identify the exact device model, installed firmware, Zcash application name/version and companion wallet version. Find vendor release notes describing the address/receiver type and supported send/receive flow.

Separately verify transparent, Sapling and Orchard support; a Unified Address is not itself proof that a particular receiver is accepted. Confirm whether shielding, shielded change, viewing-key export and recovery are supported in that exact combination.

Missing evidence should remain unknown, not be converted into a yes or no.

Security and recovery boundaries

This site never asks for a seed phrase, private key, recovery words, a wallet connection or a transaction signature. Do not use development firmware, example recovery material or unofficial installers with a device holding funds.

Device security does not eliminate host, backup, supply-chain or address-verification risks. No physical device testing, recovery drill or transaction signing was performed for this guide; it is not a purchase recommendation or a security certification.

FAQ