The four accounts on this proposal made extrinsics in the past that lost funds due to bugs in the runtime at that time.
The extrinsics were: [1](https://kusama.subscan.io/extrinsic/21678807-20), [2](https://kusama.subscan.io/extrinsic/21577634-3), [3](https://kusama.subscan.io/extrinsic/21734857-2) and [4](https://kusama.subscan.io/extrinsic/21605077-2)

You can see that each has a `polkadotXcm.Attempted` event which shows that it failed, however, there should be a `polkadotXcm.AssetsTrapped` event too. This was due to a bug that the assets were not trapped and therefore lost. This bug was present in the version used in these extrinsics, 1.1.0 of Kusama.
The accounts attempted to cross-chain transfer all their funds and didn't have enough to pay for delivery fees, since they were taken from the account itself.
This was fixed in version 1.1.2, after changes from [PR 3085](https://github.com/paritytech/polkadot-sdk/pull/3085) were included.

Since these funds were lost due to a bug, they should be reimbursed, while extrinsics where assets were trapped (not included in this proposal) can be reclaimed.

- **Problem Statement:** Accounts lost funds due to a bug in the runtime during cross-chain transfers on Kusama.
- **Significance:** The bug caused assets to not be trapped, resulting in lost funds during cross-chain transfers.
- **Proposed Solution:** Reimburse the lost funds from extrinsics affected by the bug in version 1.1.0 of Kusama.
- **Expected Outcomes:** Accounts will be reimbursed for the lost funds, ensuring fairness and rectifying the impact of the bug.

#424 [Small Spender] Reimburse accounts affected by an XCM bug