XCM

Smart Contract Standard

Cross-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.

Fundação
Links
Visitar Comunidade

Detalhes

Licença https://github.com/polkadot-fellows/xcm-format
Status de Dev 🟢 Ativo
Detalhe do Status de Dev Active (v4 current specification)
Proprietário Polkadot Fellows (polkadot-fellows/xcm-format); originally authored by Gavin Wood / Parity Technologies
País Global / Decentralized (Web3 Foundation: Switzerland)
Ano de Início 2021
Stack Rust (Substrate/Polkadot SDK); XCM instructions compile to XCVM bytecode; transport via XCMP (cross-parachain), UMP (upward), DMP (downward), or HRMP; WebAssembly runtime
Financiamento Web3 Foundation / Polkadot Treasury; Parity Technologies; Polkadot Fellows ecosystem
Última Investigação 9 de mar. de 2026

Domínios de Caso de Uso

Platform Evolution & Sovereignty

Capacidades

Cross-instance federation Data portability

Smart Contract Standard Atributos

Origins Designed by Gavin Wood (Polkadot founder, Ethereum co-founder) at Parity Technologies. XCM evolved from the need to enable communication not just between parachains but across any consensus system. v1 shipped with Polkadot parachains in 2021; v3 merged January 17, 2023 after 15 months of development, adding bridges, cross-chain locking, NFT support, and conditional execution; v4 refines the instruction set. Stewardship transferred to the Polkadot Fellows open governance collective.
Data Formats MultiLocation (hierarchical location identifier for any consensus-system entity); MultiAsset (asset descriptor: Concrete/Abstract × Fungible/NonFungible); XCM v4 uses Location and Asset types; Protobuf/SCALE encoding
Terms MIT
Funds Unknown (part of Polkadot ecosystem core development funding)
Based On Polkadot's parachain architecture (ICS-equivalent for the Polkadot interchain); XCVM is an original design; conceptually adjacent to ICS-20 (Cosmos) and LayerZero OApp for cross-chain messaging
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)