We have observed XCM errors since the upgrade of Kusama to v1000000
context: https://forum.moonbeam.network/t/proposal-mr38-hotfix-for-kusama-fails-to-convert-xcm-from-v3-v2/1366/12

hereby reproducing the same fix

Schedule the currently externally-proposed majority-carries referendum to be tabled
immediately. If there is no externally-proposed referendum currently, or if there is one
but it is not a majority-carries referendum then it fails.

The dispatch of this call must be `FastTrackOrigin`.

- `proposal_hash`: The hash of the current external proposal.
- `voting_period`: The period that is allowed for voting on this proposal. Increased to
	Must be always greater than zero.
	For `FastTrackOrigin` must be equal or greater than `FastTrackVotingPeriod`.
- `delay`: The number of block after voting has ended in approval and this should be
  enacted. This doesn't have a minimum amount.

Emits `Started`.

Weight: `O(1)`

- Problem Statement: The Polkassembly council has identified an issue with XCM errors following the upgrade of Kusama to v1000000, affecting the Polkadot community.
- Significance: The problem is significant as it disrupts the functionality of the Kusama network, potentially impacting user experience and network performance.
- Proposed Solution: The council proposes to reproduce the same fix that was previously applied to address similar issues, as detailed in the linked forum post.
- Expected Outcomes: The implementation of the proposed solution is expected to resolve the XCM errors, improving the stability and performance of the Kusama network.

#19 Fix XCM with RelayChain Query

No Active Proposals