Technology
Internet Computer Chain Fusion Explained
Most cross-chain movement runs through bridges — smart contracts that lock tokens on one chain and print a wrapper on another. Chain Fusion is a different approach: the Internet Computer reads, holds, and signs for other chains directly, using threshold signatures instead of bridges. Here is how it works and why it changes what an app can do.
August 16, 2026 · 7 min read
The bridge problem
A traditional bridge takes your Bitcoin, locks it in a smart contract controlled by a custodian, and issues a wrapped token like wBTC in exchange. That wrapper is a promise — it is only worth as much as the people holding the underlying coins. History has been unkind: billions of dollars have been stolen from bridges because one buggy contract or one compromised key controlled an enormous pile of locked assets.
Chain Fusion removes the middleman entirely. Instead of locking Bitcoin somewhere and trusting someone, the Internet Computer itself signs Bitcoin transactions. No single person, company, or node holds the private key — a subnet collectively signs using threshold cryptography.
Chain-key signatures
The technical foundation is chain-key cryptography. The protocol derives a unique key for each canister, splits it across all the nodes of a subnet, and lets those nodes produce a signature together — without any node ever seeing the complete private key. A subnet can hold a Bitcoin address, an Ethereum account, or a Solana wallet, and transact on those chains as if it were a regular user.
- Threshold ECDSA — secp256k1 keys for Bitcoin, Ethereum, all EVM chains, Filecoin, and Cosmos.
- Threshold Schnorr — BIP340 for Bitcoin Taproot and Ordinals; Ed25519 for Solana, TON, Polkadot, Cardano, and NEAR.
Because the key never exists in one place, there is nothing to steal. A bridge's single point of failure becomes a distributed signing service.
Chain-key tokens: ckBTC and ckETH
This is what makes chain-key tokens possible. ckBTC is not a wrapped Bitcoin managed by a third party — it is a 1:1 on-chain representation of Bitcoin held by a canister-controlled address on the Bitcoin network. The minting and burning happen entirely on the Internet Computer. Send Bitcoin to your canister address, and ckBTC is minted into your account. Send ckBTC out, and the canister signs a real Bitcoin transaction to release the BTC.
The same architecture powers ckETH and ckERC-20 tokens. These chain-key tokens implement the ICRC-2 standard, so they move and trade at Internet Computer speed — seconds, not minutes — while remaining redeemable 1:1 for the underlying asset.
How a canister connects to other chains
Two layers make it work. The protocol layer runs adapters — for Bitcoin, nodes run a Bitcoin adapter that speaks the peer-to-peer protocol and keeps a canister informed of the latest Bitcoin state. The signing layer lets canisters derive keys and request threshold signatures from the protocol.
- Bitcoin API — the Bitcoin canister exposes get UTXOs, get balance, and send transaction directly at protocol level.
- EVM RPC canister — a typed interface to Ethereum and EVM-compatible chains, querying multiple RPC providers and returning consensus results.
- SOL RPC canister — the same for Solana.
- HTTPS outcalls — any chain with an HTTP API can be integrated where a direct adapter does not exist.
What apps become possible
Removing the bridge opens patterns that are difficult or impossible otherwise:
- A multichain wallet — one canister controls addresses on Bitcoin, Ethereum, and Solana at the same time, with a web frontend served from the chain itself.
- Trustless automation — a canister watches an Ethereum contract and triggers loan liquidations or batch settlements automatically, no external keeper service required.
- Bitcoin-secured lending — use Bitcoin as collateral, held in a canister-controlled address, and borrow an ICRC-2 stablecoin against it.
- Tamperproof frontends — an immutable UI for an Ethereum smart contract, hosted on-chain as a certified asset.
Why developers notice the difference
On most chains, a cross-chain app means onboarding the user into a wallet, buying a native gas token, and trusting a bridge contract with their funds. On the Internet Computer, canisters pay their own cycles — the reverse gas model — so a user can interact with a cross-chain app through a standard browser with no wallet installation and no gas.
That combination — web-speed finality, low-cost compute, and native multi-chain signing — is what makes Chain Fusion one of the most searched ICP concepts and one of its most genuinely distinct capabilities.