THORChain launches Zcash pool, trading comes next
The cross-chain protocol activated its ZEC pool on Oct. 2 after a full node churn, with trading to follow as liquidity builds.
Key takeaways
- ZEC pool live Oct. 2. THORChain activated its Zcash liquidity pool on Oct. 2, 2026 after a full node churn.
- Trading not yet active. Native ZEC trading is the next step, with no official launch date announced.
- Early liquidity shallow. THORChain warned ZEC pool liquidity is limited at launch and will grow over time.
What happened
On Oct. 2, 2026, cross-chain decentralized exchange protocol THORChain launched its Zcash (ZEC) liquidity pool, following a full network node churn that updated all active nodes to monitor the Zcash chain. The protocol confirmed that native ZEC user trading is the next step in the integration, separate from the pool launch. THORChain warned that pool liquidity is shallow at launch and will increase over time, advising traders to use caution during early activity. No specific pool depth figure or firm trading start date was shared in the Oct. 2 announcement.
Why it matters
The Zcash integration adds a privacy-focused asset to THORChain's supported chain list, which already includes Bitcoin and Ethereum. The launch follows months of protocol development work tailored to Zcash's UTXO design, including custom UTXO handling, RPC logic, native ZEC price tracking via the protocol's oracle system, and fixes for network-fee reporting and cross-node signing consistency. The integration also arrives as THORChain faces increased scrutiny over its role in routing funds linked to the recent Bitget crypto hack.
What is still unclear
- No firm start date for native ZEC trading or public pool depth figure has been shared by THORChain as of the Oct. 2 announcement.
Questions readers ask
When will native ZEC trading start on THORChain?
THORChain has not shared a firm start date for native ZEC trading, only confirming it is the next step after the pool launch.
Did THORChain block Bitget hack-related addresses?
THORChain declined Bitget's request to block attacker-linked addresses, as its emergency systems can only pause entire chains or the full protocol, not individual addresses or transactions.
What development work was required for Zcash integration?
The integration required custom UTXO handling, RPC logic, oracle support for ZEC price tracking, and fixes for fee reporting and cross-node signing consistency tailored to Zcash's design.