I refreshed the chain explorer twice before I believed the status line. ZEC, marked OK, sitting next to Bitcoin and Ethereum like it had always belonged there. On October 2, 2026, THORChain finished a node churn, put a Zcash liquidity pool on the network, and told the market that trading would come after the pool, not with it. That order of events is the whole story, and it is easy to miss if you only read the victory lap.
A pool without a live swap path is a strange kind of opening. It is real infrastructure, not a teaser, and it is also not yet a place where you can casually move value. The network said every active node was watching the Zcash chain. It called the venue permissionless. Then it added the sentence that should sit on every trader’s screen for the first week: liquidity is shallow, and it will take time to deepen. If you have ever watched a new pair open on a thin book, you already know how that sentence ends when people ignore it.
What Actually Went Live on October 2
The launch was not a vague roadmap item. THORChain said the churn had completed and that every node was monitoring Zcash. The THORChain Zcash pool was described as live. Trading was explicitly framed as the next step, which separates two things people usually mash together: a liquidity venue existing, and users being able to route swaps through it.
That split matters. In a continuous liquidity pool model, the pool is the market. There is no order book waiting for a matching engine to wake up. Once swaps are enabled, price is a function of the assets sitting in the pool and the size of the trade hitting it. Turn the pool on before the routing is open, and you get a staging area. Turn routing on while the pool is still a puddle, and you get slippage that can look like a bug even when the math is working exactly as designed.
I have found that early cross-chain listings get narrated as if the asset just “arrived.” Zcash did not arrive in a weekend. The October pool sits on months of chain-specific work: UTXO handling, RPC logic, oracle pricing, fee math, and a signing fix that only landed because nodes were disagreeing with each other. The public post did not include a pool-depth figure. It did not give a clock time for trading. Both omissions are the practical headline.
Trading is the next step. Liquidity is shallow for now and will grow over time, so trade with caution in the early days.
THORChain, October 2, 2026
An active-node view on the network explorer listed ZEC as OK under chain information, alongside Bitcoin, Ethereum, and other networks already tracked by the displayed node. “OK” is a monitoring status, not a promise about depth, not a promise about quote quality, and not a promise that your outbound transaction will feel retail-smooth. Status lights are comforting. They are not a market.
Pool Live, Swaps Still Waiting
Think of it like a shop that has stocked the shelves and turned on the lights, then taped a note on the door. You can see the goods. You cannot check out yet. In protocol terms, the ZEC pool gives the network a live liquidity venue before swaps are switched on. That sequencing is deliberate. It lets nodes observe the chain, lets liquidity providers start positioning, and keeps the actual exchange function behind one more activation.
Perhaps the most interesting aspect is how plain the warning was. No soft language about “organic growth.” No implied market-maker backstop. Shallow, for now, caution in the early days. If you treat that as boilerplate, you will donate the spread to whoever is already sitting in the pool when the switch flips.
- Churn completed, so the active set is aligned on the new chain watch.
- Every node is monitoring Zcash, which is the precondition for consistent observation.
- The pool exists as a permissionless venue.
- Native trading remains a separate activation.
- No public depth number and no firm start time were attached to the October 2 post.
Why a Churn Is the Real Starting Gun
A churn is the network rotating its active node set. It sounds administrative. On a chain that settles other people’s assets, it is the moment the new rules become the rules everyone is actually running. You do not want half the signers watching Zcash and half still blind to it. You want the set that can pause a chain, report fees, and co-sign outbound transactions to be looking at the same tip.
That last point is not theoretical. Later in this piece the September signing bug shows what happens when nodes disagree about the Zcash tip. The churn is how the network tries to avoid a split brain at the exact moment a new asset goes from code to money.
How the Pool Model Actually Prices a Swap
THORChain’s own documentation frames the exchange as a set of continuous liquidity pools that hold native assets, not wrapped stand-ins. RUNE is the settlement asset. It sits in the pools and acts as the routing leg. A swap from chain A to chain B is, in simplified terms, a swap into RUNE and a swap out of RUNE. Zcash support means ZEC can occupy one side of that structure without being turned into an IOU on another chain first.
That native path is the product. It is also why the integration took so long. A wrapped token can inherit the host chain’s account model. A UTXO privacy coin cannot. You have to speak its fee rules, its expiry rules, its dust limits, and its notion of a confirmed inbound. Skip any of those and the pool can look solvent on a dashboard while the chain underneath is telling a different story.
Here is the trader’s version of the same idea. In a constant-product pool, a small trade barely moves the price. A trade that is large relative to reserves moves it a lot. If the ZEC side is thin, even a modest swap can print a terrible execution. The protocol is not “broken” when that happens. The pool is telling you the truth about its size.
Early-pool reality check: Depth unknown on day one Slippage scales with trade size RUNE is the routing leg Native ZEC is the point Caution is the listed feature, not a footnote
What “Permissionless Venue” Does and Does Not Mean
Permissionless, in this context, means you do not need an exchange account, a listing committee, or a withdrawal whitelist to interact with the pool once trading is on. It does not mean the network has no operators. It does not mean there is no way to pause a chain. It means the pause is aimed at solvency and liveness, not at curating who is allowed to swap.
That distinction became loud in the weeks before this launch, for reasons that have nothing to do with Zcash’s technology and everything to do with stolen funds moving across chains. I will get there. For the pool itself, permissionless is both the sales pitch and the risk label. Same sentence. Different readers hear different words.
The Months of Code Behind a One-Day Headline
On March 4, a protocol upgrade added chain-specific UTXO handling and RPC logic for Zcash. A separate change placed ZEC in the enshrined oracle, so price tracking lives inside protocol logic rather than as an off-to-the-side feed someone might forget to update. That is the unglamorous core of a listing. If nodes cannot agree on what a ZEC is worth inside the system, liquidity math drifts.
A March code change then corrected network-fee reporting and solvency calculations. The earlier approach could inflate gas tolerance because the full ZIP-317 fee was being treated like a per-byte rate during one solvency check. The fix changed how the transaction-size input was handled for ZEC. Dry? Yes. Also the difference between a pool that thinks it can afford an outbound and a pool that actually can.
If you have ever watched a bridge “support” an asset by wrapping it and hoping the price oracle behaves, this is the other path. Slower. More arguments in merge requests. Fewer surprises of the wrapped-token kind, and a fresh set of surprises that belong only to UTXO chains.
The September Signing Fix, in Plain Language
Development did not stop at fees. A September merge request documented signing inconsistencies caused when ZEC transaction expiry was calculated from different local chain tips. Different tips, different digests, nodes that should have agreed on a signature and did not. That is how a multi-party signer stalls.
The merged change tied transaction expiry to an agreed ZEC height at a fixed THORChain height, and it kept that value across retries and restarts. Periodic updates to the agreed height were routed through network-fee reports. Expired signing attempts were handled differently so a retry would not quietly recompute expiry from a newer local tip.
I keep coming back to this fix because it is the kind of bug that never shows up in a launch tweet. Two honest nodes, two slightly different views of the chain, one outbound that cannot collect enough signatures. Users experience that as “stuck.” Operators experience it as a weekend. The agreed-height rule is an attempt to make Zcash’s clock a shared fact instead of a local opinion.
- Nodes were deriving expiry from their own view of the Zcash tip.
- Those views diverged, so signing digests diverged.
- The fix pins expiry to an agreed height at a fixed network height.
- Retries must keep the same unsigned transaction data.
- Fee reports refresh the agreed height on a schedule, not on a whim.
From “Next in Line” to Nodes Actually Watching
On September 17, the project’s blog said Zcash was next in line for mainnet as chain launches resumed after a stretch focused on stability. Timing stayed conditional. That is the correct posture for a network that had just spent months arguing with its own fee math. Conditional, then churn, then a pool, then a public note that trading follows. The sequence is tighter than the September language, and still not a finished market.
Earlier node changes had already classified ZEC as a UTXO chain and added configuration for address validation, gas units, dust thresholds, block timing, coinbase parameters, and inbound requirements. None of that is user-facing. All of it is why a ZEC address on this network is not just an Ethereum address with a different ticker taped on.
| Stage | What changed | Why a trader should care |
| March upgrade | UTXO handling, RPC logic, oracle listing | Native price and chain logic, not a wrapper |
| March fee fix | ZIP-317 fee no longer treated as a per-byte rate | Solvency math closer to real outbound cost |
| September signing fix | Agreed ZEC height for expiry | Fewer stuck outbounds from split tips |
| September 17 note | Zcash named next, timing conditional | Launch was planned, not improvised that morning |
| October 2 | Churn, pool live, trading still next | Venue exists; execution does not, yet |
Shallow Liquidity Is Not a Vibe, It Is a Number You Do Not Have
The October 2 warning was aimed straight at opening-stage liquidity. No depth figure. No schedule. That combination should slow you down. A pool can be “live” with a few thousand dollars on one side and still print a status of OK. The first traders through a thin pool set the anecdote everyone else repeats. Sometimes that anecdote is a clean fill. Often it is a screenshot of 8% slippage on a size that would have been invisible on a major venue.
In my experience, the dangerous window is the first session after swaps flip on, when social feeds treat the listing as a destination and the pool is still a construction site. Size down. Split orders. Assume the quoted price is a suggestion until you have seen a few completed rounds. If you are providing liquidity rather than swapping, you are the exit liquidity for that first wave. That can be paid well. It can also be a donation to volatility.
A new pool does not owe you a fair price. It owes you the price its reserves can support. Those are not the same thing.
What to Watch Before You Touch the First Swap
You will not get a press release that says the pool is deep enough. You will get on-chain reserves, observed slippage, and whether outbounds are completing near the agreed height logic the September fix was built for. A few practical checks, none of which require insider access:
- Reserve size on both the ZEC side and the RUNE side, not just one.
- Whether small test swaps complete, or sit in signing.
- Fee estimates versus the ZIP-317 reality the March fix was meant to respect.
- How fast liquidity actually arrives after trading is announced, not before.
- Any chain pause. A pause is a solvency tool. It is also a signal.
None of this is advice to trade. It is a way to avoid confusing a status flag with a market structure. The protocol already said the quiet part out loud.
Zcash Is Not Just Another Ticker on the List
Zcash is a UTXO asset with optional shielded transfers and a fee schedule that does not behave like Bitcoin’s old per-byte habit. ZIP-317 is the tell. Treat that fee like a simple rate and your solvency check lies to you. The March correction existed because someone had already made that mistake in code.
Privacy coins also carry a social and compliance shadow that liquid staking tokens do not. A permissionless pool does not launder anything by itself. It also does not ask why you are swapping. That neutrality is the design. It is the same design critics point at when stolen assets move. Both descriptions can be accurate on the same day. Holding both in your head is more useful than picking a team in the replies.
There is a practical angle for liquidity providers too. Shielded and transparent flows do not present the same observability. Address validation, inbound requirements, and dust thresholds were added exactly because ZEC does not slot into an account-based template. If you are used to ERC-20 pool launches, recalibrate. The failure modes are older, and they are pickier.
The Freeze Debate Sitting Next to the Launch
The pool did not open in a quiet month. A major exchange said unauthorized transfers began on September 24 and later put the value moved to attacker-controlled addresses at about $387.5 million, after investigators folded Zcash and Tron activity into the total. The disclosed asset list included XRP, ETH, USDT, ZEC, USDC, XAUt, BNB, AVAX, and TRX. Outside firms were described as working with the exchange’s own security staff. Primary receiving addresses were published across several networks.
Reports around September 28 said a wallet linked to that attacker completed 27 swaps through THORChain, turning roughly 2,390 ETH into 75.2 BTC, about $6.3 million at the time. The exchange had asked the protocol to refuse transactions from linked addresses. The protocol refused a selective restriction. Emergency halt tools, it said, exist to protect network operations. They do not freeze a single address or a single swap.
An October 1 post laid the position out again. Node operators can pause a chain, or the whole protocol, when solvency is at risk. The same emergency system cannot pluck out one transaction. Major changes need operator adoption, with a two-thirds consensus threshold described for significant network moves. Read that next to the October 2 pool note and the tension is obvious. A new permissionless venue, days after a public argument about whether permissionless includes “please block this wallet.”
I am not interested in pretending that argument is settled. Selective freezes are how a lot of people want bridges to behave after a theft. They are also how a bridge becomes an unofficial compliance desk, with all the capture risk that implies. THORChain picked the second discomfort. Whether you like the pick depends on what you think the protocol is for. A routing utility, or a policy layer. It is telling the market it is the first.
The Earlier Bybit Episode Still Shapes the Reputation
This is not the first time the routing path has been the story. After the February 2025 Bybit theft, the FBI attributed roughly $1.5 billion in taken virtual assets to North Korea’s TraderTraitor activity and urged exchanges, bridges, RPC operators, DeFi services, and other firms to block identified addresses. Bybit’s chief executive later said 72% of about $900 million in converted assets had passed through THORChain. That figure was his, not a protocol estimate.
A separate look at activity during the early laundering window put trading volume near $2.91 billion and fee income near $3 million, citing on-chain analyst Yu Jin. Fees on flow of that kind are the awkward part of a volume-based model. The protocol earns when people swap. It does not, on current design, earn less because the swap is ugly.
The exchange in the September case has a recovery page listing attacker addresses across EVM networks, the XRP Ledger, Zcash, and Tron, plus a 5% bounty for eligible parties whose voluntary work directly leads to frozen or recovered funds. Zcash appearing on both a victim disclosure and a new pool launch is a coincidence of timing that social feeds will not treat as a coincidence. Worth separating the facts. Support for a chain is not endorsement of a theft. A pool that cannot selectively block is also not a place to expect a quiet recovery.
Two Risks, Easily Confused
One risk is market structure. Thin reserves, wide slippage, outbound delays while signing converges. That risk belongs to anyone who trades the first days.
The other risk is reputational and legal-adjacent. Privacy-coin flow plus a stated refusal to blacklist sits in a year when large thefts keep using cross-chain routes. You can believe the code is neutral and still expect counterparties, fiat ramps, and some liquidity providers to hesitate. Hesitation is a depth problem. Depth is the thing the October 2 post already said was missing.
Perhaps that loop is the real early-days story. Caution was requested because the pool is small. The pool may stay smaller, longer, because some capital does not want the headline. If that happens, the warning ages well.
Who This Pool Is Actually For
Not everyone staring at the tweet. Native ZEC in, native asset out, routed through RUNE, without a custodian in the middle, is a real product for people who already self-custody and already understand UTXO quirks. It is a poor product for anyone who wants a customer-support desk, a reversal button, or a tight spread on size.
Liquidity providers are the other audience, and the less romantic one. They warehouse inventory so swaps can clear. In a shallow pool they warehouse more price risk per dollar. Impermanent loss is not a slogan here. It is the bill for being early. If ZEC volatility spikes while RUNE moves the other way, the pool rebalances against you by design. Getting paid in fees only helps if volume shows up and you do not get run over first.
Node operators are the third group, and they already did the visible work. They churned. They are watching the chain. They hold the pause switch that cannot see individual wallets. If something in ZEC fee reporting or expiry drifts again, they are the ones who will notice before a dashboard does.
A Plain Way to Read the First Week
Ignore the adjective “live” until you can answer three questions. Is trading actually enabled, or is the pool still a staged venue? How large are reserves relative to the trade you want? Are outbounds completing, or are they gathering signatures against an expiry height?
If the answers are enabled, small, and slow, you are early in the way builders mean early, not in the way marketing means early. Builders mean unfinished. Marketing means advantageous. The October note sided with the builders, which is rarer than it should be.
Before a ZEC swap: reserves visible? trading flag on? test size completed? slippage acceptable? only then size up.What Would Make the Pool Boring, in a Good Way
Boring would look like this. Trading turns on. A few small swaps clear. Reserves climb without a single whale painting the price. Fee reporting stays consistent with ZIP-317. Signing uses the agreed height and retries do not rewrite expiry. No chain pause. No social thread about a stuck outbound that turns out to be two nodes on two tips.
That is a dull week, and it is the week this integration has been earning since March. Oracle listing, fee fix, signing fix, conditional mainnet note, churn, pool. The remaining step is the one users will judge the whole stack by, because users never see merge requests. They see whether their coins arrived.
I would rather the first public trading day be dull than viral. Viral, on a thin privacy-coin pool, usually means someone learned about slippage in public. Dull means the September clock fix held and the March solvency fix was not theoretical.
The Larger Bet Under the Ticker
Cross-chain venues keep expanding the asset list because that is how they stay relevant. Each new chain is a vote that native routing beats wrapped convenience. Zcash is a sharp test of that vote. The chain is old enough to have scars, private enough to attract both legitimate users and unwanted flow, and different enough in fee design that copy-paste Bitcoin logic already failed once in this codebase.
If the pool deepens and outbounds stay reliable, the integration becomes a template for the next awkward UTXO asset. If it stalls in shallow liquidity, or if signing quirks return, it becomes a case study in launching the venue before the market. Both outcomes teach more than the launch post can.
There is also a governance lesson hiding in the two-thirds threshold. The network can change, but not by tweet, and not by a victim’s request alone. Operator adoption is the gate. That is slow on purpose. It is also why a selective blacklist was never going to appear between September 28 and October 2. The design does not have that switch. Adding one would be a major change, not a customer-service reply.
A Few Misreadings Already Floating Around
First misreading: the pool means ZEC trading is open. The protocol separated those events in the same post. Keep them separate until a swap actually clears.
Second: OK on a node page means healthy liquidity. It means the node is watching the chain and the chain check is passing. Depth is a different field, and it was not in the announcement.
Third: a permissionless venue will screen stolen coins because the previous month was embarrassing. The October 1 post says the opposite. Pause for solvency. No selective removal of a transaction. You can dislike that and still quote it accurately.
Fourth: fees collected on suspect flow are proof the protocol directed the flow. Volume fees do not work that way. They are indifferent. Indifference is a criticism you can make. It is not the same criticism as conspiracy.
How I Would Explain It to Someone Who Missed the Thread
THORChain finished rotating its active nodes and turned on a Zcash pool. Every node is supposed to be watching that chain. You cannot treat it as a normal trading pair yet, because trading was called the next step, and the people running it already said the pool is thin. Under the hood, they spent the spring and summer teaching the protocol how Zcash fees and transaction expiry actually work, after the first versions got both wrong in subtle ways. In the same stretch, large theft-linked swaps moved through the network, and the network declined to blacklist addresses. So the launch is a technical milestone and a political one, even if the tweet only sounds like the first.
That is the version I would send a friend. No fireworks. A pool, a warning, and a stack of fixes that only matter if the first real swaps survive contact with the chain.
What Remains Unanswered on Purpose
Depth. Start time. How much RUNE will sit against ZEC once trading is more than a status word. Whether liquidity providers step in after the blacklist argument, or wait for a boring week of completed outbounds. Whether ZIP-317 reporting stays honest once real traffic hits fee estimation. Whether the agreed-height rule holds when Zcash blocks arrive faster or slower than a node’s local habit expects.
The announcement did not owe anyone those answers. It owed a clear line between pool and trading, and it drew that line. The rest is observation. Chain data will settle it faster than another thread will.
Until then, the grown-up read is the short one. The THORChain Zcash pool is up. Nodes are watching. Swaps are the next switch, not this one. Liquidity is a puddle until it is not. Trade like the puddle is real, because the people who built it already told you it is.
