Chain Fusion Is Now “Multi-Chain” in ICP’s Dashboard—What Builders Should Actually Change

The change is visible, but mostly semantic

ICP’s dashboard now presents the former Chain Fusion area as Multi-Chain. Its changelog records the navigation rename in 2026, and the live page describes the feature as ICP’s decentralized connection to multiple blockchains through canister-controlled signing, external-chain communication, and chain-key tokens.

That wording matters because it shifts the emphasis from the underlying cryptographic mechanism to the application category developers are building: wallets, asset systems, automated workflows, and cross-chain services.

What developers should update

For documentation and product work, the safest immediate action is terminology maintenance:

• Use “Multi-Chain” when referring to ICP’s dashboard navigation and current product-facing language.
• Keep “Chain Fusion” when discussing the underlying architecture, existing APIs, or established technical literature.
• Update internal links, onboarding text, screenshots, and search terms so users can find the renamed dashboard section.
• Explain that chain-key tokens are not conventional wrapped assets: the dashboard describes them as 1:1-backed assets managed on-chain by ICP smart contracts.

The technical surface remains recognizable. ICP’s developer documentation still describes chain-key signatures, threshold ECDSA and Schnorr, and the Chain Fusion guides for Bitcoin, Ethereum, Solana, and other integrations.

Why the distinction is useful

A naming change can create unnecessary migration anxiety. The current evidence points to a presentation and information-architecture update, not a breaking change. The reviewed sources do not document a new canister interface, changed signing method, or replacement for existing Chain Fusion APIs.

The distinction is especially important for teams using the SOL RPC canister. Its repository continues to provide deployment artifacts, Candid and Wasm links, client examples, and guidance about replicated HTTPS outcalls. Those implementation details remain the source of truth for code, regardless of whether the surrounding dashboard calls the capability Chain Fusion or Multi-Chain.

The practical reading

Treat Multi-Chain as the umbrella label and Chain Fusion as the technical lineage. New users may understand the former faster; engineers still need the latter to locate signing, RPC, canister, and chain-key documentation.

Editorial caveat: This is a dashboard and navigation terminology change. The reviewed sources do not describe a Chain Fusion protocol or API change, so builders should not infer a migration requirement from the rename alone.