A Zcash mining pool payout address is the destination used to receive ZEC withdrawn from a miner's pool account. Transparent addresses make the transparent side of a payment public, shielded addresses protect the receiving address on-chain, and Unified Addresses can combine different receiving options in one address string. Whether a payout succeeds depends on both the address's validity and the pool's support for that address format and payment type.
For miners using an account-based pool such as ViaBTC, reward calculation, account crediting, and withdrawal are separate steps. Rewards are calculated under the selected payment method, credited according to the pool's accounting rules, and paid out under its withdrawal rules. PPS-based reward calculation should not be described as occurring only when the pool finds a block.
Transparent Zcash Payout Addresses
A transparent Zcash address, commonly called a t-address, receives value as unspent transaction outputs (UTXOs), structurally similar to Bitcoin. In a transparent-to-transparent transaction, the input and output addresses and amounts are publicly visible.
When a transaction combines transparent and shielded components, only the transparent side's addresses and amounts are public in that way. A payment from shielded funds to a transparent address exposes the transparent recipient and output amount, but it does not expose the shielded sender's address.
For a miner, a transparent address can be a straightforward payout destination when the pool accepts it: the transparent output is easy to verify on a block explorer. The tradeoff is that the receiving address and payout amount are public.
Shielded Zcash Payout Addresses
Shielded Zcash payments represent value as notes rather than transparent UTXOs. Sapling and Orchard protect shielded receiving addresses and note values from public blockchain observers. Sapling has a standalone address format; Orchard receivers are presented through Unified Addresses.
To pay a shielded receiver, a pool's withdrawal system must be able to construct an output for the receiver's protocol. The receiving wallet must also be able to recognize and use that output. This does not mean the pool's funds must already be held in the same shielded value pool: compatible software can construct payments from transparent funds or across supported value pools.
Receiving a shielded output does not make every part of the transaction private. In a transparent-to-shielded payment, the transparent inputs remain public. Net amounts entering or leaving a shielded value pool can also be visible, although these do not always reveal the amount paid to an individual recipient. Privacy therefore depends on the transaction's inputs and outputs as well as the destination address.
A valid shielded address is not enough on its own. A pool that supports only transparent withdrawals cannot construct a shielded payout merely because a miner supplies a shielded address.
Unified Addresses: What They Solve, and What They Do Not
A Unified Address (UA) is an encoded container for one or more receivers, rather than a separate shielded payment protocol. It can include an Orchard receiver, a Sapling receiver, and a transparent receiver in one address string.
ZIP 316 requires a conforming sender to use the highest-priority receiver it supports from those present in the UA: Orchard first, then Sapling, then transparent. A sender that supports an included shielded receiver cannot simply ignore that priority and choose the transparent receiver instead.
However, a UA does not guarantee a shielded payment. A conforming sender that can parse the UA but supports only transparent payments can use its transparent receiver, if one is present. If the UA contains no receiver the sender can pay, the payment cannot proceed. A service that cannot parse UAs may reject the address altogether.
As checked on October 20, 2026, ZIP 316 Revision 0 is Active and Revision 2 remains Draft. Revision 0 UAs use the u prefix on mainnet and contain at least one shielded receiver, with an optional transparent receiver. The draft introduces zu and tu prefixes to distinguish shielded-only and transparent-enabled UAs. Miners should not assume those draft formats are supported by their wallet or pool.
The practical takeaway is that both the receivers contained in the UA and the sender's capabilities determine how payment can be made, subject to the standard's selection rules. More background is available in Z.cash's Unified Addresses explainer.
Pool Payouts Versus Direct Coinbase Mining
For an account-based pool, a withdrawal should be distinguished from the coinbase transaction that creates a block's mining reward. ZIP 213 gives an example in which a pool pays miners using ZEC it already held rather than the coinbase output of the newly mined block.
That example illustrates a possible funding source, not a universal payout architecture for every pool. Likewise, support for shielded coinbase outputs does not establish which withdrawal address types a pool offers its participants. For payout setup, the pool's current withdrawal rules are the relevant guide.
How to Choose and Verify a ZEC Payout Address
Before relying on a new payout destination:
- Confirm the exact address formats supported by the pool's withdrawal system. A valid Zcash address is not automatically a supported payout address.
- Use a receiving address generated by the intended wallet or exchange account. For a shielded address, confirm support for the relevant protocol.
- For a UA, check whether the pool can parse it and which of its receivers the pool can pay. If privacy is the goal, accepting the UA alone is not enough to establish that the payout will be shielded.
- Copy and paste the full address rather than retyping it, and verify it against the source wallet before saving it.
ViaBTC Withdrawal Settings for ZEC
ViaBTC's ZEC mining guide lists three ways to move funds from a miner's pool account: Auto Withdrawal, Normal Transfer, and Inter-user Transfer. Auto Withdrawal is processed daily, while Normal Transfer can be initiated manually and carries a transaction fee.
According to ViaBTC's auto-withdrawal setup guide, checked on October 20, 2026:
- The published minimum auto-withdrawal amount for ZEC sent to an external on-chain address is 0.001 ZEC.
- Auto withdrawals are processed once daily between 10:00 and 18:00 (GMT+8), subject to the applicable payout conditions.
- Miners can instead withdraw to their own ViaBTC main or sub-account. The minimum payment threshold does not apply to this internal destination, provided the withdrawal amount is greater than zero.
- A saved on-chain payout address setting automatically becomes invalid after 90 consecutive days without a payment. This is a ViaBTC auto-withdrawal setting rule; it does not invalidate the underlying Zcash address on-chain.
To configure the destination, log in to ViaBTC and go to Assets → My Assets, select ZEC, and open the auto-withdrawal settings.
The ZEC mining guide and auto-withdrawal guide reviewed for this article do not individually list support for transparent, shielded, and Unified Addresses. This leaves address-format compatibility unconfirmed by those two documents; it does not establish that any particular format is unsupported.
Before relying on a shielded address or UA, confirm current acceptance and the supported payment type in the withdrawal interface or with ViaBTC support.
FAQ
Can I use a Unified Address to receive shielded ZEC from a mining pool?
Only if the pool can recognize the UA and construct a payment to a shielded receiver included in it. Under ZIP 316, a conforming sender must select the highest-priority receiver it supports. A transparent-only sender can pay a transparent receiver if one is included; without a compatible receiver, it cannot complete the payment.
Does receiving ZEC at a shielded address make the entire payout private?
Not necessarily. The shielded receiving address is protected on-chain, but transparent inputs remain public if the payment comes from transparent funds. Net transfers between value pools may also be visible. Privacy additionally depends on how the pool and receiving service handle account records and transaction information.
Does ViaBTC currently support shielded or Unified ZEC withdrawal addresses?
The two ViaBTC help articles reviewed here do not provide an address-format compatibility list. Confirm current support in the withdrawal interface or with ViaBTC support before relying on a shielded or Unified Address. For a UA, also confirm which payment type the pool supports.
Is my pool withdrawal necessarily funded by the block I helped find?
No. In an account-based pool, reward accounting and withdrawal are separate processes. ZIP 213 describes how a pool can fund a payout using ZEC it already holds. The relationship between mining rewards and payments depends on the pool's accounting and payout design.