Chainlink CCIP

Blockchains do not talk to each other by default. A token on Ethereum cannot appear on another chain unless something carries a message across and both sides trust it. For years the bridges that did this were a favourite target, with single exploits costing hundreds of millions of dollars. Cross-chain protocols such as Chainlink CCIP aim to make that message both reliable and hard to fake.

How cross-chain transfers work

There are two common models:

• Lock and mint. The token is locked in a contract on the source chain and a wrapped copy is created on the destination. The copy is only as good as the lock: if the lock contract is drained, every wrapped copy loses its backing.
• Burn and mint. The token is destroyed on the source chain and the same token is created on the destination by its issuer's own contract. Total supply across chains stays constant, and there is no pool of locked tokens to steal.

A third option, lock and release, keeps the native token in managed pools on each chain and moves value between those pools. It suits tokens that already exist on several chains, at the cost of keeping liquidity in every pool.

Native support means the issuer moves its token through its own token contracts on each chain, so holders get the real token everywhere, not a third party's IOU.

What Chainlink CCIP adds

CCIP carries messages and token transfers between supported chains using decentralized oracle networks, the same kind of infrastructure behind Chainlink's price feeds. Its Cross-Chain Token standard lets issuers make their tokens transferable through CCIP while keeping control of their own token contracts, and it supports rate limits that cap how much value can move in a given period. CCIP also includes independent risk checks that can halt activity if something looks abnormal.

A simple example

A holder has 1,000 tokens on Ethereum and wants them on Arbitrum. She starts a transfer. The token contract burns 1,000 tokens on Ethereum, CCIP carries a verified message to Arbitrum, and the token's own contract there mints 1,000 tokens to her address. Total supply across both chains is unchanged. Had the transfer exceeded the configured rate limit, it would have waited instead of going through.

Why native support matters

Wrapped tokens split liquidity: three bridges can produce three different versions of the same asset on one chain, each with its own risk and its own price. A native token stays one asset everywhere, which keeps prices consistent and makes it simpler for other protocols to accept it, an advantage for composability.

Risks and limits

No cross-chain system is free of risk. The messaging layer, the token contracts on each chain and the chains themselves can all fail. Transfers take time to finalize and can slow down under congestion. Rate limits contain losses but can also delay large, honest transfers. And a token that lives on several chains is exposed to the weakest of them.

Tori Finance has native cross-chain support through Chainlink CCIP. Native support means its tokens move between chains through their own token contracts rather than as wrapped copies created by a third-party bridge.