[Forum post](https://forum.moonbeam.foundation/t/proposal-20-status-seconding-recover-dot-from-wrongly-built-xcm-message/336)

## TL:DR

Send DOTs out of Moonbeam's Sovereign account that were locked there due to a wrongly built XCM message for an xcDOT -> DOT transfer.

## Summary
On [block 1,857,847](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fwss.api.moonbeam.network#/explorer/query/1857847) there was a wrongly built XCM message sent to Polkadot to transfer/convert 138.0586102303 xcDOT to DOT.

The user used an application that crafted the XCM message with an incorrect destination multilocation. The consequence of this was that the balance was [correctly withdrawn from Moonbeam's Sovereign Account](https://polkadot.subscan.io/extrinsic/12028410-1?event=12028410-24), but it was then immediately [deposited back](https://polkadot.subscan.io/extrinsic/12028410-1?event=12028410-25), minus some fees.

Moreover, the wrongly built multilocation resulted in Polkadot sending an [XCM back to Moonbeam](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fmoonbeam.unitedbloc.com%3A3001#/explorer/query/1857848) to transfer the assets back (because the multilocation included a `ParachainId: 2004`). So, in the execution of that XCM message, another `0.0009028184` DOT were used for fees.

The amount that was deposited back in Polkadot was `138.0116684851` DOT, and the fees paid for the XCM message sent from Polkadot to Moonbeam was `0.0009028184` DOT. Therefore, this proposal will send an XCM message that will take `138.0107656667` DOT out of Moonbeam's Sovereign account, pay for fees, and deposit the rest to the account set in the original XCM message.

According to the estimations, the XCM fee will be `0.0306485226` DOT, so the user should receive `137.9801171441` DOT.

## Proposal

Proposal #20 with the following hash: *0xcc3d9ac490b5715c85bf9953021880618c967abb3745041f6124e728c550484f*

## Technical details:
The incorrect destination multilocation was the following:

```
{ "parents": 1, 
  "interior": 
    { "X2": [
      { "Parachain": 2004},
      {"AccountId32":
        {"network": "Any",
        "key": "0x681abe229de77e92d4f4c82ea282553a50eea781ae46c5200b0dcd34d17ccf14"
        }
      }
    }
  }
```
In this multilocation, the parachain ID is not needed. Therefore, the correct multilocation would be:

```
{ "parents": 1, 
  "interior": 
    { "X1": 
      {"AccountId32":
        {"network": "Any",
        "key": "0x681abe229de77e92d4f4c82ea282553a50eea781ae46c5200b0dcd34d17ccf14"
        }
      }
    }
  }
```

The consequence of this was that the balance was [correctly withdrawn from Moonbeam's Sovereign Account](https://polkadot.subscan.io/extrinsic/12028410-1?event=12028410-24), but it was then immediately [deposited back](https://polkadot.subscan.io/extrinsic/12028410-1?event=12028410-25), minus some fees.

Another XCM message was sent from Polkadot to Moonbeam, which failed to [execute on Moonbeam](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fmoonbeam.unitedbloc.com%3A3001#/explorer/query/1857848) as the account format set was not correct. Because this failed while executing the `DepositAsset` instruction, the asset is [taken away from the holding registry and minted into the user's provided account](https://github.com/paritytech/polkadot/blob/master/xcm/xcm-executor/src/lib.rs#L614-L618) (which is the part that fails). No assets are trapped on Moonbeam, meaning that the user has is assets locked in Moonbeam's Sovereign account on Polkadot.

This was [replicated on Moonbase Alpha](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Ffrag-moonlama-rpc-ws.g.moondev.network#/explorer/query/0x269aa271380e767b4a52c56a0b7ea8c712bbe38de43833c3fe013a14a5abaf99), with the same happening [on its Relay Chain](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Ffrag-moonlama-relay-rpc-ws.g.moondev.network#/explorer/query/0x39efb00d60c42abdd57ea9a07b790ea6e00eb91d28ff5457c5a494cc051f9aac).

The amount that was deposited back in Polkadot was `138.0116684851` DOT, and the fees paid for the XCM message sent from Polkadot to Moonbeam was `0.0009028184` DOT. Therefore, this proposal will send an XCM message with the following three instructions:

- WithdrawAsset: will take `138.0107656667` DOT from Moonbeam's Sovereign Account
- BuyExecution: will use the withdrawn fund to buy enough execution time in Polkadot to execute the XCM message
- DepositAsset: will deposit whatever assets are left to a provided account, which will be the same as in the original XCM message

According to the estimations, the XCM fee will be `0.0306485226` DOT, so the user should receive `137.9801171441` DOT.

The SCALE-encoded call data for the XCM message is the following:

```
0x6700010100020c0004000000000bdb9dd354410113000000000bdb9dd3544101000d01000400010100681abe229de77e92d4f4c82ea282553a50eea781ae46c5200b0dcd34d17ccf14
```

This process was tested successfully in internal networks that replicate Moonbeam-Polkadot.

This proposal outlines a 42-week plan for The Kusamarian. It includes the transition to a blended funding model, with 70% of costs covered by the treasury and 30% from alternative sources. Kusamarian’s costs breakdown is presented with full details and they welcome audits for transparency and further improvements. The Kusamarian emphasize on attracting new audience, spotlighting the builders and the overall developments within Polkadot ecosystem, and providing a forum for discourse and discovery.

- There was a mistake in a message that was sent to transfer some DOTs.
- The mistake caused the balance to be withdrawn from an account and then deposited back, but with some fees taken out.
- Another message was sent to transfer the assets back, but it failed because of a wrong account format.
- The assets are now locked in an account.
- A proposal has been made to fix the mistake and transfer the assets correctly.

#85 Recover DOT from Wrongly Built XCM Message

No Active Proposals