BNB Chain uses EVM account addresses and BNB for source gas. Solana uses Solana accounts, transaction signatures, and SOL for destination activity. A 0x address is not a valid substitute for the Solana receiving address shown by the route. SOL uses SOL contract token on the source; LINK uses LINK contract token on Solana.
Base58-encoded Solana account address A Solana receipt uses a native SOL balance or SPL token account identified by mint; later token movement and account creation use SOL fees. LINK arrives as a network-specific contract balance. The wallet still needs the destination native asset before it can transfer or approve LINK later. A compatible wallet may create or use an associated token account, and SOL—not LINK unless it is SOL—pays later Solana fees.
BNB is the native gas asset for BNB Chain. SOL is contract-tracked and can require an allowance before transfer. A BNB Smart Chain source uses BNB gas and BEP-20 contracts; a familiar 0x account does not turn a BEP-20 deposit into ERC-20.
Route-specific mistakes include sending on a network other than BNB Chain; using a destination that is not valid for Solana; running out of BNB before the source transaction is submitted; assuming evm and solana addresses are interchangeable. A BNB Smart Chain source uses BNB gas and BEP-20 contracts; a familiar 0x account does not turn a BEP-20 deposit into ERC-20. 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 Solana receipt uses a native SOL balance or SPL token account identified by mint; later token movement and account creation use SOL fees. LINK arrives as a network-specific contract balance. The wallet still needs the destination native asset before it can transfer or approve LINK later.
Solana is classified as a native asset for this route. SOL uses a network-specific contract asset on BNB Chain. The recorded BNB Chain representation uses 18 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.
Chainlink is classified as a governance or utility token for this route. LINK uses a network-specific contract asset on Solana. The Solana 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.
BNB Chain wallet, token-transfer, contract, log, and gas activity remain public, and Solana account, token, program, signature, and fee activity remain public. For this SOL on BNB Chain to LINK 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.
No. The destination must be a Solana-compatible address. Base58-encoded Solana account address
An SPL-token receipt uses the relevant mint and token account; the wallet or route may create an associated token account when needed. SOL is used for later Solana activity.
SOL is a contract representation on BNB Chain with 18 decimals at 0x570A5D26f7765Ecb712C0924E4De545B89fD43dF. BNB, not SOL, pays gas unless both symbols are the same. A BNB Smart Chain source uses BNB gas and BEP-20 contracts; a familiar 0x account does not turn a BEP-20 deposit into ERC-20. 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 Solana at LinkhB3afbBKb2EQQu7s7umdZceV3wcvAUJhQAfQ23L. SOL, not LINK, pays gas unless both symbols are the same. A Solana receipt uses a native SOL balance or SPL token account identified by mint; later token movement and account creation use SOL fees. 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 BNB Smart Chain source uses BNB gas and BEP-20 contracts; a familiar 0x account does not turn a BEP-20 deposit into ERC-20. A Solana receipt uses a native SOL balance or SPL token account identified by mint; later token movement and account creation use SOL fees. LINK arrives as a network-specific contract balance. The wallet still needs the destination native asset before it can transfer or approve LINK later.
Requirements are checked for the live SOL BSC to LINK Solana 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.
