Skip to main content
LI.FI offers Zcash support with 2 integrated bridges and interoperability between Zcash and 16 chains.
For technical implementation details, see the Zcash Providers page. For the full list of supported chains, see Chain Overview.

​
Bridges

LI.FI integrates 2 bridges for Zcash connectivity: NearIntents, Unit
  • NearIntents: Intent-based routing between Zcash and 15 chains, including Ethereum, Solana, Bitcoin, Tron, Stellar, and major L2s. NearIntents is the only bridge that pays out to a shielded unified address.
  • Unit: Native ZEC in both directions between Zcash and Hyperliquid, to and from transparent addresses only. The minimum transfer is 0.07 ZEC.
Zcash works as a source chain and as a destination chain. Every pair routes in both directions, with one exception: Stellar is a destination only. LI.FI can bridge ZEC to Stellar, but not from Stellar to Zcash.

​
DEXs

LI.FI integrates no DEX on Zcash. Zcash carries one asset, native ZEC, so there is no same-chain swap to route. Every Zcash route is a bridge.

​
Key Features

​
Shielded payouts to unified addresses

ZEC can be received into a shielded balance. When Zcash is the destination, toAddress accepts a unified (u1...) address that carries an Orchard receiver, and the payout goes to that Orchard receiver. Only NearIntents pays out to a unified address, so a Hyperliquid to Zcash transfer through Unit needs a transparent toAddress.

​
Transparent senders

When Zcash is the source, fromAddress must be a transparent address: t1 (pay-to-public-key-hash) or t3 (pay-to-script-hash). LI.FI builds the Zcash transaction from transparent UTXOs, and a transparent transaction cannot spend shielded funds. Transparent addresses are also accepted as toAddress, on both bridges.

​
Refused addresses

LI.FI refuses these Zcash addresses with a validation error that names the accepted forms:
  • A Sapling (zs1...) address. Sapling is deprecated on Zcash, and no integrated bridge accepts one.
  • A unified address without an Orchard receiver. A bridge would pay its transparent receiver instead, so the payout would not be shielded.
  • A unified address with a receiver type other than transparent, Sapling or Orchard.
  • A unified address as fromAddress.

​
ZIP-317 fees

Zcash has no fee market. The network fee follows the ZIP-317 formula and depends only on the shape of the transaction, so there is no fee rate to bid and no way to pay for faster confirmation. The network minimum is 10,000 zatoshi (0.0001 ZEC).

​
Multiple sender addresses

fromAddress accepts a single transparent address or a semicolon-separated list. LI.FI pools the UTXOs of every address in the list and returns the change to the address that contributed the most. Extended public keys (xpub) are not supported on Zcash.

​
On-chain tracking memo

Every Zcash transaction LI.FI builds carries a LI.FI tracking memo in an OP_RETURN output. /status reads that memo back from the chain, so a transfer stays trackable from the transaction hash alone.

​
Unsigned transaction artifact

Zcash uses the ZIP-243 signature hash, which no Bitcoin PSBT library can produce. LI.FI therefore returns a structured unsigned transaction rather than a PSBT. See Executing a transaction.

​
Availability

Zcash support is available on the LI.FI API. Zcash routing runs on the public Zcash mainnet only.
The LI.FI SDK and the LI.FI Widget do not support Zcash. Integrate Zcash through the API.

​
Integration Options

LI.FI’s Zcash support is available through: