XCM capability matrix: 45 chains, checked live

Tyler Woods · 2026

Every Substrate chain can be connected to. Fewer expose the extrinsics and runtime APIs an XCM integration needs. On 29 October 2026 I ran the four method probes and two runtime API probes from the capability checker against every chain in the ParaSpell SDK list, and recorded the result.

Probe method: call the extrinsic or runtime API with no arguments. A method that exists fails argument validation with Incompatible runtime entry; a missing one fails with Runtime entry ... not found. Anything else is retried once and reported as unknown. The live result is shown next to the SDK registry flag, which is what the SDK actually follows.

Result

41 of the 45 chains expose all four transfer methods and both runtime APIs. Four exceptions:

• Pendulum lacks transfer_assets_using_type_and_then. It has the other three methods, no DryRunApi and no XcmPaymentApi.
• Heima, HeimaPaseo and Peaq have all four methods but no DryRunApi and no XcmPaymentApi.

Every live probe matched the SDK registry flag. That is the useful negative result: on these chains the SDK's compiled-in knowledge is current.

The matrix

Download and reproduce

The full result is available as JSON or CSV, and the scripts that produced it are at github.com/ImBeasting/xcm-capability-checker. To reproduce a row, run the checker:

npm install @paraspell/sdk
node check-chain-capabilities.mjs Hydration Peaq Pendulum

Probe results are date-stamped because runtimes change. Re-run before relying on a row.

Excluded rows

• Centrifuge: the default provider reported finalized block 0 and a genesis-era metadata set, so its row would describe the provider, not the chain. The chain produced no blocks between 2026-08-23 and the check.
• Penpal: local development chain, endpoint not reachable from here.
• Ethereum and EthereumTestnet: external chains, not XCM origins, so the four extrinsics do not apply.

Acala timed out on the first parallel run and completed on retry against the same endpoint. The row above is from the retry.

What this does not prove

The table is about capabilities, not routes. It does not check asset listings, decimals, existential deposits, the destination's support for an asset, the reserve chain, XCM version negotiation, or whether a specific transfer can be built. A row of yes is a necessary condition for a route, not a working route.

AI assistance was used to draft this article. The data is a direct output of the published script, run on 29 October 2026; the raw JSON is dated and kept in the project record.