Private Scroll to Linea Bridge

FromScroll
ToLinea
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 Scroll to Linea direction

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

Scroll source-side visibility

Scroll exposes account history, token approvals, contract calls, logs, gas funding, amounts, and timing under its own chain identifier. It is a bytecode-compatible zero-knowledge EVM rollup that proves batches to Ethereum. Scroll inclusion and Ethereum proof settlement are distinct, and its token contracts must be verified independently from L1. The source deposit, gas funding, asset representation, confirmations, and sending-address history remain outside any promise of invisibility.

Linea destination-side visibility

Linea exposes account history, token approvals, contract calls, logs, gas funding, amounts, and timing under its own chain identifier. It is a zero-knowledge EVM rollup that batches execution and proves state to Ethereum. L2 transaction inclusion, proof completion, and Ethereum settlement are different stages, while token contracts remain specific to Linea. The destination delivery and later activity can remain observable even when the provider path reduces a direct association.

Scroll deposit role versus Linea receipt role

A Scroll source executes in the zkEVM and is later included in a proof batch to Ethereum; Scroll contract identity must be verified independently. Those deposit-side events remain public. A Linea receipt is recorded on the zkEVM L2 before the related proof settles to Ethereum; later activity needs ETH on Linea and the Linea token contract. The receipt and later activity remain public.

Two EVM histories can still be compared

Scroll and Linea 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 Scroll source executes in the zkEVM and is later included in a proof batch to Ethereum; Scroll contract identity must be verified independently. A Linea receipt is recorded on the zkEVM L2 before the related proof settles to Ethereum; later activity needs ETH on Linea and the Linea token contract.

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 Scroll source executes in the zkEVM and is later included in a proof batch to Ethereum; Scroll contract identity must be verified independently. A Linea receipt is recorded on the zkEVM L2 before the related proof settles to Ethereum; later activity needs ETH on Linea and the Linea token contract.

Private Route for USDC → USDC

Scroll wallet, token-transfer, contract, log, and gas activity remain public, and Linea wallet, token-transfer, contract, log, and gas activity remain public. For this USDC on Scroll to USDC on Linea 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 Scroll → Linea
  • Shows what remains public on Scroll and Linea before you deposit
Check Private Route availability →

Related routes

Private Scroll to Linea Bridge FAQs

What must be verified for a private Scroll to Linea 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 Scroll bridge records remain public?

Scroll exposes account history, token approvals, contract calls, logs, gas funding, amounts, and timing under its own chain identifier. It is a bytecode-compatible zero-knowledge EVM rollup that proves batches to Ethereum. Scroll inclusion and Ethereum proof settlement are distinct, and its token contracts must be verified independently from L1. The deposit, gas funding, representation, confirmations, amount, and sending-address history remain observable.

Which Linea records remain public after receipt?

Linea exposes account history, token approvals, contract calls, logs, gas funding, amounts, and timing under its own chain identifier. It is a zero-knowledge EVM rollup that batches execution and proves state to Ethereum. L2 transaction inclusion, proof completion, and Ethereum settlement are different stages, while token contracts remain specific to Linea. Delivery and later activity remain observable even if the provider path reduces direct wallet association.

Does private Scroll to Linea 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 Scroll source executes in the zkEVM and is later included in a proof batch to Ethereum; Scroll contract identity must be verified independently. A Linea receipt is recorded on the zkEVM L2 before the related proof settles to Ethereum; later activity needs ETH on Linea and the Linea token contract.

View all Help Center FAQs →