The three 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://polkadot.subscan.io/xcm_message/polkadot-f66a7e88065cf3d7b6e531f3ffa05c1d748142a5), [2](https://hydration.subscan.io/xcm_message/polkadot-a9f9dabbc0fd2066b673a2ab0611fad88dc2e699) and [3](https://assethub-polkadot.subscan.io/xcm_message/polkadot-57b7063a03798764c36226132fae6145f7b150b4).

You can see that each 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 and is already fixed.

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

There was already a proposal for the same bug on [Kusama](https://kusama.subsquare.io/treasury/proposals/424).

Send a batch of dispatch calls and atomically execute them.
The whole transaction will rollback and fail if any of the calls failed.

May be called from any origin except `None`.

- `calls`: The calls to be dispatched from the same origin. The number of call must not
  exceed the constant: `batched_calls_limit` (available in constant metadata).

If origin is root then the calls are dispatched without checking origin filter. (This
includes bypassing `frame_system::Config::BaseCallFilter`).

## Complexity
- O(C) where C is the number of calls to be batched.

- **Problem Statement:** Three accounts lost funds due to bugs in the runtime, necessitating reimbursement.
- **Significance:** Funds were lost due to a bug, highlighting the need for reimbursement to affected accounts.
- **Proposed Solution:** Reimbursement for funds lost due to bugs in the runtime.
- **Expected Outcomes:** Restoration of lost funds to affected accounts.

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

No Active Proposals