This proposal, if approved, will return the KSM from failed XCM transfers from Kusama to Basilisk, as a result of the recent issues with XCM caused by a Kusama runtime upgrade. Those issues are now resolved and the CROSS-CHAIN tab is once again activated on Basilisk app.

The refunded addresses are:

- `DJZf8pZ5vUWwNoodRtEt2JpNwB9dFDGBv8B2MJ9JQtvZb4k`
- `GvrJix8vF8iKgsTAfuazEDrBibiM6jgG66C6sT2W56cEZr3`
- `EgCtLzYq6rpMUWCd3o34XMGtQsZn1e3qK4iZi8nwXK981fD`
- `HHt7f3iq8ofVWHkGobmeUGbmJJ9CKPPZ1ikVTXULiS4dC9e`
- `D14ff224mu9AqXGjHKYHFi5CpvrBubtpngZLaLo7eBk3Qw5`
- `HCRaNkNLBQvc2vvDmeuYgMQFhvnE4RZcFz8EhutrPS7uwUx`
- `Drt99vgDkPGYvePxaDH9xPaPtrM7JXKpm2GcPxPKZZonJom`
- `F8MyAVsbdFFermUZQXZT5JMS1fTam6MmifvSG9aMVsDEvUh`

call

- **Problem Statement:** Returning KSM from failed XCM transfers from Kusama to Basilisk due to recent XCM issues post Kusama runtime upgrade.
- **Significance:** Addresses the impact of failed transfers and resolves issues caused by XCM problems.
- **Proposed Solution:** Refunding the specified addresses affected by the failed transfers.
- **Expected Outcomes:** Restoring the KSM to the specified addresses, resolving the issue caused by the XCM problems.

#28 Return KSM from failed Kusama > Basilisk XCM transfers

No Active Proposals