[Forum Post](https://forum.moonbeam.network/t/proposal-mr38-hotfix-for-kusama-fails-to-convert-xcm-from-v3-v2/1366)

**Abstract** -  There is an issue already [reported on Kusama](https://github.com/paritytech/polkadot-sdk/issues/2238) in which XCM fails with `Unroutable` for Parachains that Kusama thinks are in XCM Version 2, Moonriver included.

The proposal is so that the Moonriver OpenGov Tech Committee whitelists this proposal to notify Kusama that Moonriver is on Version 3. This patch would fix the Kusama -> Moonriver problem, although the underlying problem would still exist on Kusama.

**Details** - The proposal will send a very basic XCM message to Kusama in which Kusama is notified that Moonriver supports Version 3. If you are a curious person, [this is the XCM message being sent](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fmoonriver.unitedbloc.com#/extrinsics/decode/0x670003010003040379290303000000000000).

This needs to be sent from Root on Moonriver because it has te be executed on Kusama as Moonriver's Sovereign Account.


- Problem Statement: The Kusama network fails to convert XCM from v3 to v2, affecting Parachains including Moonriver. The intended audience is the Moonriver OpenGov Tech Committee.
- Significance: This issue prevents effective communication between Kusama and Moonriver, hindering the interoperability of these blockchain networks.
- Proposed Solution: The proposal suggests sending a basic XCM message from Moonriver to Kusama, notifying Kusama that Moonriver supports Version 3. This message needs to be sent from Root on Moonriver as it has to be executed on Kusama as Moonriver's Sovereign Account.
- Expected Outcomes: The proposed solution will fix the Kusama to Moonriver conversion problem, improving the interoperability between these networks. However, the underlying issue on Kusama will still persist.

#38 [Proposal: MR38] Hotfix for Kusama Fails to Convert XCM from V3 -> V2

No Active Proposals