Chain link is a wallet network choice before LINK confirmation

Matching the ticker while missing the network

A ticker-only match is the common setup error because LINK exists as separate contract balances on several EVM networks. Ethereum Mainnet uses chain ID 1, Arbitrum One uses 42161 and Base uses 8453; entering the same 0x recipient does not merge those ledgers. Read the destination’s network first, then select LINK deployed on that exact chain. In this Chain link workflow, matching all three fields - network, token contract and recipient - keeps the transfer on the intended ledger. The correct choice changes when the destination names another supported network.

Preparing the wallet before entering the recipient

Wallet preparation is a four-part prerequisite: the right account, an enabled network, recognized LINK and enough native coin for gas.

Start with the account expected to send LINK, because MetaMask, Rabby and Ledger can expose several addresses under one wallet interface. An EVM address contains 20 bytes, displayed as 40 hexadecimal characters after the 0x prefix, so copying the entire string matters. Enable the named network and check its chain ID before importing the token. LINK uses 18 decimal places on Ethereum, Arbitrum, Base, OP Mainnet, Polygon and Avalanche. A displayed ticker without the expected contract does not satisfy this check. The account also needs the network’s gas asset even when the LINK amount covers the intended transfer.

Use this five-point decision checklist after the destination supplies its deposit or wallet details:

• Sender: the selected account holds the LINK balance.
• Network: the chain name and chain ID match the receiver’s instruction.
• Token: the LINK contract matches that network’s published deployment.
• Recipient: the full 42-character address matches the intended account.
• Gas: the wallet shows enough ETH, POL or AVAX for the estimated fee.

MetaMask and Rabby estimate the fee after the amount and recipient are entered. A Ledger device signs the transaction prepared by its connected wallet; its screen cannot supply a missing network choice. Keep the amount below the displayed LINK balance so the interface can construct the call, then proceed when the destination accepts the selected chain.

Which network should I select for a LINK transfer?

The receiving network is the controlling requirement, so select the chain the recipient or application explicitly accepts for LINK deposits.

Chain IDs settle ambiguous labels. Ethereum Mainnet is 1, OP Mainnet is 10, BNB Smart Chain is 56, Polygon PoS is 137, Base is 8453, Arbitrum One is 42161 and Avalanche C-Chain is 43114. Ethereum, Base, OP Mainnet and Arbitrum One charge gas in ETH. Polygon PoS uses POL, Avalanche C-Chain uses AVAX and BNB Smart Chain uses BNB. Those fee assets remain separate from LINK, so holding 10 LINK and zero native coin does not fund a transfer. The wallet’s network switch changes the ledger queried and the fee asset shown. It also changes the token contract receiving the call.

A standard wallet send stays within one chain. Moving LINK from Ethereum to Base or Arbitrum requires a separate cross-chain route such as Chainlink CCIP through Transporter or the network’s supported bridge. That is a different operation with its own source and destination choices. Select the ordinary send flow only when the LINK already sits on the recipient’s accepted chain.

Contract identity separates one LINK balance from another

A LINK contract is the network-specific ledger the wallet calls, and its address distinguishes the asset from every other token entry.

On Ethereum Mainnet, LINK uses 0x514910771AF9Ca656af840dff83E8264EcF986CA. Arbitrum One uses 0xf97f4df75117a78c1A5a0DBb814Af92458539FB4, while Base uses 0x88Fb150BDc53A65fe94Dea0c9BA0a6dAf8C6e196. Each address has 40 hexadecimal characters plus the 0x prefix, giving 42 displayed characters. All three deployments use 18 decimals. Importing the Ethereum contract while viewing Base will not reveal the Base balance because each chain keeps independent contract storage. Polygon adds another distinction: bridged LINK and ERC-677-compatible LINK use separate contracts, so an application request for ERC-677 LINK identifies the required token.

LINK follows the ERC-20 interface with ERC-677 functionality. One LINK equals 1,000,000,000,000,000,000 Juels, so the contract records 18 decimal places. Wallets convert that integer balance into the readable amount. The token contract refuses transfers to its own address and to the zero address, giving two protocol-level rejection cases before a balance can settle.

Confirmation changes balances and records a Transfer event

A confirmed LINK send is a token-contract state change, not a native-coin payment to the recipient.

The wallet builds an ERC-20 transfer call addressed to the LINK contract on the selected chain. Its first 4 calldata bytes identify transfer(address,uint256); the recipient occupies one 32-byte ABI word and the amount occupies another 32-byte word. Standard transfer calldata therefore totals 68 bytes. The transaction’s native value stays at 0, while the LINK amount sits inside calldata as an integer measured in Juels. After execution, the contract subtracts the amount from the sender’s LINK balance, adds it to the recipient’s balance and emits one Transfer event containing the sender, recipient and amount.

Gas follows another path. On an EIP-1559 chain, a type 2 transaction carries a maximum fee per gas and a maximum priority fee per gas. The chain charges gas used at the effective rate and returns unused allowance. LINK’s contract does not deduct the network fee from the token amount, so a direct transfer of 2 LINK credits 2 LINK when the call succeeds. Before signing, compare the confirmation screen’s account, network, contract interaction, recipient, amount and fee asset. Those six fields describe the action more precisely than the LINK ticker alone. Confirmation should proceed after the network and contract match the receiving instruction.

On-chain verification outranks the wallet activity label

On-chain verification is the receipt and token event recorded by the selected network, and it resolves a delayed or incomplete wallet display.

Copy the transaction hash after broadcast. An EVM transaction hash contains 32 bytes and appears as 64 hexadecimal characters after 0x, for 66 displayed characters. Open the explorer for the chosen chain: Etherscan for Ethereum, Arbiscan for Arbitrum, BaseScan for Base or PolygonScan for Polygon. A successful receipt identifies the block, sending address, LINK contract and gas paid. The Transfer event then identifies the recipient and token amount. Check both records because the transaction’s "to" field is the LINK contract, not the final token recipient.

Balance verification uses the same chain and contract. The ERC-20 balanceOf function reads one account’s stored amount without sending another transaction. If the event shows the expected recipient and amount, the transfer has settled even when MetaMask has not indexed the token. Wait for the recipient’s required confirmation depth when a custodial deposit defines one. A dedicated page examines Chain link start with eligibility checklist.

Restoring a missing balance after a network mismatch

A missing LINK balance is usually a view-selection problem when the transaction succeeded on a different EVM network controlled by the same account.

Start from the 66-character transaction hash, identify its chain and note the recipient in the Transfer event. Then switch MetaMask or Rabby to that chain and import the matching LINK contract. A network switch changes the balance query; it does not create a second transfer. If a Ledger account supplied the address, reconnect the same account path through the wallet interface before checking. The same 20-byte EVM address can appear on Ethereum, Base and Arbitrum, yet each chain returns its own LINK balance from its own contract.

When the destination is another self-custodied EVM account from the same recovery phrase or key, controlling that address lets the owner view and send the received LINK after adding the correct network and gas asset. Fund the address with ETH on Base, Arbitrum or OP Mainnet, POL on Polygon or AVAX on Avalanche before making a new transaction. A bridge becomes relevant only if the asset must return to a different chain. Use Chainlink CCIP through Transporter or a route the destination supports; switching the wallet network alone never changes the chain holding the tokens.

A custodial deposit changes the recovery path. If the transaction reached a platform-controlled address through a network the platform did not accept, the wallet owner cannot switch that platform’s internal ledger. Provide its operator with the transaction hash, chain ID, recipient and LINK contract so it can evaluate crediting. The outcome follows the platform’s supported-network process.

If the Transfer event names an unintended address outside your control, the ERC-20 contract has no reversal command. Recovery remains a display fix only when the recipient address is controlled and the network is the mismatched field.