Private USDC on Solana to WETH on Linea Swap

FromSolana
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 considerations for USDC to WETH

Where offered, Private Route is designed to reduce an obvious direct association between the sending wallet and received assets; it does not make USDC on Solana or WETH on Linea activity anonymous or invisible. 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. 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. USDC is an issued dollar-oriented stablecoin with canonical, native, and bridged variants across networks. Contract events and issuer controls differ from a network-native gas asset. WETH is a contract wrapper for ETH. It can be transferred as a token but cannot replace the native gas balance required by the network. Stablecoins can exist through different contracts and issuers on different networks. Confirm the exact representation and remember that contract events, issuer controls, receiving services, and later transfers can add context beyond the immediate swap. Identity-verification requirements are separate and must be checked in the live flow.

What remains visible on Solana

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. SOL is the native gas asset for Solana. Reusing the sending address, approval pattern, or recognizable amount can preserve source-side context.

What remains visible on Linea

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. Receiving-address reuse, immediate consolidation, and later transfers can create destination-side associations.

Solana source role versus Linea destination role

A Solana source signs over accounts or token accounts, identifies SPL assets by mint, and spends SOL for transaction fees. Those source-side events remain visible. 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. That receipt and later destination activity remain visible.

Solana source activity and EVM delivery remain inspectable

Solana exposes the source signature, accounts, mint or native balance changes, programs, and SOL fee. Linea exposes the destination 0x account, token contract or native receipt, logs, and later gas funding.

Stablecoin contracts add representation and issuer context

The source wallet sends the exact USDC native or contract representation selected by the route; contract USDC can require approval and the chain’s native gas asset. Source contract events remain visible. WETH arrives as a token contract balance. It may need an explicit unwrap before becoming native ETH and cannot itself pay transaction gas. Issuer controls, receiving-service deposits, and later transfers can provide context beyond the immediate route.

Wrapper activity can add another association point

Wrapped-token approvals, transfers, and later unwrap activity are public contract events. The source wallet sends the exact USDC native or contract representation selected by the route; contract USDC can require approval and the chain’s native gas asset. WETH arrives as a token contract balance. It may need an explicit unwrap before becoming native ETH and cannot itself pay transaction gas.

USDC native, canonical, or bridged evidence; WETH wrapper and unwrap evidence

The exact USDC representation determines the public contract or native record. Issuer controls, transfer events, receiving services, amount, timing, and later use remain outside any promise of invisibility. The source wallet sends the exact USDC native or contract representation selected by the route; contract USDC can require approval and the chain’s native gas asset. Those source events remain public. WETH approvals, wrapper transfers, and later unwrap activity remain visible contract events. A private route does not turn WETH into an unrecorded native ETH balance. WETH arrives as a token contract balance. It may need an explicit unwrap before becoming native ETH and cannot itself pay transaction gas. The receipt and later destination use remain public.

What Private Route changes—and what it does not

Private routing can reduce a direct association between the Solana source account and EVM receiver. The source signature, program and token-account changes, destination contract logs, gas, amounts, and timing remain public. A Solana source signs over accounts or token accounts, identifies SPL assets by mint, and spends SOL for transaction fees. The source wallet sends the exact USDC native or contract representation selected by the route; contract USDC can require approval and the chain’s native gas asset. 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. WETH arrives as a token contract balance. It may need an explicit unwrap before becoming native ETH and cannot itself pay transaction gas.

Verification and provider policy for this exact route

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 Solana source signs over accounts or token accounts, identifies SPL assets by mint, and spends SOL for transaction fees. The source wallet sends the exact USDC native or contract representation selected by the route; contract USDC can require approval and the chain’s native gas asset. 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. WETH arrives as a token contract balance. It may need an explicit unwrap before becoming native ETH and cannot itself pay transaction gas.

Private Route for USDC → WETH

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

Related routes

Private USDC on Solana to WETH on Linea Swap FAQs

What must be checked before using Private Route for USDC on Solana to WETH on Linea?

Confirm the live privacy status, provider, exact USDC source representation, WETH destination representation, amount, region, fees, address, and any verification request. A Solana source signs over accounts or token accounts, identifies SPL assets by mint, and spends SOL for transaction fees. The source wallet sends the exact USDC native or contract representation selected by the route; contract USDC can require approval and the chain’s native gas asset. 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. WETH arrives as a token contract balance. It may need an explicit unwrap before becoming native ETH and cannot itself pay transaction gas.

Which USDC on Solana records remain public?

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 USDC deposit, gas funding, approval or native transfer, amount, and timing remain outside any promise of invisibility.

Which WETH on Linea records remain public after delivery?

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 WETH receipt and later wallet activity remain observable on that ledger.

Can EVM and Solana records still be correlated?

Potentially. The 0x-side transaction and Solana signature are separate, but comparable amounts, close timing, token representations, provider observations, address reuse, and later consolidation can still support association.

Do stablecoins create additional privacy considerations here?

Yes. The source wallet sends the exact USDC native or contract representation selected by the route; contract USDC can require approval and the chain’s native gas asset. WETH arrives as a token contract balance. It may need an explicit unwrap before becoming native ETH and cannot itself pay transaction gas. Issuer, representation, amount, timing, and receiving-service context can remain observable.

How do USDC source records differ from WETH receipt records?

The source wallet sends the exact USDC native or contract representation selected by the route; contract USDC can require approval and the chain’s native gas asset. WETH arrives as a token contract balance. It may need an explicit unwrap before becoming native ETH and cannot itself pay transaction gas. Private Route does not erase either asset-specific record.

Does this private USDC to WETH route 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 Solana source signs over accounts or token accounts, identifies SPL assets by mint, and spends SOL for transaction fees. The source wallet sends the exact USDC native or contract representation selected by the route; contract USDC can require approval and the chain’s native gas asset. 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. WETH arrives as a token contract balance. It may need an explicit unwrap before becoming native ETH and cannot itself pay transaction gas.

View all Help Center FAQs →