Zcash now has a truly permissionless trading venue: THORChain has launched its ZEC liquidity pool, and for the first time the privacy coin can move across blockchains without a centralized exchange in the middle.
By David Chen | October 3, 2026
The Hook: Privacy Meets Cross-Chain Swaps
THORChain announced on October 2 that its Zcash (ZEC) liquidity pool is now live, following a network “churn” — the protocol’s regular process of rotating the nodes that run the network. Every THORChain node is now watching the Zcash blockchain, the project confirmed on X, calling it a moment where “Zcash now has a truly permissionless venue.”
Why should a regular investor care? THORChain is like a currency exchange booth that no company owns. It lets people swap coins across different blockchains directly from their own wallets, with no middleman holding the funds and no account required. Until now, trading ZEC across chains meant using a centralized exchange — handing over your coins, your identity, and your privacy. That option just got an alternative.
On-Chain Evidence: Months of Engineering Behind One Pool
The launch sounds simple, but the plumbing took most of the year to build. According to THORChain’s own protocol upgrade notes, the Zcash integration required:
- March 4 protocol upgrade — added Zcash-specific transaction handling and communication logic, plus ZEC price tracking inside the protocol’s built-in oracle
- March GitLab fix — corrected ZEC network-fee reporting that could inflate calculations by treating a flat fee like a per-byte rate
- September signing fix — resolved a subtle bug where nodes could disagree on transaction expiry times, producing mismatched signatures, by tying expiry to an agreed block height
- September 17 blog post — confirmed Zcash was next in line as chain launches resumed after a stability-focused pause
The network explorer now lists ZEC’s chain status as “OK” alongside Bitcoin, Ethereum, and the other networks THORChain tracks. RUNE, THORChain’s own token, serves as the settlement asset — every swap routes through it, which is why new chain listings historically matter for RUNE demand.
The Core Conflict: Shallow Liquidity and Unwanted Attention
Before anyone rushes to trade, THORChain itself issued a blunt warning: “Liquidity is shallow for now and will grow over time, so trade with caution in the early days.” The announcement gave no pool-depth figure and no firm date for when full trading activates — the pool going live is step one, with swaps switched on separately.
Shallow liquidity means big gaps between buy and sell prices. Think of a market stall with only a few items on display — a large order moves the price far more than it would at a stocked exchange. Early traders in new THORChain pools routinely face worse execution than on established venues.
The launch also lands amid renewed scrutiny. According to on-chain reporting, wallets linked to the September Bitget hack swapped roughly 6.3 million USD of ETH into Bitcoin through THORChain after the breach — part of an ongoing debate about whether permissionless cross-chain swaps should be able to refuse stolen funds. That debate does not block the Zcash launch, but it colors the environment THORChain is expanding in.
Market Implications: What This Means for You
For Zcash holders, the practical benefit is exit and entry options that do not require an account or identity verification — a natural fit for a privacy-focused coin. More venues for ZEC generally means more access, which can support liquidity over time.
For RUNE holders, each new chain routes more potential swap volume through the settlement asset. Zcash joins a growing list of supported chains, and historically, expansion announcements have coincided with renewed interest in the token.
For everyone else, the sensible move is patience. Wait for trading to actually activate, watch how the pool depth develops, and let the first wave of early traders discover the spreads. There is no prize for being first into a shallow pool.
The Verdict
THORChain’s Zcash pool is a genuine milestone for privacy-coin accessibility — the product of months of careful engineering rather than a rushed listing. But the protocol’s own caution about shallow liquidity deserves to be taken seriously, and the timing, amid hack-fund flows moving through the network, keeps the spotlight on the trade-offs of permissionless design. Watch for the trading activation announcement and the first week of pool depth data before treating this as a mature market.
The cryptocurrency market remains highly volatile. This article is for informational purposes only and does not constitute financial advice.
zec moving cross chain with zero kyc middleman, been waiting years for this. took them from the march upgrade to september bugfixes to get here
The expiry-block signing fix is the detail most people will skip. Mismatched node signatures would have turned those swaps into a support nightmare.
genuine question, does pool depth even work for ZEC here? privacy coins have historically had thin native liquidity outside the big exchanges
exactly my worry. the announcement gave zero depth figures and the team flat out said liquidity is shallow early on. i would wait a few weeks before pushing any size through it
checked the pool an hour after the churn finished, book was already six figures deep on the ZEC side. the day one depth worry looks overblown, at least for now
six figures on the ZEC side is nice until someone tests it with an actual seven figure swap and the slippage calc cries. still better than i expected for week one tho
depth will be rough for weeks since half the LPs just churned back in. but even a thin book beats the old option, which was a KYC desk holding your coins and your ID
the depth question answered itself within an hour of the churn finishing, six figures on the zec side. whether it survives week two without the early lp fleche is the actual test
first permissionless ZEC venue and it took a march protocol upgrade, a fee reporting fix AND a full churn to get here. respect to the THORChain devs
that gitlab fee fix mattered more than people realize. a flat fee treated as per byte was silently wrecking every calculation on that pool
a flat fee treated as per byte is such a classic silent killer, glad someone read the gitlab thread before everyone blamed the chain itself
the churn is the part everyone forgets. every LP had to pull and redeposit so the pool could relaunch clean. days of coordination just to list one asset
Until now trading ZEC across chains meant handing your coins and identity to a centralized exchange. This is the use case privacy coins have needed for years.
first permissionless route between zcash and other chains is a quiet milestone. shielded pool liquidity has been the missing piece forever
a privacy coin you can move cross chain without an exchange holding your id is the whole point of ZEC. churn logistics sound painful but this is the venue the coin needed for years
worth reading carefully: pool going live and swaps activating are separate steps. people will see the headline, try to swap ZEC today, then wonder why it fails
saved me a wasted lunch break honestly, was about to try a swap today. also explains why depth is thin, every LP had to churn out and back in
same, checked the pool before swapping anything. half the LPs still churning back in means slippage eats you before the fee does
^ this. saw three people in the tg complaining their swap failed because swaps are not even enabled yet. read the announcement people
guilty, had the tab open ready to swap before i read past the headline. pool live and swaps live being two separate toggles is gonna catch a lot of people this week
every node now watching the zcash chain means the expiry block signing finally matches across the network. that september fix was the actual unlock, the churn was ceremony
finally someone crediting the september fix. without matching expiry signatures the first big ZEC swap becomes a stuck transaction horror story
watching ZEC pool depth fill up over the next churn is the real signal. day one books are decoration
the fee bug is my favorite part of this launch. one flat fee read as per byte and the pool would have quoted nonsense rates from day one. whoever caught that gitlab thread earned their coffee
the scary version of that fee bug is nobody reads the gitlab thread and every zec swap gets quoted like a data heavy tx. fee reporting is where cross chain integrations quietly bleed out
the rune angle gets skipped in every headline about this. every zec swap routes through rune by design, so a busy zec pool is silent buy pressure on the settlement asset