XCM
Standards/Coordination SystemsCross-Consensus Messaging Format: a universal, versioned message format for expressing instructions between heterogeneous consensus systems (parachains, relay chains, smart contracts, bridges). XCM is a messaging format, not a protocol — it defines what messages mean, not how they are transported. Built around a XCVM (Cross-Consensus Virtual Machine) with a register-based instruction set. Enables trustless asset transfers, remote execution, and cross-chain governance across the Polkadot ecosystem and beyond.
Hybrid Foundation Low capture risk
Links
Details
License https://github.com/polkadot-fellows/xcm-format
Dev Status Active
Owner Polkadot Fellows (polkadot-fellows/xcm-format); originally authored by Gavin Wood / Parity Technologies
Country Global
Start Year 2021
Stack Rust, XCM instructions compile to XCVM bytecode, transport via XCMP, UMP, DMP, HRMP, WebAssembly runtime
Funding Foundation
Last Investigated Mar 10, 2026
Smart Contract Standard Attributes
Permissions Permissionless message sending for whitelisted origins; chain-level governance controls which cross-chain operations are permitted; XCM itself is chain-agnostic
Development Tools Polkadot SDK (formerly Substrate); xcm-simulator for testing; XCM Playground; Chopsticks (local fork testing); polkadot-js API; XCM Executor and Builder libraries
Protocol Maturity / Standardization Production standard across 40+ Polkadot parachains; v4 is the current canonical version; IBC expansion (IBC Eureka) and growing non-Polkadot adoption; more relevant to Polkadot ecosystem than ink! following Polkadot's EVM pivot
Trust Framework Trust-minimized: message validity enforced by Polkadot shared security (relay chain); XCM execution at destination chain is cryptographically verified; no relayer trust required for XCMP; HRMP channels require governance approval
Target Application Domain Cross-parachain DeFi; cross-chain governance and voting; interchain asset transfers; cross-chain NFT operations; sovereign staking; multi-chain DAO coordination; bridge communication
Deployment Model Integrated as a Substrate pallet in each parachain runtime; XCM version negotiation via channel handshake; transport layer (XCMP/HRMP) is separate from the format itself
Standard Type Cross-chain Standard
Ecosystem Polkadot (also designed for cross-ecosystem use)