BNB is classified as a native asset for this route. BNB uses a native asset on BNB Chain. The recorded BNB Chain representation uses 18 decimal places. Native BNB can fund value and BSC gas, while tokenized BNB requires the source chain’s gas asset and contract handling.
BNB Chain source execution occurs on L1, while Scroll delivery occurs on a separate L2 ledger that settles to ethereum. BNB pays source gas and ETH is the destination gas asset; identical-looking wallet addresses do not merge the balances or transaction histories.
Scroll is a L2 EVM network in the Ethereum ecosystem. ETH pays destination-side network gas on Scroll. EVM 0x account address A Scroll receipt is an L2 native or contract balance whose proof settlement to Ethereum is a separate milestone; later activity uses ETH on Scroll.
Chainlink is classified as a governance or utility token for this route. LINK uses a network-specific contract asset on Scroll. The Scroll 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 is a L1 EVM network in the BNB Chain ecosystem. BNB pays source-side network gas on BNB Chain. EVM 0x account address 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.
BNB Chain and Scroll 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 BNB Chain; using a destination that is not valid for Scroll; running out of BNB before the source transaction is submitted. 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 BNB can fund value and BSC gas, while tokenized BNB requires the source chain’s gas asset and contract handling. A Scroll receipt is an L2 native or contract balance whose proof settlement to Ethereum is a separate milestone; later activity uses ETH on Scroll. 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 Scroll wallet, token-transfer, contract, log, and gas activity remain public. For this BNB on BNB Chain to LINK on Scroll 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.
BNB is listed as the native representation on BNB Chain; BNB is used for network gas. 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 BNB can fund value and BSC gas, while tokenized BNB requires the source chain’s gas asset and contract handling.
LINK is a contract representation on Scroll at 0x548c6944cba02b9d1c0570102c89de64d258d3ac. ETH, not LINK, pays gas unless both symbols are the same. A Scroll receipt is an L2 native or contract balance whose proof settlement to Ethereum is a separate milestone; later activity uses ETH on Scroll. 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 BNB can fund value and BSC gas, while tokenized BNB requires the source chain’s gas asset and contract handling. 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.
BNB 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 BNB can fund value and BSC gas, while tokenized BNB requires the source chain’s gas asset and contract handling. 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 Scroll receipt is an L2 native or contract balance whose proof settlement to Ethereum is a separate milestone; later activity uses ETH on Scroll. 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 is the native gas asset for BNB Chain. 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. BNB is recorded as native on this source.
Sending BNB on a network other than BNB Chain, or using an address that is not valid for Scroll, can prevent detection or delivery. Match both network labels and representations to the active route.
Requirements are checked for the live BNB BSC to LINK Scroll 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.
