Chain to chain,natively,no intermediaries
An Interchain Messaging (ICM) message carries an aggregate signature from the source chain's validators, verified against the P-Chain's validator registry. No committee, no custodian.
- Messaging
- Protocol-native
- Attestation
- Source validator set
- Verification
- P-Chain registry
Documentation
04Academy
03How it works.The primitives underneath.
01
Authenticated messaging
Messages carry aggregate BLS signatures from the source validator set, verified at the destination against the validator registry on the P-Chain.
02
Native token transfer
Interchain Token Transfer (ICTT) moves tokens between L1s over ICM, with contracts you deploy and control.
03
Permissionless relay
Messages are carried by relayers anyone can run. The destination chain verifies the source validators' signatures, never the messenger.
Where it is used.Institutional patterns built on it.
Liquidity access
Public liquidity from a private chain.
A regulated business runs on its own chain, but the stablecoin liquidity it settles against lives on the public C-Chain. Crossing that boundary usually means trusting a third-party bridge, which adds a new custodian and a new counterparty to every settlement.
A permissioned business chain reaches public stablecoin liquidity with no custodial bridge in the settlement path.
Dedicated L1 · ICM · C-Chain liquidity
- Bridging
- Protocol-native
- Custody risk
- None in path
- Finality
- Sub-second
Token issuance
One token, issued once, native everywhere.
A token issued on one chain needs to circulate on others, and every third-party bridge that wraps it mints a liability the issuer does not control. Multiple wrapped versions fragment liquidity and put the issuer's name on assets it never approved.
ICTT keeps the home contract with the issuer and deploys native remotes on every destination chain.
ICTT · Home contract · Native remotes
- Wrapped versions
- None
- Supply
- Home-anchored
- Attestation
- Source validators