Reimbursement for lost pool rewards

This proposal aims to reimburse 50 pool members that didn't receive various amounts of pool rewards due to this bug, which was fixed in the latest runtime upgrade.

In short, when a pool enters the destroying phase anyone can permissionlessly unbond the pool members. When that happens any pending rewards are claimed. This bug caused the rewards to be sent to the caller of the unbond extrinsic, instead of the actual pool member.

We ran this Python script to find the affected accounts and the rewards they didn't receive (credit to Kian who wrote it). The results can be found here. I'd appreciate any cross checks to make sure the batch call has been built correctly and the proper amounts will be sent to the correct recipients.

To be clear, this is a double spend. These rewards have already been claimed by the pool owners who called the unbond extrinsics. But given that the amount is small, and trying to contact all these pool owners to return the misappropriated rewards would be troublesome to say the least, we believe this proposal is the most straightforward way to make these pool members whole and we'd appreciate it if the community approved it.

Edited

Summary of Proposal

Issue: A bug caused pool rewards to be sent to the wrong accounts during the unbonding process.
Bug Fix: The bug was fixed in the latest runtime upgrade.
Affected Members: 50 pool members did not receive their rewards.
Python Script: A script was used to identify the affected accounts and the missing rewards.
Results: The findings are available in a shared file for cross-checking.
Double Spend: The rewards were already claimed by pool owners, but contacting them to return the rewards would be difficult.
Proposal: The proposal suggests reimbursing the affected pool members directly.
Community Approval: The community's approval is requested for this proposal.

Source

This proposal aims to reimburse 50 pool members that didn't receive various amounts of pool rewards due to this bug, which was fixed in the latest runtime upgrade.

In short, when a pool enters the destroying phase anyone can permissionlessly unbond the pool members. When that happens any pending rewards are claimed. This bug caused the rewards to be sent to the caller of the unbond extrinsic, instead of the actual pool member.

We ran this Python script to find the affected accounts and the rewards they didn't receive (credit to Kian who wrote it). The results can be found here. I'd appreciate any cross checks to make sure the batch call has been built correctly and the proper amounts will be sent to the correct recipients.

To be clear, this is a double spend. These rewards have already been claimed by the pool owners who called the unbond extrinsics. But given that the amount is small, and trying to contact all these pool owners to return the misappropriated rewards would be troublesome to say the least, we believe this proposal is the most straightforward way to make these pool members whole and we'd appreciate it if the community approved it.

Edited