BNB is classified as a native asset for this route. BNB uses a network-specific contract asset on Polygon. The recorded Polygon 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.
Polygon source execution occurs on L1, while Base delivery occurs on a separate L2 ledger that settles to ethereum. POL pays source gas and ETH is the destination gas asset; identical-looking wallet addresses do not merge the balances or transaction histories.
Base is a L2 EVM network in the Ethereum ecosystem. ETH pays destination-side network gas on Base. EVM 0x account address A Base receipt belongs to the Base L2 balance and token contract, not Ethereum L1; later activity needs ETH specifically on Base.
Chainlink is classified as a governance or utility token for this route. LINK uses a network-specific contract asset on Base. The Base 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.
Polygon is a L1 EVM network in the Polygon ecosystem. POL pays source-side network gas on Polygon. EVM 0x account address A Polygon PoS source uses its validator/checkpoint system and POL gas; its token contracts and checkpoints are separate from Ethereum L1.
Polygon and Base 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 Polygon; using a destination that is not valid for Base; running out of POL before the source transaction is submitted. A Polygon PoS source uses its validator/checkpoint system and POL gas; its token contracts and checkpoints are separate from Ethereum L1. Native BNB can fund value and BSC gas, while tokenized BNB requires the source chain’s gas asset and contract handling. A Base receipt belongs to the Base L2 balance and token contract, not Ethereum L1; later activity needs ETH specifically on Base. LINK arrives as a network-specific contract balance. The wallet still needs the destination native asset before it can transfer or approve LINK later.
Polygon wallet, token-transfer, contract, log, and gas activity remain public, and Base wallet, token-transfer, contract, log, and gas activity remain public. For this BNB on Polygon to LINK on Base 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 a contract representation on Polygon with 18 decimals at 0x5c4b7CCBF908E64F32e12c6650ec0C96d717f03F. POL, not BNB, pays gas unless both symbols are the same. A Polygon PoS source uses its validator/checkpoint system and POL gas; its token contracts and checkpoints are separate from Ethereum L1. 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 Base at 0x88fb150bdc53a65fe94dea0c9ba0a6daf8c6e196. ETH, not LINK, pays gas unless both symbols are the same. A Base receipt belongs to the Base L2 balance and token contract, not Ethereum L1; later activity needs ETH specifically on Base. 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 Polygon PoS source uses its validator/checkpoint system and POL gas; its token contracts and checkpoints are separate from Ethereum L1. A Base receipt belongs to the Base L2 balance and token contract, not Ethereum L1; later activity needs ETH specifically on Base. LINK arrives as a network-specific contract balance. The wallet still needs the destination native asset before it can transfer or approve LINK later.
POL is the native gas asset for Polygon. A Polygon PoS source uses its validator/checkpoint system and POL gas; its token contracts and checkpoints are separate from Ethereum L1. BNB is token-tracked and can need approval before transfer.
Sending BNB on a network other than Polygon, or using an address that is not valid for Base, can prevent detection or delivery. Match both network labels and representations to the active route.
Requirements are checked for the live BNB Polygon to LINK Base 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.
