Zcash unified addresses (u1) explained
A unified address is a single Zcash address, starting with u1, that bundles several receivers: a shielded one (Orchard-type, now used by the Ironwood pool), optionally a Sapling one and optionally a transparent one. The sender's wallet automatically pays the most private receiver it supports, so you can share one address with everyone.
Before 2022 Zcash users had to juggle separate transparent and shielded addresses and explain to every sender which one to use. Unified addresses, defined in ZIP 316 and introduced with the NU5 upgrade on 31 May 2022, fixed that. Today almost every shielded wallet shows you a u1... address by default.
What is inside a unified address
A unified address is a container. Each item inside it is a receiver for one pool:
| Receiver | Pool it pays | Private? |
|---|---|---|
| Orchard-type receiver | Ironwood since 28 July 2026 (Orchard before that) | Yes |
| Sapling receiver | Sapling | Yes |
| Transparent receiver (P2PKH or P2SH) | Transparent | No |
ZIP 316 requires every unified address to contain at least one shielded receiver. The items are encoded with Bech32m and scrambled with a step called F4Jumble, so that changing a few characters breaks the whole address. That is also why u1 addresses are long: you should always copy and paste them, or scan a QR code, and check the first and last characters.
How sending to a u1 address works
When you pay a unified address, your wallet reads the receivers it understands and chooses the most private one. A modern Ironwood-ready wallet pays the shielded receiver. An older wallet that understands only Sapling pays the Sapling receiver. A wallet that only knows transparent ZEC can pay only if a transparent receiver is included, and that payment is public.
Some wallets now create shielded-only unified addresses with no transparent receiver. Zashi (now Zodl) introduced these in May 2025. They are better for privacy but cannot be paid by transparent-only wallets or most exchanges.
Did Ironwood change my address?
No. Ironwood uses the same receiver structure as Orchard, so existing u1 addresses did not change when NU6.3 went live on 28 July 2026 (Zodl, Jul 2026; The Block, 28 Jul 2026). Funds sent to your u1 address by an Ironwood-ready wallet land in the Ironwood pool. What you may need to do is move older funds out of Orchard; see Orchard to Ironwood migration.
Many addresses, one wallet
Shielded wallets can generate many different-looking unified addresses from the same seed (called diversified addresses). They all belong to your wallet, and outsiders cannot tell they are linked. Some wallets give you a fresh one each time you tap "receive". Using a different address for each payer is a simple privacy habit. Transparent receivers are different: reusing one links all its payments together, which is why Zkool rotates transparent addresses.
TEX addresses (tex1)
A TEX address (ZIP 320, starting tex1) is a transparent address written in a different format. It tells the sender's wallet: "pay me only from transparent funds". It was created for Binance's deposit rules in 2024. If you pay a TEX address from shielded funds, your wallet must first move the amount to a one-time transparent address and then pay the TEX address, so it takes two transactions and two fees. Zingo! supports this. Wallets without TEX support may refuse the address.
Coming next: zu and tu prefixes
A draft revision of the unified address standard (ZIP 316 Revision 2, reviewed as ZIP 1206) proposes new prefixes: zu for shielded-only addresses and tu for addresses that include a transparent receiver. It was still in review in 2026 and is not deployed. When it is, the prefix alone will tell senders whether a transparent payment is possible.
Exchanges and unified addresses
- Gemini added withdrawals to unified addresses in August 2025 and routed them to Orchard from November 2025. Its behaviour after Ironwood is not confirmed.
- Coinbase withdraws to transparent addresses only, though it accepts deposits from shielded addresses.
- Exchanges using TEX deposit addresses need transparent funds, as explained above.
If an exchange rejects your u1 address, ask your wallet for a transparent receiving address, withdraw, then shield. See how to shield ZEC.
Unified viewing keys
ZIP 316 also defines unified viewing keys (uview... for full and uivk... for incoming), which let someone see a wallet's activity without being able to spend. Read Zcash viewing keys before sharing one: they cannot be revoked.
Quick safety checks
- Never type a u1 address by hand. Copy, paste, then compare the first and last six characters.
- Beware clipboard malware that swaps addresses. Re-check after pasting.
- Use our address validator to confirm an address is well formed before sending a large amount.
- Send a small test payment first when using a new address.
Frequently asked questions
Why is my Zcash address so long?
A unified address bundles several receivers and adds error-detection, so it is much longer than a Bitcoin address. Always copy and paste or scan it, never type it.
Do I need a new address after Ironwood?
No. Ironwood uses the same receiver structure as Orchard, so existing u1 addresses keep working. Older Orchard funds may need migrating, which your wallet guides you through.
Can an exchange send to my u1 address?
Some can, such as Gemini. Others, including Coinbase, only withdraw to transparent addresses. Use a transparent receiving address for those, then shield the funds in your wallet.
What is the difference between u1 and tex1?
A u1 address can receive shielded funds. A tex1 address is transparent and must be paid from transparent funds, so a shielded wallet needs two transactions to pay it.