How does Avalanche ICM work?
How Avalanche ICM Works
Avalanche ICM (Interchain Messaging) is a foundational protocol enabling seamless cross-chain communication between Layer 1 (L1) blockchains launched within the Avalanche ecosystem. It’s designed to facilitate robust interoperability, liquidity flow, and composability across independently operating Avalanche L1s.
Core Principles
- Cross-Avalanche L1 Communication: Avalanche ICM allows any two Avalanche L1s to send and receive messages directly without going through a central relay.
- Developer-Oriented: VM developers can implement custom communication protocols using ICM, significantly easing integration of complex cross-chain operations.
- Decentralization and Customization: Each L1 can have its own staking, gas, permissions, and validator set—all while remaining interoperable with other Avalanche chains through ICM.
Technical Architecture
Messaging Flow
There are four main stages in cross-Avalanche L1 communication:
- Signing: Messages generated on the origin L1 are signed by its validators using BLS signatures. Each validator has a BLS key pair for this purpose.
- Signature Aggregation: Multiple validator signatures are aggregated into a compact multisignature, making verification efficient even with large validator sets.
- Delivery: The message is delivered to the target L1, without passing through a central service, preserving both scalability and privacy when needed.
- Verification: The target L1 uses the aggregated signature to verify the authenticity and integrity of the received message.
This structure supports:
- Arbitrary data payloads (any byte array)
- Oracle data transmissions, general state sharding, and token transfers between Avalanche L1s
Smart Contract Layer
On EVM-compatible Avalanche L1s, ICM is implemented through a set of Solidity contracts, most notably the TeleporterMessenger. This contract abstracts the cryptographic signing/aggregation/verification process, providing a simple API:
sendCrossChainMessage(): Called by contracts on the origin chain.
receiveCrossChainMessage(): Called by relayers/contracts on the destination chain.
Developers only need to interact with these methods, instead of handling the underlying cryptographic details.
Benefits and Use Cases
- Shared Liquidity: New L1s can tap into aggregate liquidity across Avalanche L1s from day one.
- Custom Chain Design: Chains can tailor staking, fee models, governance, and permissions, then interoperate instantly via ICM.
- No Central Bottlenecks: Since there’s no central hub, chains are free from single points of failure or congestion.
Real-World Applications
Projects like DeFi Kingdoms, Gunzilla, MapleStory, and Shrapnel have deployed their own Avalanche L1s and benefit from ICM’s architecture for fast, open, and private cross-chain operations. The protocol also unlocks modular infrastructure—for instance, oracles or state sharding schemes that work uniformly across chains.
Summary Table
+3