### Background
In an exceptional edge case, Account(25x4MUiqk9W2nqpQJfQXgjaUVZRpm9448DyMVJhtGSGoFb5N) during a DEX swap operation(https://acala.subscan.io/extrinsic/0xb5cefda106f982943c056bdd9430ffbf3b9c50be7c7221d8c135d2ed0f358575), the account's was reaped for ED . This triggered a KillAccount event, unbinded its default EVM address(0x6C9403e126960efb1b61ffCFBF8c8dA80DF963D9). Subsequently, the user manually bound the account to a new EVM address(0x7cacd1407ae510ae21bc95ca8209593c2b0518d4), which resulted in the loss of control over the default EVM address. Notably, the original EVM address still holds USDCet , creating an unintended and undesirable situation.

This proposal aims to address this situation by rebind the account and its original default EVM address in a way that aligns with the user's original intent.

### Proposal Content
1. Remove the association between the account(25x4MUiqk9W2nqpQJfQXgjaUVZRpm9448DyMVJhtGSGoFb5N) and EVM address (0x7cacd1407ae510ae21bc95ca8209593c2b0518d4).
2. Rebind account(25x4MUiqk9W2nqpQJfQXgjaUVZRpm9448DyMVJhtGSGoFb5N) to its original EVM address(0x6C9403e126960efb1b61ffCFBF8c8dA80DF963D9).

- An account (25x4MUiqk9W2nqpQJfQXgjaUVZRpm9448DyMVJhtGSGoFb5N) was reaped during a DEX swap due to ED.
- This triggered a KillAccount event and unbinded the account from its default EVM address (0x6C9403e126960efb1b61ffCFBF8c8dA80DF963D9).
- The user manually bound the account to a new EVM address (0x7cacd1407ae510ae21bc95ca8209593c2b0518d4), losing control of the original EVM address.
- The original EVM address still holds USDCet, causing an undesirable situation.
- The proposal aims to rebind the account to its original EVM address to align with the user's intent.
- Steps include removing the association with the new EVM address and rebinding to the original one.

#339·Restore Control of the Default EVM Address for Account 25x4MUiqk9W2nqpQJfQXgjaUVZRpm9448DyMVJhtGSGoFb5N

Background

Proposal Content