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

[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

7 Likes

Also, it seems that the following address were affected and they have KSM stuck in Moonriver’s Sovereign Account on the Relay Chain:

KSM Address Amount [KSM]
G9z7Co9LAViZyfEANSyHAKLyeZiMdm2Bfmmky7XPKHH3tMX 0.1
HLbGgmYTS2qCGk6v3nxsdGirquG1LMADecLWhe34WxvbPBg 23.2
HWyLYmpW68JGJYoVJcot6JQ1CJbtUQeTdxfY1kUTsvGCB1r 0.1
GXeHEVY5SSJFQqcFmANaY3mTsRpcE9EUVzDcGpowbbe41ZZ 12
EiMKCFXoj4K3115hFMuJS2Ryxsv8d1RUGdqHtcvEZcBHdKy 0.06070199878

I’ll work to see if there is something that can be done via XCM, or with MBF directly.

3 Likes

The 0.1 KSM from HWyLYmpW68JGJYoVJcot6JQ1CJbtUQeTdxfY1kUTsvGCB1r can be ignored from the list - that was my test tx fully aware of sending the funds into nirvana.

thank you very very much @AlbertoV19 for the speedy hotfix and the detailled information!
Also saw other parachains struggle but none coming up with a solution thus far :wink: Well done :rocket:

5 Likes

Thanks @AlbertoV19 - I agree we should fix this quickly. I will create a motion for the tech committee to consider for whitelist.

5 Likes

Whitelist proposal is open for voting for the Moonriver technical committee:

Proposal Hash: 0xaccc0d98c90496882283b571acd49e6260e870ce03770933ca88ee58db1c1d5d

Proposal Index: 6

5 Likes

The open tech committee has voted in favor and the pre-image has been whitelisted.
(0x6557039f285fa327502fcdc967417ef9ecf897b9f49b0fa97382e13f0aaa35f9)

4 Likes

Proposal 38 submitted → Moonbeam Dapps

3 Likes

We’re flyyiiiiin’ :rocket:
Lets get the votes rolling!

2 Likes

agreed lets fix this asap before more users are affected

2 Likes

This referendum has been executed.

2 Likes

1 Like

Using Chopsticks, now transfers are functioning again:

Also tested the Moonriver <> Kusama flow just to check and it worked as well.

I’ll request so that KSM transfers resume in the dApp.

4 Likes

For the users whose KSM got locked up in Moonriver’s sovereign account, due to the fact that:

  • the sums are relatively small
  • using governance to return these funds via XCM would cause further delay

The Moonbeam Foundation has decided it will reimburse these users directly and will do so at some point later today.

The KSM left in the sovereign account can be used at a later time for XCM transacting or the Foundation can always seek reimbursement via governance at a later time.

I or someone else from the Foundation will post back here with the transactions when this has been completed.

6 Likes

just wanted to say thanks for sorting out the issue so quickly. your fast response really much appreciated

5 Likes

Credit goes to @AlbertoV19 !

3 Likes

These addresses have now all been reimbursed.

4 Likes

Wow that was quick! Very much appreciated yall

2 Likes

Great job! This issue was solved so quickly that I didn’t even know it existed.

3 Likes