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 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) to whitelist the submission hash
SetTopic instruction conflicts with default version 2 destinations, causing failed transactions.safeXcmVersion to v3 on Polkadot's relay chain.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 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) to whitelist the submission hash