<a href="https://forum.moonbeam.network/t/proposal-67-bump-xcm-safe-version-to-3/1976">Forum Post</a>
Abstract
Simple Proposal to bump the XCM Safe Version to 3
Details
As more projects are migrating to newer versions of XCM, it is best if we set Moonriver's XCM Safe version to 3, as it is a more modern XCM version that supports more methods.
The bytes of the call can be found <a href="https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fwss.api.moonriver.moonbeam.network#/extrinsics/decode/0x67050103000000">here</a>.
Preimage tested in chopsticks was <code>0x72477dd269108f83d1fb58c4c903033ac353b89d421a3ae0b14b09f267a7835a</code>.
&nbsp;

Set a safe XCM version (the version that XCM should be encoded with if the most recent
version a destination can accept is unknown).

- `origin`: Must be an origin specified by AdminOrigin.
- `maybe_xcm_version`: The default XCM encoding version, or `None` to disable.

- **Problem Statement:** Updating Moonriver's XCM Safe version to 3 to align with modern XCM standards.
- **Significance:** Ensuring compatibility with newer XCM versions for projects migrating to Moonriver.
- **Proposed Solution:** Set Moonriver's XCM Safe version to 3 for enhanced support of methods.
- **Expected Outcomes:** Improved compatibility and functionality for projects on Moonriver.

#67 [Proposal: 67] Bump XCM Safe Version to 3