The next [runtime upgrade v0.4.0](https://zeitgeist.subsquare.io/council/motions/34) requires `polkadotXcm.safeXcmVersion` to be configured properly to be able to send XCM, as `pallet-xcm` uses the storage instead of a hard coded value from v0.4.0 onward.

Right now XCMv2 is deployed. The message format V1 is the oldest supported version, V2 is the current version. With v0.4.0, XCMv3 is deployed. The message format V1 will be deprecated, V2 will be the safe default and V3 will be the most recent version.

⚠ Not configuring this value before deployment of v0.4.0 results in the inability to send XCMs. 

- The upcoming runtime upgrade v0.4.0 requires `polkadotXcm.safeXcmVersion` to be set correctly for sending XCM messages.
- From v0.4.0, `pallet-xcm` will use the configured storage value instead of a hardcoded one.
- Currently, XCMv2 is in use, with V1 being the oldest supported format and V2 the current one.
- With v0.4.0, XCMv3 will be deployed, making V1 deprecated, V2 the safe default, and V3 the latest version.
- Failing to configure the `polkadotXcm.safeXcmVersion` before v0.4.0 will prevent sending XCM messages.

proposalId

Awarded

Set safe default XCM version to 2

root

whitelisted_caller

wish_for_change

staking_admin

treasurer

lease_admin

fellowship_admin

general_admin

auction_admin

referendum_canceller

referendum_killer

small_tipper

big_tipper

small_spender

medium_spender

big_spender

#35·Set safe default XCM version to 2