Solana is classified as a native asset for this route. SOL uses a network-specific contract asset on Base. The recorded Base representation uses 9 decimal places. Native SOL leaves a Solana account through a signed transaction and pays the fee; wrapped or tokenized SOL uses a token account or external contract instead.
This route crosses two L2 execution environments. Base settles to ethereum, while zkSync Era settles to ethereum; each side keeps its own gas balance, token contracts, transaction hash, and settlement progress.
zkSync Era is a L2 EVM network in the Ethereum ecosystem. ETH pays destination-side network gas on zkSync Era. EVM 0x account address A zkSync Era receipt belongs to EraVM account state and uses ETH for later fees; proof settlement to Ethereum remains distinct from L2 delivery.
Chainlink is classified as a governance or utility token for this route. LINK uses a network-specific contract asset on zkSync Era. The zkSync Era side is contract-tracked rather than a native gas balance. LINK arrives as a network-specific contract balance. The wallet still needs the destination native asset before it can transfer or approve LINK later.
Base is a L2 EVM network in the Ethereum ecosystem. ETH pays source-side network gas on Base. EVM 0x account address A Base source transaction is sequenced on the OP Stack rollup and later settles to Ethereum; Base ETH and Base token approvals remain on the L2 ledger.
Base and zkSync Era can use the same 0x address syntax, but they are separate networks with different chain identifiers, gas balances, token contracts, and transaction histories. The recorded settlement context includes ethereum, so L1 and L2 confirmation behavior should not be assumed identical.
Route-specific mistakes include sending on a network other than Base; using a destination that is not valid for zkSync Era; running out of ETH before the source transaction is submitted. A Base source transaction is sequenced on the OP Stack rollup and later settles to Ethereum; Base ETH and Base token approvals remain on the L2 ledger. Native SOL leaves a Solana account through a signed transaction and pays the fee; wrapped or tokenized SOL uses a token account or external contract instead. A zkSync Era receipt belongs to EraVM account state and uses ETH for later fees; proof settlement to Ethereum remains distinct from L2 delivery. LINK arrives as a network-specific contract balance. The wallet still needs the destination native asset before it can transfer or approve LINK later.
Base wallet, token-transfer, contract, log, and gas activity remain public, and zkSync Era wallet, token-transfer, contract, log, and gas activity remain public. For this SOL on Base to LINK on zkSync Era 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.
SOL is a contract representation on Base with 9 decimals at 0x311935Cd80B76769bF2ecC9D8Ab7635b2139cf82. ETH, not SOL, pays gas unless both symbols are the same. A Base source transaction is sequenced on the OP Stack rollup and later settles to Ethereum; Base ETH and Base token approvals remain on the L2 ledger. Native SOL leaves a Solana account through a signed transaction and pays the fee; wrapped or tokenized SOL uses a token account or external contract instead.
LINK is a contract representation on zkSync Era at 0x52869bae3e091e36b0915941577f2d47d8d8b534. ETH, not LINK, pays gas unless both symbols are the same. A zkSync Era receipt belongs to EraVM account state and uses ETH for later fees; proof settlement to Ethereum remains distinct from L2 delivery. LINK arrives as a network-specific contract balance. The wallet still needs the destination native asset before it can transfer or approve LINK later.
Native SOL leaves a Solana account through a signed transaction and pays the fee; wrapped or tokenized SOL uses a token account or external contract instead. On receipt, LINK arrives as a network-specific contract balance. The wallet still needs the destination native asset before it can transfer or approve LINK later.
SOL is the deposited native-asset input; LINK is the quoted token output. Source allowance or native-spend rules and destination wallet/representation checks are evaluated separately.
Native SOL leaves a Solana account through a signed transaction and pays the fee; wrapped or tokenized SOL uses a token account or external contract instead. A Base source transaction is sequenced on the OP Stack rollup and later settles to Ethereum; Base ETH and Base token approvals remain on the L2 ledger. A zkSync Era receipt belongs to EraVM account state and uses ETH for later fees; proof settlement to Ethereum remains distinct from L2 delivery. LINK arrives as a network-specific contract balance. The wallet still needs the destination native asset before it can transfer or approve LINK later.
ETH is the native gas asset for Base. A Base source transaction is sequenced on the OP Stack rollup and later settles to Ethereum; Base ETH and Base token approvals remain on the L2 ledger. SOL is token-tracked and can need approval before transfer.
Sending SOL on a network other than Base, or using an address that is not valid for zkSync Era, can prevent detection or delivery. Match both network labels and representations to the active route.
Requirements are checked for the live SOL Base to LINK zkSync quote. Verification requirements can depend on the provider, amount, jurisdiction, and current route. Sasquatch does not verify this route as universally no-KYC; check the live flow before continuing.
