Chainlink

Chainlink is a network of independent node operators that delivers outside data to smart contracts (price feeds, proof of reserve and similar services) and, through CCIP, carries tokens and instructions from one blockchain to another. CCIP stands for Cross-Chain Interoperability Protocol. It is one product in a larger platform, but it is the part most people meet when they search for a Chainlink bridge.

Two organizations sit behind the brand. The Chainlink Foundation is the party to the terms of service for chain.link and its associated services, according to version 6.0 of those terms, effective 18 August 2026. Chainlink Labs is the main developer; its own site describes a team of more than 600 developers, researchers and capital markets specialists. The structured data on chain.link names Sergey Nazarov and Steve Ellis as co-founders. Neither organization publishes a registered address on the pages we checked, and the terms do not name the Foundation's place of incorporation.

The network's token is LINK. In CCIP it is one of the accepted ways to pay fees, and paying in LINK costs about 10% less than paying in a chain's native gas token or another accepted asset, according to the CCIP billing page.

CCIP moves a message along a lane, a configured route from one source chain to one destination chain. The documentation breaks every transfer into four steps: send, verify, index and execute.

Tokens move through token pools, contracts that the token issuer deploys on each chain. A pool either locks the tokens on the source chain and releases them on the destination, or burns them and mints new ones, depending on how the issuer set it up. Under the Cross-Chain Token standard, issuers register and manage their own pools without needing Chainlink's approval, and pointing a pool to the zero address removes the token from CCIP. Pools enforce per-chain rate limits, so an issuer can cap how much value crosses a lane in a given period.

• Send: an app or user calls the Router contract on the source chain, pays the fee, and the token pool locks or burns the tokens.
• Verify: Cross-Chain Verifiers (CCVs) watch the source chain, wait for finality and sign attestations. The default Committee Verifier, run by 16 independent node operators, is always included; issuers and apps can require additional CCVs, including ones they run themselves.
• Index: an optional indexer collects the attestations in one place.
• Execute: anyone can submit the message and its attestations on the destination chain. Chainlink runs a default executor, but delivery does not depend on it.

By default a verifier waits for full finality on the source chain before it signs. CCIP 2.0 lets issuers opt into faster-than-finality transfers for smaller amounts, with separate rate limits and higher fees to price the risk that a block is reorganized. The Router address stays fixed across upgrades, while the OnRamp and OffRamp contracts behind it can be swapped.

A CCIP transfer has up to four cost components: a network fee set by Chainlink, an executor fee that covers destination-chain gas, any fee the token pool charges, and fees for any extra verifiers. The network fee is the only part with a published flat rate. Token pool fees are set by each issuer and can be a dollar amount or a percentage of the transfer, and third-party verifiers set their own prices.

The executor fee is the destination gas limit plus fixed overheads, multiplied by the destination gas price, so it rises when the destination chain is busy. Wallets and apps that embed CCIP may add their own charges on top; the CCIP documentation does not cover those.

Our count of the CCIP mainnet directory on 25 October 2026 found 78 networks, from Ethereum, Arbitrum, Base, Solana, Aptos and TON to bank-oriented networks such as Canton. Chainlink's own marketing pages give a rounder figure. A network being listed does not mean every token can move between every pair of chains: each token is enabled lane by lane by its issuer, and the directory lists the tokens and lanes for each network.

The service limits for CCIP 2.0 lanes on EVM chains cap a message at 32 kilobytes of data and one token per message. The default execution gas limit is 15 million on most destination chains and 6 million on Unichain. HyperEVM carries a separate warning about data availability during RPC downtime.

The documentation also flags private and permissioned networks. There, CCIP relies on a single centralized RPC provider rather than independent nodes, and Chainlink states that a compromised provider could manipulate transaction data, up to and including theft of bridged funds. Anyone holding a token bridged to or from such a network carries that extra exposure.

CCIP's security rests on attestations, not on the destination chain checking a proof. A message executes when at least a quorum of the 16 Committee Verifier operators has signed it, plus any additional verifiers the lane, token pool or receiving contract requires. That is a committee model. Adding independent verifiers raises the number of parties an attacker would have to compromise, but it does not change the kind of trust involved. For how this design compares with canonical and other committee bridges, see how Chainlink CCIP compares with other crypto bridges.

An emergency brake sits on top. The RMN contract keeps a list of cursed chains or lanes; while a curse is in place, sends and executions involving them revert. At the 2023 launch Chainlink described a separate Risk Management Network as a second check on transfers; the CCIP 2.0 architecture page describes the RMN contract only as an onchain emergency safeguard and does not say who may set or lift a curse.

Upgrades are the other trust point. When CCIP launched in July 2023, Chainlink said security-critical configuration changes and upgrades had to pass through a timelock during which a quorum of node operators could veto them, or be approved explicitly by that quorum. We did not find a restatement of that rule in the CCIP 2.0 documentation, so it should be read as the launch-era design.

• Bug bounty: Chainlink's Immunefi program pays up to $3 million for critical smart contract findings. We did not confirm which CCIP contracts are in its scope.
• Shared responsibility: Chainlink's service responsibility page says app developers, token issuers and chain teams remain responsible for their own audits, configuration and monitoring, and that support for a chain or token is not an endorsement.
• Incidents: we found no exploit of CCIP itself in the DefiLlama hacks database or Chainlink's documentation as of October 2026. A bug in a token issuer's own pool or receiving contract would sit outside that record.

Every CCIP message has an ID and appears in the CCIP Explorer at ccip.chain.link, which shows its status on both chains. Chainlink's default executor tries to deliver every message sent with it. If execution fails, for example because the receiving contract ran out of gas, the message sits in a FAILURE state; if no executor was chosen, it stays UNTOUCHED.

In both cases manual execution is open to any account. The caller submits the encoded message and its attestations to the destination OffRamp contract, and no special role is needed. A failed message has to be retried after whatever caused the failure is fixed.

Retail users rarely call CCIP directly. They reach it through an app that integrates it, such as the Transporter bridging app built with the Chainlink Foundation, or a token issuer's own interface. Before bridging, check the app's spending approvals the same way you would for any contract (how token approvals work).

CCIP has gone from a four-chain early-access launch in 2023 to a second-generation design aimed at banks and asset issuers.

• 17 July 2023: CCIP enters mainnet early access on Avalanche, Ethereum, Optimism and Polygon, with Synthetix live and Aave integrating it.
• 24 April 2024: general availability; any developer can use it without permission on nine chains, including Arbitrum, Base and BNB Chain.
• June to September 2026: in the four months before the 2.0 launch, by Chainlink's account, more than $15 billion in token value migrates to CCIP, including BitGo's WBTC, Coinbase's cbBTC and Kraken's kBTC.
• 28 September 2026: CCIP 2.0 goes live, adding issuer-run verifiers, built-in compliance controls through Chainlink's Automated Compliance Engine and configurable settlement speeds.