How Unified Addresses Work in Zcash
A Unified Address lets you share a single Zcash address while remaining compatible with multiple receiver types. Instead of asking which address format someone supports, the sender's wallet automatically selects the best receiver that both wallets understand.
TL;DR
A Unified Address lets you share a single Zcash address while remaining compatible with multiple receiver types. Instead of asking which address format someone supports, the sender's wallet automatically selects the best receiver that both wallets understand.
Before Unified Addresses, receiving ZEC could be surprisingly confusing.
Zcash has supported multiple address types throughout its history, including transparent addresses and several generations of shielded addresses such as Sapling and Orchard. Each address type has its own encoding and capabilities. As the protocol evolved, users often needed to know which type of address another wallet supported before sharing an address.
This created unnecessary friction.
The idea behind Unified Addresses
A Unified Address (UA) bundles multiple receivers into a single address encoding.
Rather than maintaining separate addresses for different receiver types, you only need to share one Unified Address.
When someone wants to send you ZEC, their wallet parses the Unified Address and determines which receiver types it contains. It then selects the most preferred receiver that it supports, following the rules defined in ZIP 316.
This means users no longer need to ask questions like:
- "Does your wallet support Orchard?"
- "Should I send to your Sapling address instead?"
- "Can you give me your transparent address?"
The wallet handles that decision automatically.
Why this matters
Unified Addresses improve interoperability across the Zcash ecosystem.
As new shielded protocols are introduced, wallets can continue exchanging payments without forcing users to manage multiple address formats or understand the technical differences between receiver types.
From a user experience perspective, this is a significant improvement:
- One address to share.
- Less confusion.
- Better compatibility between wallets.
- Easier adoption of newer protocol upgrades.
Importantly, Unified Addresses do not introduce a new cryptographic privacy mechanism. The underlying receivers (such as Orchard or Sapling) still provide the privacy properties. A Unified Address is simply a standardized way of packaging multiple receivers into a single address that wallets can interpret consistently.
Final thoughts
Unified Addresses are a good example of protocol design focused on usability.
The underlying cryptography remains just as sophisticated, but users no longer need to think about which address type to provide. By moving receiver selection into wallet software, Zcash reduces friction while maintaining compatibility across different generations of the protocol.