How Does Chain Fusion Work?
Chain Fusion is ICP's (Internet Computer Protocol) trustless cross-chain infrastructure that enables smart contracts on ICP to directly interact with Bitcoin and Ethereum without traditional bridges. It produces chain-key tokens (ckBTC, ckETH) backed 1:1 by native assets with fast finality and negligible fees. The technology uses novel threshold cryptography where ICP consensus nodes collectively sign cross-chain transactions. While theoretically more secure than multisig bridges, the approach is newer and less battle-tested.
TVL
$25M
Sector
Bridge
Risk Grade
B-
Value Grade
C-
Core Mechanisms
8.1.3
NovelTrustless cross-chain messaging using ICP chain-key cryptography: ICP smart contracts directly sign and submit transactions to Bitcoin and Ethereum
Novel approach using threshold ECDSA signatures from ICP consensus nodes to interact with other chains without traditional bridges
8.2.1
Chain-key tokens (ckBTC, ckETH): 1:1 backed tokens on ICP representing native BTC and ETH, redeemable at any time
Standard wrapped token pattern but backed by chain-key cryptography rather than multisig
8.4.2
ICP nodes connect directly to Bitcoin P2P network and Ethereum via HTTPS outcalls to multiple RPC providers
Bitcoin adapter for native P2P connection; Ethereum via redundant JSON RPC providers (Ankr, BlockPI, Alchemy)
6.4.3
Cross-chain state verification via ICP consensus: subnet nodes independently verify state of connected chains
Custom verification using ICP's BFT consensus as the trust anchor
3.2.1
ICP consensus-level slashing for subnet nodes that misbehave in cross-chain operations
Standard algorithmic slashing at the ICP network level
2.1.1
Negligible transaction fees for cross-chain operations on ICP (cycles-based fee model)
ICP's cycles model makes cross-chain transactions very cheap
How the Pieces Interact
If threshold signature key shares are compromised or ICP subnet consensus is attacked, forged cross-chain transactions could drain all chain-key token reserves
ckBTC and ckETH are only as secure as the underlying chain-key cryptographic scheme; a break in threshold ECDSA would compromise all wrapped assets
Bitcoin state verification depends on ICP nodes running Bitcoin adapters; bugs in the adapter could cause ICP to have incorrect view of Bitcoin state
Ethereum state relies on 3 separate RPC providers; if providers return inconsistent data, ICP must resolve conflicts which could delay or fail transactions
Slashing may not be sufficient deterrent if the value of compromising chain-key tokens exceeds the total slashable stake
What Could Go Wrong
- ICP consensus dependency: Chain Fusion relies entirely on ICP subnet consensus for cross-chain operations; a consensus failure could freeze all bridged assets
- Novel chain-key cryptography: the threshold signature scheme enabling cross-chain transactions is a relatively new cryptographic approach with limited adversarial testing
- Cross-chain bridge risk: despite trustless design, bridge infrastructure remains the most commonly exploited DeFi primitive historically
Chain-Key Cryptographic Compromise
TailTrigger: Threshold ECDSA key shares are compromised through ICP subnet attack, allowing unauthorized signing of cross-chain transactions
- 1.Attacker compromises sufficient ICP subnet nodes to reconstruct threshold ECDSA private key — Attacker can sign arbitrary transactions on Bitcoin and Ethereum using the chain-key
- 2.Attacker transfers all BTC and ETH reserves backing ckBTC and ckETH to attacker-controlled addresses — Chain-key tokens become unbacked; ckBTC and ckETH effectively worthless
- 3.ICP DeFi ecosystem collapses as ckBTC and ckETH are widely used as collateral and trading pairs — Cascading liquidations and protocol failures across ICP DeFi
- 4.ICP network halts cross-chain operations and initiates key resharing — Stolen Bitcoin and Ethereum are unrecoverable; affected users face total loss
Risk Profile at a Glance
Overall: B- (35/100)
Lower score = safer