The new Kusama runtime 1000000 introduced a XCM bug that can result partially executed XCM and stuck of funds.

I worked with Parity devs to debug and identify the root cause of the bug, create [a Github issue](https://github.com/paritytech/polkadot-sdk/issues/2238) described action items, [a twitter thread](https://twitter.com/XiliangChen/status/1722546330382565572) explaining the bug, [suggestion to parachain teams](https://twitter.com/XiliangChen/status/1722546359071609103) to workaround the issue. I also created [a test script](https://github.com/xlc/chopsticks-ksm-xcm/tree/master) using Chopsticks to reproduce the issue, and use it to verify the fix.

I will also work with Fellowship to setup e2e tests and regression tests for future releases. But this can be considered out of scope of this tip.

- Problem Statement: The new Kusama runtime 1000000 has introduced a Cross-Chain Message (XCM) bug that can result in partially executed XCM and stuck funds. The intended audience includes Parity developers and parachain teams.
- Significance: The bug disrupts the smooth operation of the Kusama network, potentially affecting transactions and causing loss of funds.
- Proposed Solution: The author has identified the root cause of the bug, created a Github issue outlining action items, and provided a workaround suggestion to parachain teams. They have also developed a test script using Chopsticks to reproduce the issue and verify the fix.
- Expected Outcomes: The author plans to work with Fellowship to set up end-to-end tests and regression tests for future releases, aiming to prevent similar issues in the future. This will ensure the smooth operation of the Kusama network and protect users' funds.

#304 Help debug and mitigate Kusama XCM issue

No Active Proposals