Chainlink CCIP

The Chainlink Cross-Chain Interoperability Protocol (CCIP) is the standard for blockchain interoperability. CCIP enables developers to build secure cross-chain applications that can transfer tokens, send messages, and initiate actions across blockchains.

Through the Cross-Chain Token (CCT) standard, CCIP allows token developers to integrate new and existing tokens with CCIP in a self-serve manner within minutes—without requiring vendor lock-in, hard-coded functions, or external dependencies that limit future flexibility.

CCTs support:

  • Self-serve deployments with full control and ownership

  • Zero-slippage transfers across supported chains

  • Enhanced programmability via configurable rate limits

  • Smart Execution, ensuring reliable cross-chain transaction delivery

CCIP is powered by Chainlink Decentralized Oracle Networks (DONs)—a proven infrastructure that has secured tens of billions of dollars and enabled over $21 trillion in on-chain transaction value.


Overview of CCIP and HTS Compatibility

On Hedera, CCIP extends interoperability between Hedera’s Hashgraph network and EVM-compatible blockchains such as Ethereum. It integrates seamlessly with both the Hedera Token Service (HTS) and standard EVM tokens (ERC-20 and ERC-721), allowing developers to bridge data, tokens, and logic across ecosystems.

Through CCIP, developers can:

  • Send and receive arbitrary messages across chains

  • Execute programmable cross-chain logic using Chainlink’s oracle network

  • Experiment with LINK, Wrapped HBAR (WHBAR), or ETH as fee tokens

  • Prepare for future Cross-Chain Token (CCT) transfers once fully enabled on Hedera

⚠️ Note: Cross-Chain Token (CCT) transfers on Hedera are still in progress on testnet. The current demos focus on message passing between Hedera Testnet and Ethereum Sepolia.


Why CCIP Matters

CCIP provides a unified framework for cross-chain connectivity—replacing the need for custom bridges with a decentralized standard backed by Chainlink’s proven security model.

By integrating CCIP, Hedera developers can create applications that benefit from:

  • Secure message delivery via decentralized oracle networks

  • Universal token compatibility through the CCT standard

  • Reduced integration overhead through SDK tooling and no-code deployment options

  • Future-proof design with no vendor lock-in

This aligns with Hedera’s mission to enable high-throughput, low-fee interoperability across distributed ledger technologies.


Key CCIP Developer Tools

  • CCIP Official Documentation — Start integrating CCIP into your cross-chain application.

  • CCIP Token Manager — A web interface for deploying and managing Cross-Chain Tokens (CCTs) with no-code guided configuration.

  • CCIP SDK (JavaScript) — A development kit for building JavaScript dApps that perform token transfers or cross-chain messaging.


Getting Started with CCIP on Hedera

You can explore CCIP on Hedera using the Hedera CCIP Demo Repository, which demonstrates bi-directional cross-chain messaging between the Hedera Testnet and Ethereum Sepolia.

These examples use the Chainlink CCIP JavaScript SDK and show how to configure networks, manage fee tokens, and send cross-chain messages.

Setup

  1. Install dependencies

    pnpm install
  2. Configure your environment

    cp .env.example .env

    Add your Hedera Testnet private key:

    PRIVATE_KEY=0x...
  3. Run a demo

    pnpm run demo:hedera-sepolia-link

Available Demos

Direction
Payment
Command
Description

Read-only

pnpm run demo:readonly

Query CCIP configuration without executing transactions.

Hedera → Sepolia

LINK

pnpm run demo:hedera-sepolia-link

Send a message using LINK as the fee token.

Hedera → Sepolia

WHBAR

pnpm run demo:hedera-sepolia-whbar

Send a message using Wrapped HBAR for fees.

Sepolia → Hedera

ETH

pnpm run demo:sepolia-hedera

Send a message from Sepolia to Hedera using ETH for fees.

💡 Tip: Wrap HBAR before running WHBAR examples:

pnpm run wrap-hbar

All demos operate on testnet and are designed for educational purposes only. They are not audited and should not be used in production.


Network Configuration

Hedera Testnet

ADD HEDERA TESTNET

Name
Value

Network Name

Hedera Testnet

RPC Endpoint

https://testnet.hashio.io/api

Chain ID

296

CCIP Router

0x802C5F84eAD128Ff36fD6a3f8a418e339f467Ce4

Chain Selector

222782988166878823


Ethereum Sepolia

ADD ETHEREUM SEPOLIA

Name
Value

Network Name

Ethereum Sepolia

Chain ID

11155111

CCIP Router

0x0BF3dE8c5D3e8A2B34D2BEeB17ABfCeBaf363A59

Chain Selector

16015286601757825753


Token Addresses

Network
Token
Address

Hedera Testnet

LINK

0x90a386d59b9A6a4795a011e8f032Fc21ED6FEFb6

WHBAR

0xb1F616b8134F602c3Bb465fB5b5e6565cCAd37Ed

Ethereum Sepolia

LINK

0x779877A7B0D9E8603169DdbD7836e478b4624789

⚠️ Note: WHBAR uses 8 decimals, while most EVM tokens use 18 decimals.


Developer Considerations

Decimal Precision

HBAR’s smallest unit is the tinybar (8 decimals). Because CCIP on EVM networks operates with 18-decimal precision, conversions between tinybars and wei-based values may be required. See EVM Differences and Compatibility.

Cross-Chain Fees

Ensure your wallet holds sufficient LINK, WHBAR, or ETH to cover CCIP fees.

Message Timing

Cross-chain message delivery on testnet may take several minutes while the Chainlink oracle network confirms execution.


Test Tokens and Faucets

Network
Token
Faucet

Additional Resources


Summary

Chainlink CCIP establishes a universal standard for secure, decentralized cross-chain interoperability. It brings Hedera into a broader multi-chain ecosystem—enabling applications that move assets, execute logic, and share state across blockchains through a common protocol.

On Hedera, CCIP provides a modular and future-ready foundation for interoperability, supporting HTS and EVM token compatibility under the Cross-Chain Token (CCT) standard. This capability complements other interoperability solutions like LayerZero and Hashport, positioning Hedera as a key network within the interoperable web3 ecosystem.

Last updated

Was this helpful?