# XCMv3 to be removed in stable2612

**URL:** <https://forum.polkadot.network/t/xcmv3-to-be-removed-in-stable2612/19205>\
**Category:** Tech Talk\
**Tags:** xcm\
**Created:** [November 2, 2026, 3:45pm UTC](https://forum.polkadot.network/t/xcmv3-to-be-removed-in-stable2612/19205 "2026-11-02T15:45:00Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![francisco.aguirre](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/francisco.aguirre/32/1388_2.png) [@francisco.aguirre](https://forum.polkadot.network/u/francisco.aguirre)\
**Post date:** [November 2, 2026, 3:45pm UTC](https://forum.polkadot.network/t/xcmv3-to-be-removed-in-stable2612/19205/1 "2026-11-02T15:45:01Z")

</div>

TL;DR: XCMv3 will be removed in polkadot-sdk stable2612 (release 2026-12-17, ingestion by fellowship runtimes only after that). Once system chains upgrade, they will no longer send or accept v3 messages. If your chain or your app still uses v3, you need to move to v4 or v5 before then. Check your chain on the dashboard: [XCM Versions](https://franciscoaguirre.github.io/xcm-versions-dashboard/) .

XCMv5 was merged in November 2024: [XCM v5 by franciscoaguirre · Pull Request #4826 · paritytech/polkadot-sdk · GitHub](https://github.com/paritytech/polkadot-sdk/pull/4826) . A PR removing v3 ( [Remove XCMv3 by franciscoaguirre · Pull Request #13629 · paritytech/polkadot-sdk · GitHub](https://github.com/paritytech/polkadot-sdk/pull/13629) ) will ship in `stable2612`, scheduled for `2026-12-17`. After that, system parachains and any other runtime can adopt it. Allowing for runtime releases and governance, expect the first chains to drop v3 in early 2027.

Once a chain drops v3, it can’t decode v3 messages sent to it and can’t downgrade outgoing messages to v3. XCM between that chain and any other chain still on v3 will fail.

To help, I built a dashboard ( [XCM Versions](https://franciscoaguirre.github.io/xcm-versions-dashboard/) ) showing each chains’ XCM version. Click a chain to see suggested action items. The main ones are:

- Code: move XCM programs and types to v4+. This is mostly renames (e.g. dropping the `Multi` prefix). Raw v3 types in storage don’t need migrating because the encoding is the same, but stored `Versioned*` values with the `V3` variant do.
- Storage: update `SafeXcmVersion` (via `force_default_xcm_version`) and any `SupportedVersion` entries pinned to v3 (via `force_xcm_version`). These are Root calls so plan for governance time.
- Off-chain: wallets, dapps and scripts that build v3 versioned types need updating too

If you run into any issues migrating, please ask in the Paraspell support group: [Telegram: View @paraspell](https://t.me/paraspell) , me or anyone else there can help you out. If you have any issues with the dashboard you can reply here or open an issue: [Issues · franciscoaguirre/xcm-versions-dashboard · GitHub](https://github.com/franciscoaguirre/xcm-versions-dashboard/issues) .