[Proposal: MR38] Hotfix for Kusama Fails to Convert XCM from V3 → V2
Abstract - There is an issue already reported on Kusama in which XCM fails with Unroutable
for Parachains that Kusama thinks are in XCM Version 2, Moonriver included.
I’m proposing this 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.
This needs to be sent from Root on Moonriver because it has te be executed on Kusama as Moonriver’s Sovereign Account.
Chopsticks Test - First let’s try a regular XCM transfer to see the error:
0x6308030001009d1f0300010300f24ff3a9cf04c71dbc94d0b566f7a27b94566cac030400000000070010a5d4e80000000000
Now let’s build the XCM message and create the preimage:
0x3e0048670003010003040379290303000000000000
The preimage hash is: 0x6557039f285fa327502fcdc967417ef9ecf897b9f49b0fa97382e13f0aaa35f9
Next, I’ll propose this preimage through the ROOT track, and using a tool we can speed ahead this proposal so that it executes instantly:
On Kusama we see:
Now, if I test the XCM Token transfer:
And on Moonriver:
Note that for whitelisting, this preimage is not required!! The process is a bit different, but the end result is the same