Hi all,
If you’ve tried to send ZEC to Binance lately, you may have run into this. Binance gives every ZEC user a deposit address that starts with tex1, and a lot of wallets reject it as “invalid address”. THORChain’s ZEC inbound address is often a TEX address too, so the same wallets can’t swap ZEC through THORChain either. The address is fine. The wallet just doesn’t support TEX addresses (ZIP 320) yet.
I’ve spent the last few weeks reading wallet code and filing issues, so here’s where things stand today (18 Nov). It comes from code and release notes, not from sending real funds out of every wallet, so please correct me if I’ve got one wrong.
Wallets that can send to a TEX address
Zodl, Zingo, Zkool, Edge, Unstoppable, Zallet, Gem, Vultisig, OneKey, KeepKey, Coin Wallet, Vizor, Zafu, Noir, Zapp, ZChat and Laurel.
One thing worth knowing: Zodl can pay a TEX address from a shielded balance (it does the two steps for you), but not from a Keystone or Ledger account yet.
Wallets that can’t yet (each has an open issue)
- Cake Wallet: cake-tech/cake_wallet#3871
- Brave Wallet: brave/brave-browser#61975
- Ledger Live: LedgerHQ/ledger-live#25091
- Trezor: trezor/trezor-firmware#4581 and trezor/trezor-suite#35232
- Keystone: KeystoneHQ/keystone3-firmware#2313
- ShapeShift: the fix is upstream, in christsim/multicoin-address-validator#20
- SSP Wallet: already has a fix in review (RunOnFlux/ssp-wallet#770). That one came together in a day, so thanks to their team.
What’s been fixed so far
- Zebra now shows a TEX address as
tex1…instead of itst1…form (ZcashFoundation/zebra#11880), and onnextit rejects a TEX address with the wrong kind of checksum (#12360, from #12254). - zecblock can now look up a TEX address (Kenbak/zecblock#284).
- Zkool’s scanner now finds the temporary addresses it uses when paying a TEX address from shielded funds (hhanh00/zkool2#1639).
- blockchain_utils, a Dart library, now rejects TEX addresses that carry the wrong amount of data. Mohsen fixed it within an hour of the report (mrtnetwork/blockchain_utils#19).
Two edge cases are now settled
ZIP 320 didn’t spell out two cases, and the ZIP 320 Owners have now decided both (zcash/zips#1468, with the ZIP change in zcash/zips#1469):
- An address written in all capitals (
TEX1…, which QR codes often use) must be accepted. Mixed case is still invalid. - Extra padding at the end of the encoded data must be rejected.
zcash_address and Zebra don’t handle either one yet (zcash/librustzcash#3306 and #3223, ZcashFoundation/zebra#12517). If your wallet decodes TEX addresses with its own code, it’s worth checking both.
If you build a wallet or an exchange
I put every bad address that caught a real bug this year into one test file, with the network each one should be checked on. It’s MIT and runs on plain Python: GitHub - cryppit/zcash-tex-vectors: ZIP 320 TEX address test vectors, a reference codec and an integrator checklist. · GitHub
The same invalid cases are proposed for zcash-test-vectors in zcash/zcash-test-vectors#139. The ones that tripped up real code were a Bech32 checksum where Bech32m is required, a 19- or 21-byte payload, an extra padding group, and a valid TEX address for the wrong network.
I’ve also asked several exchanges and closed-source wallets directly. None has told me it can send to TEX yet. If you work on a wallet or exchange that isn’t listed here, a quick reply saying whether it can pay a tex1 address would help a lot of people.
Disclosure: I maintain that test file and filed most of the issues above. This TEX work is part of our retro grant application (t/58901).