Sasquatch Exchange
TRADE
OrdersSupportAffiliatePrivate Swap

Private Scroll to Solana Bridge

FromScroll
ToSolana
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 Solana direction

Where offered, Private Route is intended to reduce an obvious direct association between the Scroll sending wallet and Solana receiving wallet; it does not hide either blockchain. ETH is the native gas asset for Scroll. EVM 0x account address SOL is the native gas asset for Solana. Base58-encoded Solana 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.

Solana destination-side visibility

Solana exposes account keys, transaction signatures, token-account changes, program calls, amounts, fees, and timing. It uses an account-and-program execution model with transaction signatures rather than EVM hashes. SPL tokens use mint and token-account records, and a receiving wallet may need the correct associated token account plus SOL for later activity. The destination delivery and later activity can remain observable even when the provider path reduces a direct association.

Scroll deposit role versus Solana 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 Solana receipt uses a native SOL balance or SPL token account identified by mint; later token movement and account creation use SOL fees. The receipt and later activity remain public.

Public EVM deposit and public Solana delivery

Scroll exposes the 0x sender, gas, approvals, and deposit event. Solana exposes the receiving accounts, mint changes, program calls, signature, SOL fee, and later activity. Private Route does not make either record disappear.

Cross-chain linkability limits

Private routing can reduce a direct association between the EVM deposit account and Solana receiving account. The 0x transaction, approval, gas, Solana signature, token-account changes, amounts, and timing remain public 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 Solana receipt uses a native SOL balance or SPL token account identified by mint; later token movement and account creation use SOL fees.

Verification status is separate from privacy status

Provider policy is evaluated for the exact Solana mint or native asset, the other network representation, amount, and region. Cross-ecosystem wallet compatibility and no-KYC status are separate checks. 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 Solana receipt uses a native SOL balance or SPL token account identified by mint; later token movement and account creation use SOL fees.

Private Route for USDC → USDC

Scroll wallet, token-transfer, contract, log, and gas activity remain public, and Solana account, token, program, signature, and fee activity remain public. For this USDC on Scroll to USDC on Solana path, Private Route is intended to reduce the direct visible relationship between activity around the source-side EVM 0x account address and destination-side Base58-encoded Solana 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 → Solana
  • ✓Shows what remains public on Scroll and Solana before you deposit
Check Private Route availability →

Related routes

Scroll to Solana standard bridgeStandard routePrivate Solana to Scroll optionsReverse privacy-intent routePrivate Scroll bridge routesPrivate Solana bridge routesPrivate bridge directoryHow private cross-chain routing worksBridge Solana to ScrollReverse routeBridge Arbitrum to SolanaRelated network route

Private Scroll to Solana Bridge FAQs

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

Solana exposes account keys, transaction signatures, token-account changes, program calls, amounts, fees, and timing. It uses an account-and-program execution model with transaction signatures rather than EVM hashes. SPL tokens use mint and token-account records, and a receiving wallet may need the correct associated token account plus SOL for later activity. Delivery and later activity remain observable even if the provider path reduces direct wallet association.

Can the EVM transaction and Solana signature still be compared?

Potentially. They use different ledgers, but amount, timing, token representation, provider observations, address reuse, and later consolidation can still create context.

Does private Scroll to Solana bridging guarantee no KYC?

Provider policy is evaluated for the exact Solana mint or native asset, the other network representation, amount, and region. Cross-ecosystem wallet compatibility and no-KYC status are separate checks. 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 Solana receipt uses a native SOL balance or SPL token account identified by mint; later token movement and account creation use SOL fees.

View all Help Center FAQs →