Sasquatch Exchange
TRADE
OrdersSupportAffiliatePrivate Swap

Private zkSync Era to Base Bridge

FromzkSync Era
ToBase
ENTER AMOUNT
Squatch Guard
Before a deposit order moves forward, Squatch Guard checks the amount, asset, network, and active quote window against the order details.

What you need to know

Privacy for the zkSync Era to Base direction

Where offered, Private Route is intended to reduce an obvious direct association between the zkSync Era sending wallet and Base receiving wallet; it does not hide either blockchain. ETH is the native gas asset for zkSync Era. EVM 0x account address ETH is the native gas asset for Base. EVM 0x account address Similar amounts, timing, address reuse, and later consolidation can still add association signals. Identity requirements must be checked separately.

zkSync Era source-side visibility

zkSync Era exposes account history, token approvals, contract calls, logs, gas funding, amounts, and timing under its own chain identifier. It is a zero-knowledge rollup using EraVM and native account-abstraction features while settling proofs to Ethereum. Execution, fee estimation, and contract compatibility can differ from a byte-for-byte Ethereum assumption. The source deposit, gas funding, asset representation, confirmations, and sending-address history remain outside any promise of invisibility.

Base destination-side visibility

Base exposes account history, token approvals, contract calls, logs, gas funding, amounts, and timing under its own chain identifier. It is an OP Stack optimistic rollup that batches L2 execution and settles to Ethereum. The same 0x wallet can display different balances on Base and Ethereum, and a token contract on one chain does not identify the representation on the other. The destination delivery and later activity can remain observable even when the provider path reduces a direct association.

zkSync Era deposit role versus Base receipt role

A zkSync Era source executes in EraVM with native account-abstraction behavior and ETH fees before proof settlement to Ethereum. Those deposit-side events remain public. A Base receipt belongs to the Base L2 balance and token contract, not Ethereum L1; later activity needs ETH specifically on Base. The receipt and later activity remain public.

Two EVM histories can still be compared

zkSync Era and Base use separate chain identifiers, balances, contracts, transaction hashes, and gas records even when address syntax matches. Sequencer inclusion and settlement timing can add further observable milestones.

Cross-chain linkability limits

Private routing can reduce an obvious link between two EVM accounts, but source approvals, gas, logs, destination contract or native receipt, and later activity remain on separate chain histories. Sequencer and settlement timing can add correlation evidence. A zkSync Era source executes in EraVM with native account-abstraction behavior and ETH fees before proof settlement to Ethereum. A Base receipt belongs to the Base L2 balance and token contract, not Ethereum L1; later activity needs ETH specifically on Base.

Verification status is separate from privacy status

The provider must support the exact L2 direction, asset contracts, amount, and region. Rollup support and privacy routing do not imply that identity verification, account, or custody requirements are absent. A zkSync Era source executes in EraVM with native account-abstraction behavior and ETH fees before proof settlement to Ethereum. A Base receipt belongs to the Base L2 balance and token contract, not Ethereum L1; later activity needs ETH specifically on Base.

Private Route for USDC → USDC

zkSync Era wallet, token-transfer, contract, log, and gas activity remain public, and Base wallet, token-transfer, contract, log, and gas activity remain public. For this USDC on zkSync Era to USDC on Base path, Private Route is intended to reduce the direct visible relationship between activity around the source-side EVM 0x account address and destination-side EVM 0x account address; it does not hide either chain's public records.

  • ✓Reduces the obvious link between the USDC deposit and USDC receipt
  • ✓Compare standard and Private Route options for zkSync Era → Base
  • ✓Shows what remains public on zkSync Era and Base before you deposit
Check Private Route availability →

Related routes

zkSync Era to Base standard bridgeStandard routePrivate Base to zkSync Era optionsReverse privacy-intent routePrivate zkSync Era bridge routesPrivate Base bridge routesPrivate bridge directoryHow private cross-chain routing worksBridge Base to zkSync EraReverse routeBridge Arbitrum to BaseRelated network route

Private zkSync Era to Base Bridge FAQs

What must be verified for a private zkSync Era to Base bridge?

Check the exact source and destination asset representations, live privacy status, provider, amount, region, source gas, destination address, fees, and any verification request. Standard bridge support is not proof of private availability.

Which zkSync Era bridge records remain public?

zkSync Era exposes account history, token approvals, contract calls, logs, gas funding, amounts, and timing under its own chain identifier. It is a zero-knowledge rollup using EraVM and native account-abstraction features while settling proofs to Ethereum. Execution, fee estimation, and contract compatibility can differ from a byte-for-byte Ethereum assumption. The deposit, gas funding, representation, confirmations, amount, and sending-address history remain observable.

Which Base records remain public after receipt?

Base exposes account history, token approvals, contract calls, logs, gas funding, amounts, and timing under its own chain identifier. It is an OP Stack optimistic rollup that batches L2 execution and settles to Ethereum. The same 0x wallet can display different balances on Base and Ethereum, and a token contract on one chain does not identify the representation on the other. Delivery and later activity remain observable even if the provider path reduces direct wallet association.

Does private zkSync Era to Base bridging guarantee no KYC?

The provider must support the exact L2 direction, asset contracts, amount, and region. Rollup support and privacy routing do not imply that identity verification, account, or custody requirements are absent. A zkSync Era source executes in EraVM with native account-abstraction behavior and ETH fees before proof settlement to Ethereum. A Base receipt belongs to the Base L2 balance and token contract, not Ethereum L1; later activity needs ETH specifically on Base.

View all Help Center FAQs →