The proposal addresses a recent XCM issue where the `SetTopic` instruction in XCM programs conflicts with destinations set to default version 2. This mismatch lead to failed transactions. [Referendum 305](https://kusama.subsquare.io/referenda/305) has successfully resolved the issue on Kusama. Now, this proposal sets its sights on Polkadot's relay chain, advocating for a similar adjustment by aligning the `safeXcmVersion` to v3 and ensuring it sends XCMs in the v3 format by default.

The mismatch in XCM versions can lead to issues between the relay chain and parachains. To resolve this, we propose setting the relay chain's safeXcmVersion to v3. This adjustment ensures that the relay chain will send XCMs in the v3 format by default.

Note that the proposal has been submitted on the Whitelisted Caller track, meaning the Fellowship is also voting on a proposal (no. [56](https://collectives.subsquare.io/fellowship/referenda/56)) to whitelist the submission hash

See [`Pallet::dispatch_whitelisted_call_with_preimage`].

- **Problem Statement:** Addressing the influx of refund requests and double spends related to Treasury Spend Proposals on the Polkadot network.
- **Significance:** Preventing double spends and reducing the number of refund requests to streamline the transition from Governance 1.0 to the upcoming runtime upgrade.
- **Proposed Solution:** Implementing measures to slash and refund treasury deposits based on specific criteria for proposers.
- **Expected Outcomes:** Efficient handling of refund requests, prevention of double spends, and smoother transition during the runtime upgrade on the Polkadot network.

#380 Setting the relay chain's safeXcmVersion to v3

No Active Proposals