CCIP Bridge
Purpose and Scope
Section titled “Purpose and Scope”CCIP Bridge handles cross-chain routing of wrapped assets between supported chains using Chainlink CCIP.
Use this page for chain-to-chain wrapped transfers (for example Ethereum ↔ Base or Ethereum ↔ Solana or Solana ↔ Base).
For native Bittensor asset bridging (TAO/ALPHA), use Bridge.
Supported Networks
Section titled “Supported Networks”Current routes are available across supported lanes on:
- Ethereum
- Base
- Solana
Route availability can vary by asset and lane configuration.
Bridge vs CCIP
Section titled “Bridge vs CCIP”| Feature | Native Bridge | CCIP Bridge |
|---|---|---|
| Primary Purpose | Bittensor ↔ Ethereum native/wrapped conversion | Wrapped asset routing across supported chains |
| Token Type | Native ↔ Wrapped | Wrapped ↔ Wrapped |
| Solana Support | No (native corridor) | Yes (supported CCIP lanes) |
End-to-End Flow
Section titled “End-to-End Flow”- User selects source chain, destination chain, and supported wrapped asset.
- User receives fee quote (source gas, CCIP fee, destination execution cost).
- User approves/signs on source chain.
- DON (Chainlink’s Decentralized Oracle Network) validates and routes the message.
- Destination delivery executes according to the configured token pool model (release or mint).
- Transaction completes after destination-chain confirmation.
Fee Model
Section titled “Fee Model”| Component | Description |
|---|---|
| Platform Fee | VoidAI service fee (if applicable to route) |
| Source Gas | Execution fee on source chain |
| CCIP Fee | Chainlink CCIP protocol routing fee |
| Destination Execution Cost | Settlement execution fee on destination chain |
Final costs vary with lane, congestion, and token configuration.
Timing and Finality
Section titled “Timing and Finality”- Typical completion window: 20-25 minutes.
- Delays can occur during high source/destination congestion or lane-level backpressure.
- Transfer is final only after destination settlement confirmation.
Transaction Lifecycle
Section titled “Transaction Lifecycle”| Status | Description | User Action |
|---|---|---|
INITIATED | Request created | Wait for source-chain signing/submission |
PENDING_SOURCE | Awaiting source-chain confirmation | Monitor source transaction |
CCIP_PROCESSING | DON is validating and routing cross-chain message | No action needed |
PENDING_DESTINATION | Destination settlement executing | Wait for destination confirmation |
COMPLETED | Destination settlement confirmed | Verify destination balance |
FAILED | Terminal route/settlement error | Retry with new request or contact support |
Security and Trust Model
Section titled “Security and Trust Model”- Message routing and risk checks are enforced by Chainlink DON.
- Supported assets and lanes are allowlisted through route configuration.
- Destination settlement requires validated cross-chain proofs/messages before execution.
Troubleshooting
Section titled “Troubleshooting”- Confirm the selected lane supports your token and chain pair.
- Ensure sufficient source-chain gas balance before submitting.
- Track status via transaction history and chain explorer links.
- If status remains non-terminal beyond expected time, escalate with transaction ID and source hash.