THORChain's native Zcash integration went live in late April 2026 — ahead of its Monero counterpart, which followed in May. For the first time, users can swap BTC directly to ZEC on a decentralized protocol without wrapped tokens, bridges, or centralized exchanges.
One catch that matters to most ZEC users: the initial integration supports transparent addresses only. No z-addresses, no u-addresses, no shielded pool. If you're buying ZEC specifically for privacy, the THORChain workflow lands your funds at a transparent t-address, and you have to shield them yourself in a second on-chain step — which creates a visible link between your transparent receipt and your shielded balance.
💡 Want shielded ZEC delivered straight to your unified (u-address) wallet? Superswap.cx supports u-address destinations natively. Paste your u-address, send your BTC, receive shielded ZEC in 5–30 minutes. No transparent intermediary step. No KYC.
Zcash supports two transaction types. Transparent transactions use t-addresses (starting with "t1") and work like Bitcoin — sender, receiver, and amount are visible on-chain. Shielded transactions use z-addresses or modern unified u-addresses, and rely on zk-SNARKs cryptography to hide all three from public view.
About 30 percent of total ZEC supply now sits in the shielded pool — up from roughly 8 percent in prior years. The shielded pool is where the privacy actually lives. Transparent ZEC is, for privacy purposes, equivalent to Bitcoin.
THORChain's nodes validate cross-chain transactions by inspecting them on the source chain. For transparent ZEC, this is straightforward: nodes can read the transaction the same way they read a Bitcoin transaction. For shielded ZEC, it's not: the transaction is encrypted by zero-knowledge proofs. Validating it without breaking the privacy guarantee requires either trust assumptions or significantly more complex verification infrastructure than the protocol currently has. The Zcash chain client, developed by contributor StarSquid, prioritized a transparent-only launch for safer deployment. Shielded-address support is on the roadmap with no published date.
If you bought ZEC because you wanted the privacy of the shielded pool, the THORChain workflow doesn't deliver that directly. Here's what actually happens:
For users with sophisticated threat models, this is meaningfully worse than receiving ZEC directly into the shielded pool. The on-chain link between the transparent receipt and the shielded send is a known correlation vector. Privacy researchers have published techniques for analyzing shielding patterns at scale.
This isn't a critique of THORChain — the technical reason for transparent-only is real. It's a clarification of what the integration delivers versus what users may assume "native ZEC support" means.
The mechanics, step by step:
The ZEC pool, like the XMR pool, was seeded with limited treasury-funded liquidity. Practically:
Protocol-Owned Liquidity in THORChain v3.18 is designed to add capital to newer pools (including ZEC) over time — estimated at around $200,000 per month at current network revenue. Slippage should improve materially through the second half of 2026.
The THORChain integration arrives at a moment of unusually high attention on Zcash. Worth knowing:
Demand for ZEC swap infrastructure is at a multi-year high. THORChain's transparent-only integration meets some of that demand. The privacy-focused share — users who specifically want shielded receipts — needs a different tool.
For most users buying ZEC in 2026, the better choice is an instant non-custodial swap service that supports shielded addresses directly. The use cases:
For broader context on no-KYC Zcash access, see our Zcash exchange no-KYC guide. For the technical primer on why shielded matters, see Zcash shielded transactions explained. For the Monero side of THORChain's privacy-coin push, see the THORChain Monero swap guide.
No, not at launch. THORChain's initial Zcash integration supports only transparent (t-address) ZEC. Shielded addresses — both legacy z-addresses and modern unified u-addresses — are not part of the first mainnet release. The reason is technical: validating shielded transactions on an external protocol would require either trust assumptions or a more complex zero-knowledge verification setup. The Zcash chain client, developed by contributor StarSquid, prioritized a transparent-only launch for safer deployment. Shielded support is on the follow-up roadmap but has no published date as of mid-2026.
Transparent ZEC (t-addresses) works like Bitcoin — sender, receiver, and amount are visible on the blockchain. Shielded ZEC (z-addresses or unified u-addresses) uses zk-SNARKs cryptography to hide all three. About 30 percent of total ZEC supply is now in the shielded pool, up from 8 percent in prior years. If you're swapping into ZEC specifically for privacy reasons, transparent-only ZEC from THORChain doesn't give you the privacy benefit until you shield those funds inside your wallet — which is an extra step that creates an on-chain link between the transparent receipt and the shielded balance.
Set up a Zcash wallet that supports transparent addresses (Zashi, YWallet, or Zecwallet). Get your t-address — it starts with "t1". Open a THORChain interface (ASGARDEX, Vultisig, or THORSwap) with your Bitcoin wallet connected. Select BTC to ZEC, paste your t-address as the destination, review the rate (watch slippage carefully due to thin initial liquidity), and confirm. The swap routes BTC → RUNE → ZEC internally and ZEC arrives at your t-address typically within 15 to 45 minutes. If you want the funds shielded, you'll need to send them from your t-address to a z-address or u-address inside your wallet as a second step.
The cryptography is sound — THORChain uses Threshold Signature Scheme (TSS) and the protocol is genuinely decentralized. The honest tradeoffs are the same as the Monero integration: initial liquidity is thin (treasury-seeded), the protocol has a history of multi-million-dollar exploits prior to 2022, and the network has been under regulatory scrutiny after processing exploit-related funds in 2026. The Zcash chain client itself is new code. For small swaps from a non-custodial wallet, it works. For larger amounts, the slippage from limited pool depth is often a bigger practical concern than security. Established no-KYC instant swap services are a lower-friction alternative.
Any Zcash wallet that supports transparent (t-address) receiving works as the destination for a THORChain swap. Zashi (Electric Coin Co.'s official mobile wallet) handles both transparent and shielded. YWallet is a more advanced multi-platform option with strong shielded support. Zecwallet is a full-node desktop wallet. On the THORChain side, you'll separately need ASGARDEX (desktop) or Vultisig (multi-platform) for the BTC wallet that initiates the swap. The two wallets don't talk to each other — you copy your ZEC t-address into the THORChain interface manually.
No published date. THORChain's roadmap notes shielded-address support as a follow-up to the transparent-only launch but doesn't commit to a timeline. The technical hurdle is non-trivial: shielded transactions require zero-knowledge proof verification, which adds complexity to the cross-chain validation that THORChain nodes perform. The most plausible window is late 2026 to 2027, conditional on the initial transparent integration proving stable in production. Until then, users who want shielded ZEC need to swap into transparent ZEC and shield manually in-wallet, or use a service that supports shielded addresses directly.
Use THORChain if you want protocol-level decentralization, you're comfortable with non-custodial wallet setup, and transparent ZEC is acceptable for your use case. Use Superswap.cx if you want to receive ZEC directly at a unified (u-address) or shielded address in one step, want a simpler workflow without separate wallet integration, or your swap size exceeds the THORChain pool's depth. Superswap supports u-addresses natively — the address that pulls funds from the shielded pool — which means privacy-focused users get the shielded benefit without the extra transparent-to-shielded shielding hop.
U-address support · No KYC · No transparent intermediate · 5–30 min settlement
Start a No-KYC ZEC Swap →