Chain link eligibility is determined by wallet, network and gas readiness

One ticker, two different assets

One matching ticker does not establish eligibility because LINK identity comes from its network and 20-byte contract address together.

Wallet interfaces such as MetaMask display a symbol and decimal-formatted balance, yet those labels are presentation data supplied by a token contract. An EVM address contains 20 bytes and appears as 40 hexadecimal characters after the 0x prefix. The wallet must therefore match the chain, the checksummed address and the application’s accepted asset. Adding a custom token only reveals a balance; it does not move LINK or change its contract. This distinction prevents the most common setup error: selecting a familiar ticker on the wrong deployment.

Chainlink publishes separate LINK contracts for Ethereum, Arbitrum One, Base and other supported networks. An application may accept only one of them. Treat the contract address as the asset identifier and the chain ID as its operating environment. That pair completes the first Chain link eligibility test.

Two balances fund one onchain action

Two balances fund most LINK actions: LINK supplies the token amount and the chain’s native coin pays execution gas.

Ethereum, Arbitrum One, OP Mainnet and Base use ETH for gas. Polygon PoS uses POL, Avalanche C-Chain uses AVAX and BNB Chain uses BNB. LINK never substitutes for those native balances in an ordinary wallet transaction, even when LINK pays for a Chainlink service inside the application. The cost driver is execution: a direct transfer uses one contract call, while an approval followed by an application call creates two network fees. The wallet’s quote is denominated in the native coin, so funding decisions must use gas units and the offered fee per gas rather than the LINK amount alone.

Which network must the wallet use?

One exact network qualifies: the chain selected by the receiving contract or application, not another EVM network with LINK.

A wallet address can look identical on Ethereum and its EVM-compatible networks because the same key derives the same 20-byte address. Balances and contracts remain separate state. LINK on Ethereum does not become LINK on Arbitrum One merely because MetaMask shows the same account. The network selector, connected RPC and chain ID must all point to the destination environment before the transaction is prepared. WalletConnect only carries the session between a wallet and an application; the requested chain still determines where the signature executes. The application should present that chain in its transaction request.

Cross-chain movement is a separate transaction path. Chainlink CCIP and applications such as Transporter transfer supported tokens between named source and destination chains. After delivery, eligibility is judged again on the destination: accepted LINK contract, available LINK amount and native gas balance.

Seven chain IDs worth recognizing

Seven durable identifiers separate common LINK environments before any transaction leaves the wallet.

Ethereum uses chain ID 1, OP Mainnet uses 10 and BNB Chain uses 56. Polygon PoS is 137, Base is 8453, Arbitrum One is 42161 and Avalanche C-Chain is 43114. These identifiers are not balances or token contract addresses. They tell an EVM wallet which replay-protected signing domain it is using. EIP-155 binds a chain ID into the signed transaction. A request labeled "Ethereum" with chain ID 42161 is therefore an Arbitrum One request. Reading the numeric ID before signing resolves ambiguous network names and exposes an incorrect wallet configuration without relying on a ticker.

18 decimals and the ERC-677 contract

18 decimal places mean 1 LINK equals 1,000,000,000,000,000,000 Juels in contract storage.

LINK follows ERC-677, an extension inheriting ERC-20 functionality and adding a data payload to token transfers. Standard wallet transfers still use familiar token methods, while some Chainlink service contracts use the additional transfer-and-call behavior. Decimal precision affects display and input conversion, not network eligibility by itself. A wallet showing 0.5 LINK sends 500,000,000,000,000,000 base units. Smart contract checks operate on those integer units. The application must still accept that contract on that chain, and its interface must encode the intended amount without rounding away needed units.

Contract compatibility matters most on routes with multiple LINK representations. BNB Chain distinguishes bridge-provided LINK from the ERC-677 LINK required by Chainlink services and uses Chainlink PegSwap for conversion. Matching decimals and symbols therefore does not replace a contract-level match.

Wallet authority and contract-account limits

One valid signature authorizes an externally owned account, while a Safe smart account enforces its configured owner threshold.

MetaMask manages or connects to EVM accounts and Ledger authorizes EVM transactions through that interface. The address holding LINK must be the address the signer controls. Importing a watch-only address displays balances without adding signing authority. A Ledger-backed address also requires the device to confirm the call, while the browser wallet supplies network data and broadcasts the signed transaction.

WalletConnect provides a session transport, not custody or a substitute signature. The connected wallet still applies its own account and chain rules.

Safe changes the workflow because its address is a smart contract account. A configured threshold decides how many owners must approve before execution, and one owner’s confirmation does not satisfy a 2-of-3 Safe. The target application must also support contract-wallet calls and preserve the correct sender context. Gas funding then follows the Safe’s execution design: the account, an owner or a relayer arrangement pays under the configured transaction path. Batching can combine several operations, but simulation must cover the complete batch. A 2-of-3 Safe reaches its execution threshold only after the second required confirmation, as covered in Chain link for beginners basics.

How much native gas is enough?

One gas estimate, plus a stated buffer, sets the native-coin funding target immediately before signing.

Ethereum-style fees use gas consumed multiplied by the effective fee per gas. Under EIP-1559, the effective rate combines the block’s base fee with a priority fee, capped by the transaction’s maximum fee. One gwei equals 0.000000001 ETH. The wallet balance must cover the gas limit multiplied by the maximum fee per gas when the transaction is validated. Estimates change with contract logic and network demand, while unused gas below the limit is not charged. Estimate every planned call, not only the final LINK transfer.

In this hypothetical example, the changing inputs are a gas limit of 70,000, base fee of 20 gwei, priority fee of 2 gwei, maximum fee of 30 gwei and buffer of 20%. The expected effective rate is 22 gwei, producing an expected charge of 1,540,000 gwei or 0.00154 ETH at the stated gas limit. Funding against the 30 gwei maximum requires 2,100,000 gwei or 0.0021 ETH. Applying the 20% buffer adds 0.00042 ETH. The wallet therefore needs 0.00252 ETH for this case, before any separate approval transaction.

Approvals add a second transaction

Two transactions enter the workflow when an application requests an ERC-20 approval before its LINK action.

The first call sets an allowance for a named spender contract and consumes native gas; it does not transfer LINK by itself. The second call uses part or all of that allowance and consumes gas again. A direct transfer is one token transaction, while ERC-677’s transferAndCall combines a token transfer with a data payload in one call when the receiving contract supports it. Estimate the path shown by the application. If approval already exists at a sufficient amount, the application requests only the consuming call; if it is insufficient, the gas balance must cover both transactions.

Edge cases before the signature

Three edge cases deserve a final check: contract wallets, cross-chain representations and application-specific token rules.

Contract wallets such as Safe may fail preflight checks designed only for externally owned accounts, even though the wallet controls sufficient LINK and gas. The application decides account-type support. A successful wallet connection through WalletConnect proves session access, not contract compatibility. Simulation should reach the intended contract method from the exact Safe address, as broken down in Chain link checklist.

Cross-chain representations require the destination contract, not just an arrival transaction. Chainlink CCIP routes and Transporter handle supported transfers, yet the receiving application may name one LINK contract. A completed bridge step therefore changes location; it does not grant universal acceptance across every protocol on that chain.

Application rules sit above wallet readiness. Chainlink Automation, staking interfaces and third-party DeFi contracts each define supported networks, payment assets, minimum amounts or access conditions for their own action. Those conditions are separate from the base eligibility described here. The complete Chain link eligibility decision is positive only when the wallet controls the account, the chain ID matches, the LINK contract is accepted and native gas covers the entire call sequence. A 2-call path needs funding for both calls.