TLDR
- THORChain activated its Zcash (ZEC) liquidity pool on October 2 following a complete network node churn process.
- Every active node across the network now tracks the Zcash blockchain, with native swap functionality planned as the immediate next milestone.
- The decentralized exchange cautioned users that pool depth remains limited in these initial stages and recommended careful trading.
- The ZEC integration required extensive development work spanning months, including UTXO management upgrades, RPC infrastructure, and oracle price feed implementation.
- The rollout occurs while THORChain continues addressing criticism regarding Bitget breach-related assets that transited its protocol.
The decentralized liquidity protocol THORChain has activated support for its Zcash pool. The milestone was announced October 2 after the platform successfully executed a comprehensive node churn across its validator network.
All operational nodes within the THORChain infrastructure are now actively observing and monitoring the Zcash blockchain. While actual trading functionality has not yet commenced, the protocol confirmed this represents the immediate next phase.
THORChain’s announcement clearly distinguished between these implementation stages. Pool activation and the enablement of user-facing swap capabilities are intentionally separate deployment steps.
Pool Depth Limited During Launch Phase
The protocol issued a warning to potential users regarding current pool conditions. THORChain emphasized that available liquidity remains limited at this stage and will expand gradually.
Traders were urged to exercise prudence when interacting with ZEC pools during this initial period. The October 2 announcement did not specify exact liquidity metrics or provide a concrete timeline for trading activation.
Current monitoring tools tracking THORChain’s validator infrastructure show ZEC listed with normal operational status. The privacy coin now appears alongside established chains like Bitcoin and Ethereum in the network’s supported asset roster.
Lengthy Technical Preparation Preceded Launch
Zcash integration represents the culmination of significant development effort. THORChain’s March 4 protocol enhancement introduced specialized UTXO processing and RPC infrastructure tailored for ZEC compatibility.
The same upgrade integrated Zcash into THORChain’s oracle infrastructure. This integration enabled the network to natively track and reference ZEC pricing data.
Subsequent GitLab patches resolved a ZEC network fee calculation issue. Engineers identified that earlier code versions could miscalculate gas tolerance parameters during specific solvency verification procedures.
Development activity continued through September. A THORNode merge addressed signature inconsistencies arising when different nodes calculated transaction expiration times based on varying local blockchain tip heights.
The resolution standardized transaction expiry calculations to a consensus ZEC block height. This modification ensured signature data remained uniform across the validator network during transaction retry attempts and node restarts.
On September 17, THORChain confirmed Zcash as the next chain scheduled for mainnet deployment. This announcement followed an operational period where the project prioritized network stability improvements over expanding chain coverage.
Zcash’s underlying UTXO architecture necessitated specialized configuration. THORChain required precise parameters for address verification protocols, gas measurement units, dust transaction thresholds, block generation timing, and coinbase maturity rules before deployment could proceed.
The pool’s activation coincides with intensified scrutiny of THORChain’s function in facilitating stolen asset movements. Bitget publicly revealed a security breach beginning September 24, subsequently updating the total value transferred to attacker-controlled addresses to approximately $387.5 million.
According to Bitget’s disclosure, the total encompassed both Zcash and Tron-based activity traced by security researchers. The exchange enumerated impacted assets including XRP, ETH, USDT, ZEC, USDC, XAUt, BNB, AVAX, and TRX.
Blockchain analysis suggests a wallet associated with the Bitget attacker executed 27 separate swaps via THORChain’s infrastructure. These transactions exchanged approximately 2,390 ETH for 75.2 BTC, representing roughly $6.3 million in value at execution.
Bitget formally requested that THORChain block transactions originating from attacker-associated addresses. THORChain refused, clarifying that its emergency mechanisms can halt an entire chain or the complete protocol but lack the capability to freeze individual addresses or specific transactions.
THORChain articulated its governance structure in an October 1 blog post. The protocol noted that fundamental architectural modifications require approval from two-thirds of participating node operators.
This represents a recurring challenge for THORChain. During February 2025’s Bybit security incident, Bybit’s chief executive stated that 72% of approximately $900 million in converted stolen assets flowed through THORChain’s swap infrastructure.
Bitget’s asset recovery portal currently displays attacker wallet addresses across multiple blockchain networks, including Zcash. The exchange maintains a 5% bounty reward for information directly contributing to asset freezing or recovery.
At present, THORChain’s Zcash pool remains operational with monitoring active, though native trading functionality has not yet launched.
Get 3 Free Stock Ebooks
Discover top-performing stocks in AI, Crypto, and Technology with expert analysis.
- Top 10 AI Stocks - Leading AI companies
- Top 10 Crypto Stocks - Blockchain leaders
- Top 10 Tech Stocks - Tech giants
