## TL:DR
We propose to update Moonriver's XCM Supported Version on Kusama to Version 2.

## Summary
Kusama is using XCM Version 1 when "communicating" with Moonriver. This proposal updates the XCM Supported version to Version 2.

## Proposal
Proposal #17 with the following hash: *0x1fbe2211015409a8a4ab90235a19436e63690e333356e965f3f842389bb1ef31*

## Technical details:
Kusama expects from Moonriver a response to a Query ID with the supported verison. The Query ID can be verified by checking the [chain state](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fkusama-rpc.polkadot.io#/chainstate) `xcmPallet.queries(2654)`, which returns the following:

```
{
  VersionNotifier: {
    origin: {
      V1: {
        parents: 0
        interior: {
          X1: {
            Parachain: 2,023
          }
        }
      }
    }
    isActive: false
  }
}
```

The version is updated by sending a XCM message with the `QueryResponse` XCM instruction, `queryId` of 2654,  `response` set to `Version: 2` and `maxWeight` to 0.

If you are interested, the hex-encoded call data is [Moonriver](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fwss.api.moonriver.moonbeam.network#/extrinsics/decode) is: `0x67000101000204037929030200000000`



 Sets the ideal number of validators.

 The dispatch origin must be Root.

 # <weight>
 Base Weight: 1.717 µs
 Write: Validator Count
 # </weight>

- Problem Statement: Kusama is using an outdated version of XCM when communicating with Moonriver.
- Audience: Kusama and Moonriver users.
- Significance: Updating the XCM Supported version will improve communication between Kusama and Moonriver.
- Proposed Solution: Update Moonriver's XCM Supported Version on Kusama to Version 2.
- Expected Outcomes: Improved communication and compatibility between Kusama and Moonriver.

#83 Updated XCM Supported Version on Kusama

No Active Proposals