Skip to main content

CCIP

Use the Bloctopus platform to create CCIP connections across your Bloctopus networks and external chains.

I. Set up CCIP connections​

Select networks already running in your account or onboard external networks.

For external networks and public testnets, provide:

  • Fork Type — choose from the dropdown to indicate the chain type; select 'Not Forked' for non forked networks.
  • ChainID — the chain ID of your EVM-based chain
  • Private key of a funded account
  • Faucet URL exposing a /fund POST endpoint that accepts {"address": "eth_key", "amount": 1}
  • RPC URL
  • WebSocket URL
Network Interconnection

All chains listed in the UI are automatically interconnected, with bidirectional lanes between every pair. The first chain is the Home Chain hosting Chainlink DON configuration contracts; every chain (including the Home Chain) deploys the CCIP contracts required for cross-chain messaging. Select minimum 2 chains.

Bloctopus deploys all required contracts and spins up a 4-node Chainlink DON configured for CCIP. For details on the underlying infrastructure, see the CCIP Kurtosis package.

II. Use deployed CCIP lanes​

Once deployed, you can find key information about your CCIP network displayed in the network details view:

Contract addresses​

Essential for Basic Use:​

These are required for standard CCIP operations like cross-chain messaging and token transfers:

  • Router Address — Main contract for routing cross-chain messages
  • Chain Selector — Unique ID for the chain within CCIP

Advanced Infrastructure (Optional for Customization):​

These contracts support advanced features, troubleshooting, or deeper customization. They are typically used when building more complex setups, integrating tokens, or customizing network behavior:

  • FeeQuoter — Provides fee estimates. Useful for applications showing fee previews before sending messages
  • OnRamp / OffRamp — Gateways for sending and receiving cross-chain messages. Sometimes interacted with directly for testing or custom message flows

Extra (Not displayed in the UI but available as part of bloctopus deployment):

  • NonceManager — Prevents replay attacks. Rarely needed unless managing low-level message flow
  • RMN Proxy — Proxy for the Risk Management Network. Used when creating or managing token pools
  • TokenAdminRegistry — Manages token admin roles. Used when assigning or modifying token permissions
  • RegistryModule — Manages modular extensions. Relevant when adding custom logic or features to the network
  • TokenPoolFactory — Deploys token pools. Used when launching new token liquidity pools

(optional) - deployed when operating on non-forked networks only

  • LinkToken — LINK token address. Required for paying CCIP fees
  • WETH9 — Wrapped native token. Used for operations requiring wrapped ETH on the chain
Contract Ownership

All contracts are deployed using the private key linked to the user account that created the network (exposed in each network details), allowing easy future modifications.

Follow the official CCIP guide for token transfers and other operations. Ensure you reference the router addresses and chain selectors shown in the Bloctopus UI.

The CCIP details page also links to each DON node's Operator GUI, where you can view node settings, ccip transactions, keys, and manage or run jobs as needed.

Credentials (Node UI & API Auth):

CCIP UI (Coming soon!)​

On the CCIP Network Details page, you'll find a link to our CCIP UI directly connected to bloctopus CCIP contracts and underlying bloctopus testnets, allowing you to:

  • Deploy CCT Tokens, BnM, and LnR with ease
  • Perform cross-chain transfers through an intuitive interface
  • Access advanced configuration details for the network
  • Experiment with advanced message sending and other cross chain messaging features