Decoded from scratch
Unified addresses are decoded per ZIP 316, including the F4Jumble step, and tested on the official test vectors. TEX addresses follow ZIP 320.
✓ Offline · nothing is looked up or sent
Sending ZEC? Check the address first.
Zcash has several kinds of address, and not every wallet can pay every kind. Paste one to see whether a transparent-only or a shielded wallet can send to it, what to do next, and which refund the Omni bridge could make to it. It also catches typos before they cost you.
Try one
How an answer readsExamples
tex1s2rt…khdgteTEX · valid
This is a TEX address, so send from a transparent balance.
From a transparent-only wallet
From a shielded wallet
Omni refund: transparent, sent with near-cli
Check this address →
tex1s2rt…khdgtfTypo
Don't send: a character in this address is wrong.
It fails its built-in check. Copy it again from the source.
Check this address →
Every kind of Zcash address
The prefix tells you the kind; the checksum tells you whether it was copied right. This is what the check answers for each.
Starts with
What it is
Transparent-only wallet
Shielded wallet
As an Omni refund address
t1 t3
TransparentPublic, like a Bitcoin address
✓ Yes
✓ Yes, but the amount and address become public
Transparent refund (near-cli)
tex1
TEXTransparent-only, ZIP 320; used by some exchanges
✓ If your wallet accepts TEX
✕ Only from transparent funds
Transparent refund (near-cli)
u1
Unified, with a transparent receiverOne address holding several receivers, ZIP 316
✓ If your wallet reads unified addresses
✓ Pays the Orchard or Sapling receiver
Transparent, or shielded if it has an Orchard receiver
u1
Unified, shielded onlyNo transparent receiver inside
✕ Ask for a t-address
✓ Yes
Shielded only, if it has an Orchard receiver
zs1
SaplingThe older shielded pool
✕ Ask for a t-address
✓ If your wallet supports Sapling
Don't use: the bridge can't pay it
zc
SproutClosed to new funds since 2020, ZIP 211
✕ Don't send
✕ Don't send
Don't use
Testnet addresses (tm, t2, textest1, utest1, ztestsapling1) are recognised and flagged: real ZEC sent to them is lost. Newer Revision 2 unified addresses are recognised but not yet read, so the check tells you to let your wallet decide.
On the Omni bridge
Which refund an address can take
A ZEC deposit the bridge never credits can be refunded to the refund address its sender named. The Zcash connector pays only two kinds of receiver, so the address decides which refund is possible.
Check a stuck deposit →-
Shielded refund
To an Orchard receiver. bridge-cli builds it, and it is the default. Since NU6.3 it lands in the Ironwood pool, where your wallet reads it like any shielded note.
-
Transparent refund
To a t-address, a TEX address or a unified address's transparent receiver. near-cli can send the call.
-
Neither
A Sapling address, or a unified address with only a Sapling receiver. A refund to it could never be executed, so don't name it as a refund address.
What it catches before you send
- A typoEvery Zcash address carries a checksum. One wrong or missing character fails it, and the check says don't send.
- Shielded money to a TEX addressA TEX address must be paid from transparent funds. A shielded wallet has to move the ZEC to a transparent address first.
- A shielded address for a transparent walletA transparent-only wallet can't pay a Sapling address or a shielded-only unified address. Ask for a t-address.
- A testnet or Sprout addressTestnet addresses take no real ZEC, and Sprout has accepted no new funds since 2020.
- Not a Zcash address at allA Bitcoin or Ethereum address pasted by mistake is rejected, not guessed at.
Offline and private
The address is read in your browser. Nothing is looked up or sent anywhere, so the check works with no connection and nobody learns which address you checked.
Also in your terminal
The same check runs from the command line, with the same words:
pnpm zec-refund <a Zcash address>