Search
Search projects, tokens and protocols by name or address
Pin a project to keep it here. Saved only in this browser.
Zcash via NEAR IntentsZcash via NEAR Intents
This route has no Ethereum contracts. Real-time monitoring is not supported.
About
A shielded ledger round trip: Zodl swaps Ethereum funds into shielded ZEC and back through NEAR Intents, which custodies the Ethereum side.
About
A shielded ledger round trip: Zodl swaps Ethereum funds into shielded ZEC and back through NEAR Intents, which custodies the Ethereum side.
Zodl, a Zcash wallet, lets users move funds from one Ethereum address to a new one through Zcash’s shielded pool, which hides the path. Its swap screen uses NEAR Intents to turn Ethereum assets into shielded ZEC and, later, ZEC back into Ethereum assets. Both Ethereum transfers and every swap on NEAR are public.
Users trust the NEAR Intents operatorAn operator is the entity charged with managing a rollup and progressing its state. A rollup operator can be a centralized sequencer, proposer, prover, challenger, pauser of admin that is able to perform upgrades., which holds the Ethereum funds in a custodial bridgeA message-passing protocol between two blockchains. At its most basic, a token bridge consists of a smart contract which can escrow funds on one side of the bridge, and instruct the release or minting of corresponding assets on the other side, but bridges could also support arbitrary messages. How these instructions are validated is a critical factor in assessing the trust assumptions of a bridge., screens every swap and can freeze balances. Two NEAR multisigs upgrade the contracts instantly, and NEAR’s MPC networkA constellation of nodes (peers) that communicate via a peer-to-peer protocol, for example, in propagating transactions and blocks to other nodes. signs every Zcash payout. Leaving needs the operator, which runs the Ethereum side of every swap.
Flow
- Ethereum to NEAR Intents. Each quote from the operator’s 1Click API comes with a fresh Ethereum deposit address. The user sends ETH or an ERC-20 there. The operator’s custodial bridge, named Proof-of-Authority (PoA), sweeps the funds into its treasury
0x2CfF…2680. It then mints a wrapped token on NEAR whose memo names the Ethereum transaction hashA fixed-length fingerprint of variable-size input, produced by a hash function.. - Swap to ZEC. Market makers quote offchain through a relay the operator runs. The winning quote settles in the VerifierAn entity in a ZK-Rollup, often a smart contract, that verifies zero-knowledge proofs submitted by a prover. contract
intents.near, whose balances and swaps are public NEAR state. - Withdraw into Zcash. The wrapped ZEC is burned through the Zcash connector
zcash-connector.bridge.near. The connector builds a transaction from bridge funds and has NEAR’s MPC network sign it. The payout goes to a shielded address that Zodl creates for every swap, and the burn message publishes it. The connector requires an all-zero outgoing viewing key so that it can check the payout, so anyone can decrypt its address and amount. - Inside Zcash. The ZEC sits in the shielded pool, where transfers hide sender, recipient and amount. Every amount that enters or leaves the pool is public, so a round trip of similar size within a short time pairs up.
- Back to Ethereum. Zodl pays ZEC from the pool to a fresh transparent deposit address of the connector. A relayer proves the deposit to the Zcash light clientSometimes labelled interchangeably as a “node”, they are tasked with processing transactions and managing the blockchains's state. They run the computations for each transaction according to the rollup's virtual machine and protocol rules. If comparing to Ethereum clients, these would be execution clients such as Geth, as opposed to consensus clients.
zcash-client.bridge.near, and the wrapped ZEC is minted and swapped. The operator then pays the Ethereum address from its treasury.
App
Zodl, formerly Zashi, is rated with its built-in Tor switched on manually. It syncs from public lightwalletd servers, which serve the Zcash chain to light wallets, zec.rocks by default. Each sync looks up the transparent addresses of every account in the wallet over one Tor connection. The custom server setting can move all of this to a lightwalletd the user runs.
Custody
The Ethereum leg is custodial. The operator’s deposit and treasury addresses are EOAs, and the operator mints the wrapped tokens on NEAR. The Verifier lets the NEAR Intents multisig and one single-key account freeze any account, which the operator uses for compliance holds. On Zcash, the connector holds funds at MPC-derived addresses and checks deposits against the light client. Relayers post Zcash blockAn ordered list of transactions and chain-related metadata that gets bundled together and published to the L1/DA layer. Nodes execute the transactions contained within blocks to change the rollup chain’s state. Protocol rules dictate what constitutes a valid block, and invalid blocks are skipped over. headers, credit deposits and request withdrawals. Anyone can become one by staking 1,000 NEAR and waiting seven days, unless the Rainbow Bridge multisig rejects them. The roles are listed under upgrades and governance.
Compliance
Intents Technology Ltd. (British Virgin Islands) screens every quote against the NEAR Intents AML portal, Binance AML, AMLBot, PureFi and TRM Labs. Its terms let it delay, block or freeze bridged funds and collect IP and wallet addresses. Market makers pass KYB, end users swap without an account.
Fees
The Verifier charges 1 pip (0.0001%) per swap. Zodl adds a 0.67% app fee to each quote, which it shares with the 1Click API. Each leg also pays a bridge withdrawal fee, 0.000035 ETH on Ethereum and 0.00047 ZEC on Zcash on 2026-10-08.
What the protocol promises: Hides which funds leaving Ethereum come back as which, by passing through Zcash's shielded pool. Everything on Ethereum and NEAR is public.
NEAR Intents web appLeaks moreEvery swap runs through an account named after the connected wallet, whose one ZEC deposit address links all its round trips publicly.
Fix: Swap through a fresh 1Click deposit address per quote, as Zodl does. · Source
Cake WalletLeaks moreIts built-in Tor skips the Zcash wallet, so the lightwalletd server gets each transaction it sends with the user's IP.
Fix: Route the Zcash wallet's lightwalletd connections through the built-in Tor. · Source
Brave WalletLeaks moreThe wallet is disabled in Tor windows and has no Tor setting, so Brave's Zcash and swap servers get the user's IP.
Fix: Offer a Tor setting that covers the wallet's Zcash sync and swap requests. · Source
Unstoppable WalletLeaks moreRoutes every swap through Unstoppable's own server, which records each leg's payout and refund addresses and deposit transaction hash.
Fix: Request quotes and report deposits to the 1Click API directly. · Source
ZkoolLeaks morePays swaps only to the account's transparent address, which adds a public shielding step.
Fix: Pay each swap to a fresh shielded address. · Source
Ethereum is public by default. Each protocol is rated on its main privacy promise, like hiding who paid, who received, how much, or which deposit became which withdrawal. Against each adversary, the colour says whether it holds for a careful user with the app's own settings: green yes, yellow only with significant extra work, red no. Fields marked at risk stay private only under the condition in their note.
Zcash’s shielded pool hides which payout into it funds which later exit. Everything up to the pool edge is public: the Ethereum deposit and the NEAR entries that credit, swap and withdraw it. The bridgeA message-passing protocol between two blockchains. At its most basic, a token bridge consists of a smart contract which can escrow funds on one side of the bridge, and instruct the release or minting of corresponding assets on the other side, but bridges could also support arbitrary messages. How these instructions are validated is a critical factor in assessing the trust assumptions of a bridge. encrypts each payout so that anyone can decrypt its Zcash address and amount.
Only the amount and timing of a round trip can pair a payout into the pool with a later deposit to the bridgeA message-passing protocol between two blockchains. At its most basic, a token bridge consists of a smart contract which can escrow funds on one side of the bridge, and instruct the release or minting of corresponding assets on the other side, but bridges could also support arbitrary messages. How these instructions are validated is a critical factor in assessing the trust assumptions of a bridge.. Deposit addresses are fresh per quote and spent together with the bridge change address, which marks every exit as NEAR Intents.
Advice: Hold the ZEC in the pool for days, split or merge it with other shielded funds, and swap back amounts that match no payout.
Each sync sends the account’s transparent addresses to lightwalletd before fetching its transactions, so lightwalletd can tie the payout and the exit to the account. With Tor on, each 1Click request and each sent transaction gets its own circuitA program written for the purpose of being proven within a proving system. A circuit is a mathematical representation of the computation to be executed, arithmetic circuits and zkVM execution trace are examples of circuits. Circuits can be written in different languages, ranging from low-level to high-level., and sync lookups go over Tor while blocksAn ordered list of transactions and chain-related metadata that gets bundled together and published to the L1/DA layer. Nodes execute the transactions contained within blocks to change the rollup chain’s state. Protocol rules dictate what constitutes a valid block, and invalid blocks are skipped over. download directly. Tor hides the user’s IP from the lookups, not the addresses they name.
Advice: Turn on Tor in Zodl and point it at a lightwalletd server the user runs.
The operatorAn operator is the entity charged with managing a rollup and progressing its state. A rollup operator can be a centralized sequencer, proposer, prover, challenger, pauser of admin that is able to perform upgrades. custodies both legs in transit and can freeze any account or deposit, setting the terms on which the user’s funds return. Over Tor, its 1Click API sees each leg only as NEAR publishes it, with a fresh shielded address per swap. It holds no key into the shielded pool.
Whoever breaks elliptic-curve cryptography recovers an account’s incoming viewing key from any of its payout addresses, which are public on NEAR. All of the account’s rotated addresses share that key, so it decrypts every note the account ever received. Those include the change notes of its exits, which join both legs of every round trip. ZIP 2005’s quantum recoverability protects only funds.
Funds can be stolen if
- the custodial bridgeA message-passing protocol between two blockchains. At its most basic, a token bridge consists of a smart contract which can escrow funds on one side of the bridge, and instruct the release or minting of corresponding assets on the other side, but bridges could also support arbitrary messages. How these instructions are validated is a critical factor in assessing the trust assumptions of a bridge. operatorAn operator is the entity charged with managing a rollup and progressing its state. A rollup operator can be a centralized sequencer, proposer, prover, challenger, pauser of admin that is able to perform upgrades.’s mint key or its Ethereum treasury key is compromised.
- the NEAR Intents multisig deploys a malicious upgrade of the VerifierAn entity in a ZK-Rollup, often a smart contract, that verifies zero-knowledge proofs submitted by a prover., with no delay.
- the Rainbow Bridge multisig deploys a malicious upgrade of the Zcash connector, its token or the light clientSometimes labelled interchangeably as a “node”, they are tasked with processing transactions and managing the blockchains's state. They run the computations for each transaction according to the rollup's virtual machine and protocol rules. If comparing to Ethereum clients, these would be execution clients such as Geth, as opposed to consensus clients., with no delay.
- a threshold of the NEAR MPC nodes colludes to sign Zcash transactions from bridge addresses.
Funds can be frozen if
- the NEAR Intents multisig or the single-key account locker freezes the user’s account in the Verifier.
- the custodial bridge operator holds a deposit or withdrawal for a compliance review.
- the relayers stop and the Rainbow Bridge multisig rejects anyone who stakes to replace them.
Privacy can be lost if
- the operator, which custodies both legs, makes the release of either depend on who the user is (see privileged insider).
- the lightwalletd server Zodl syncs from ties the payout and the exit to the account through the transparent addresses each sync sends (see networkA constellation of nodes (peers) that communicate via a peer-to-peer protocol, for example, in propagating transactions and blocks to other nodes. observer).
- elliptic-curve cryptography is broken, which recovers each account’s viewing key from its payout addresses on NEAR (see future adversary).
The route touches three governed systems on NEAR, each can change instantly. The Ethereum side runs on EOAs.
NEAR Intents VerifierAn entity in a ZK-Rollup, often a smart contract, that verifies zero-knowledge proofs submitted by a prover. (intents.near)
intents.sputnik-dao.near, a 3/5 multisig, holds the DAO role and is super admin, so it can grant every other role. Upgrades go through ctl-intents.near, a controller whose only admin is the same multisig, and deploy at once. Two EOAs there can apply a release the multisig added or roll back to the previous one. Seven accounts hold PauseManager and can halt all swaps and withdrawals, and only the multisig can resume them. One EOA holds UnrestrictedAccountLocker and can lock any user account. A locked account keeps receiving deposits, while its intents and withdrawals stop until the multisig unlocks it.
Custodial “PoA” bridgeA message-passing protocol between two blockchains. At its most basic, a token bridge consists of a smart contract which can escrow funds on one side of the bridge, and instruct the release or minting of corresponding assets on the other side, but bridges could also support arbitrary messages. How these instructions are validated is a critical factor in assessing the trust assumptions of a bridge. (omft.near, eth.omft.near)
The poa-factory contract omft.near deploys one token per bridged asset. It mints on the signal of TokenDepositer: bridge-mng.near, an EOA, and int-mnt-dao.sputnik-dao.near, a 3/3 multisig. NEAR takes every mint on trust. The NEAR Intents multisig is super admin.
Zcash connector (zcash-connector.bridge.near, zec.omft.near, zcash-client.bridge.near)
rainbowbridge.sputnik-dao.near, a 3/5 multisig, governs the connector, the token’s controller and the light clientSometimes labelled interchangeably as a “node”, they are tasked with processing transactions and managing the blockchains's state. They run the computations for each transaction according to the rollup's virtual machine and protocol rules. If comparing to Ethereum clients, these would be execution clients such as Geth, as opposed to consensus clients., and sets the bridge fees. bridge-ops.near can stage code and pause the connector, and pm.bridge.near can pause it. omni-relayer.bridge.near, intents-relayer.near and bridge-ops.near prove deposits against the light client, whose headers zcash-relayer.near relays. Withdrawals are signed by the NEAR MPC networkA constellation of nodes (peers) that communicate via a peer-to-peer protocol, for example, in propagating transactions and blocks to other nodes. v1.signer (11/16, see the MPC operators page) on request of a relayer. These four hold roles that make them relayers, and the multisig can reject anyone else who applies. Anyone can refund a deposit the connector never credited, once the light client holds its blockAn ordered list of transactions and chain-related metadata that gets bundled together and published to the L1/DA layer. Nodes execute the transactions contained within blocks to change the rollup chain’s state. Protocol rules dictate what constitutes a valid block, and invalid blocks are skipped over.. The refund waits two days. Without a refund address in the deposit message, it waits 100 years unless the multisig shortens that. The multisig or omni-relayer.bridge.near can reject the refund until then.
Transparent setup
Detailed description
Transparent proving systems require no trusted setups and have no additional setup-related trust assumptions.
Zcash via NEAR Intents