Dear council,

I have opened a tip for a community member who mistakenly sent [10.18 DOT directly to nomination pool 61](https://polkadot.subscan.io/extrinsic/13355740-2) instead of using the nominationPools.join extrinsic. By this action and given that no one holds the private key for the destination account, the user is now unable to access funds. Considering that the balances.forceTransfer call is very powerful and it takes a more complex process, and the balance is low, I think the best option is to refund this community member through a tip. If you know any other solution, we are open to listen to you.

You can find the references below:

[Rewards address of the pool 61](https://polkadot.subscan.io/account/13UVJyLnbVp8c4FQeiGYEwEKvJcqfvpmypp2gHHP8nxqnpGJ)

[Transaction to the pool rewards address](https://polkadot.subscan.io/extrinsic/13355740-2)

A similar event happened in the past and is being taken as a reference. You can see it [here](https://kusama.polkassembly.io/tip/0x410a4f0a577cac54e6f5fec623f7c07602b0e9668375bd8c8c1922de79952692).

0x544f3a206b6f75736869726f20464f523a20636f6e747269627574696f6e73206f66207375627374726174652337383832

- Problem Statement: Community member mistakenly sent 10.18 DOT to the wrong pool, unable to access funds.
- Significance: Balances.forceTransfer is complex, low balance, no private key for destination account.
- Proposed Solution: Refund the community member through a tip due to the complexity of the balances.forceTransfer process.
- Expected Outcomes: Provide a solution for the community member to access their funds, ensuring fairness and transparency in the process.

To aid a community member who lost 10.18 DOT by mistakenly sending funds directly to a nomination pool rewards address

No Active Proposals