How to bridge ETH to zkSync Era? (Official bridge guide)

Understanding the zkSync Era Bridge Mechanism

1. The official zkSync Era bridge operates as a trustless, non-custodial channel between Ethereum Mainnet and zkSync Era’s Layer 2 network.

2. Users initiate transfers by interacting directly with smart contracts deployed on Ethereum, verified and audited by Matter Labs.

3. ETH bridging involves locking native ETH on L1 and minting equivalent canonical ETH tokens on zkSync Era.

4. The process relies on zk-rollup cryptographic proofs to ensure finality and data availability without requiring third-party validators.

5. Transaction batches are submitted to Ethereum every ~10–30 minutes, with proof verification occurring on-chain via the verifier contract.

Step-by-Step ETH Bridging Process

1. Navigate to https://bridge.zksync.io using a supported browser with MetaMask or another EIP-1193–compliant wallet installed.

2. Connect your wallet to the Ethereum Mainnet network—ensure it holds sufficient ETH for gas and the amount you intend to bridge.

3. Select “Ethereum” as the source chain and “zkSync Era” as the destination; confirm ETH is the selected asset.

4. Enter the amount of ETH to bridge, then click “Deposit” and approve two transactions: one granting allowance (if needed) and another initiating the lock.

5. Wait for the transaction to be confirmed on Ethereum; once included in a zkSync batch and verified, funds appear in your zkSync Era wallet—typically within 15–40 minutes.

Security Considerations and Verification

1. All bridge contracts are open-source and published on GitHub under the matter-labs/zksync repository with full Solidity code and deployment addresses.

2. Users can verify the exact contract address used during bridging against the official list published on the zkSync docs site.

3. No private keys are ever transmitted or stored—the entire flow occurs client-side using signed messages and on-chain execution.

4. Reorg protection is enforced through Ethereum’s 12-block confirmation threshold before batches are considered finalized.

5. Withdrawals from zkSync Era back to Ethereum require waiting for the challenge period to expire—currently set at 7 days—but deposits are irreversible after confirmation.

Common Issues During ETH Transfer

1. Insufficient gas may cause deposit failure; always maintain at least 0.01 ETH on Ethereum Mainnet beyond the bridging amount.

2. Network congestion on Ethereum can delay confirmation—monitor current gas prices via Etherscan before initiating.

3. Some wallets display incorrect balances immediately after bridging due to caching; refreshing the zkSync block explorer resolves this.

4. Using unofficial bridges or phishing sites may result in permanent loss—only interact with bridge.zksync.io and verified contract addresses.

5. MetaMask must be manually configured to add zkSync Era as a custom RPC network after bridging to view balances properly.

Frequently Asked Questions

Q: Can I bridge ETH from a hardware wallet like Ledger or Trezor?A: Yes—connect the device via WalletConnect or directly through MetaMask’s hardware wallet integration before initiating the bridge.

Q: Why does my ETH balance not appear instantly on zkSync Era after deposit confirmation?A: Finalization depends on batch submission and proof verification; delays up to 40 minutes are normal during peak load.

Q: Is there a minimum ETH amount required to bridge?A: No fixed minimum exists, but extremely small amounts may be uneconomical due to gas fees on Ethereum Mainnet.

Q: What happens if I send ETH to the zkSync Era bridge contract address directly via Etherscan?A: Funds will be stuck permanently—deposits must be initiated exclusively through the official bridge interface to trigger correct state transitions.