Zcash privacy workflow
Watch: Zcash, transparent and shielded.
Transparent Zcash exposes addresses and amounts on-chain. Orchard shielded activity has different visibility and wallet-scanning requirements. A transparent balance is not automatically a shielded balance.
Check availability first
The shielded videos demonstrate a shielded-capable build. They do not establish that the same feature is available in every published Desktop/firmware combination. Check Supported Coins, the Orchard capability reference and release status before using these steps with funds. Use KeepKey Desktop for official application downloads.
Continue only when your exact build supports shielded Zcash and exposes Zcash → Privacy. A feature-flag label alone does not establish compatible firmware or completed release acceptance. If Privacy is absent, do not install an experimental firmware merely to match a video; stay with the supported workflow for your build.
The video names its demonstrated firmware prerequisite. This guide deliberately requires the exact build’s capability and release evidence rather than treating that version number as a universal support promise.
Initialize the privacy wallet
On a compatible build, open Zcash and choose Privacy. The first setup asks KeepKey to export a viewing key. Read and approve that request on the device only if you intend the application to scan this wallet’s shielded activity.
A viewing key cannot authorize spending by itself, but it can expose shielded financial information within its scope. Protect it and local wallet data, backups and reports. Do not post it in a support request. Confirm the intended wallet and passphrase before initializing or comparing balances.
Receive shielded Zcash
Watch: Receive shielded Zcash.
- In Zcash → Privacy, open Receive and identify the shielded receiving address.
- Select Show address on KeepKey. Read the full physical address, including all screens, and compare it with the address you intend to share. The demonstrated build also offers a device QR display.
- Stop if the address differs. Do not resolve a mismatch by trusting the computer’s copy.
- Confirm the sender supports the address and receiving pool, then make a small test before a larger payment.
- Let the wallet scan catch up and inspect the received result. A public explorer may not reveal the shielded recipient or amount; use the wallet’s scan and appropriate transaction evidence rather than expecting transparent-chain visibility.
See receiving and device verification for the general address-sharing checks.
Send shielded Zcash
- Let the privacy wallet synchronize, then open Send. Enter the intended recipient and amount from an independently verified source.
- Add a memo only when needed. Shielded memo contents are encrypted, but wallet viewing access can expose transaction information; do not treat a memo as a place for credentials or recovery material.
- Review the quote and fee before continuing. Desktop scans and prepares the transaction/proof before asking KeepKey to sign; allow that work to finish.
- Read the physical device’s requested details across all screens. Compare the recipient, amount where displayed, memo and fee with your intent. Reject unexpected data. Screen order can vary by build; a video frame is not a substitute for reviewing the actual request.
- After approval, check submission and resulting wallet state separately. If a step fails, preserve its status and transaction identifier if one exists before retrying.
Use the verification checklist and the state distinctions. A signature is not proof of broadcast or successful settlement.
Shield and synchronize
To move available transparent funds into the shielded pool on a compatible build, open Privacy → Shield, enter an amount or choose Max, and review the amount and fee. Confirm the intended operation on KeepKey, then check its submission and subsequent shielded scan. Shielding does not erase the earlier transparent transaction history.
The shielded balance comes from scanning chain data with the wallet’s viewing information. Scan time depends on wallet history, backend, connection and local state; the video’s timing is an example, not a guarantee. A wallet that is still scanning has not established a final balance.
If a balance or action is missing
Check the selected wallet/passphrase, compatible build, network connection and scan progress first. Determine whether the issue is transparent balance discovery, proof preparation, submission or shielded scanning. Record the exact error and any known transaction identifier before attempting another send.
Do not use Reset App Data as the first repair: it removes local Zcash wallet state and other application data. Read Settings → Danger zone and missing-balance troubleshooting. A device wipe is a separate operation and is not a sync remedy.