## TL:DR

The following proposal registers DOT from Polkadot as xcDOT on Moonbeam.

## Summary

We propose to register DOT from Polkadot as xcDOT on Moonbeam. The XC-20 has the following details:

Multilocation: *{ "parents": 1, "interior":  Here}*

Decimals: *10*

Name: *xcDOT*

Symbol: *xcDOT*

 
The proposed fee to execute the XCM was calculated using the current KSM to USD price ratio in Moonriver.

## Proposal

Proposal #34 with the following hash: 0xdac719ae418394261f44f41d69b98d846fca956695a52950238798ef6deb089a

## Technical details:

The procedure to register an asset on Moonbeam is as follows:

*assetManager.registerAsset* to register the asset with the information provided in the summary

*assetManager.setAssetUnitsPerSecond* to set the amount we are gonna charge in xcDOT for XCM execution. This was calcualted using the value for KSM, and the price ratio between KSM and DOT on April 20th, 2022.

*system.setStorage* to store a revert code in the asset's storage. This is so that smart contracts can interact with the XC-20 (through the EVM)

Once the proposal is enacted, *xcDOT* will live under asset ID *42259045809535163221576417993425387648*. Consequently, the XC-20 address would be *0xFfFFfFff1FcaCBd218EDc0EbA20Fc2308C778080*

If you are interested, the hex-encoded call data of the proposal on [Moonbeam](Polkadot/Substrate Portal  ) is:

**batchAll:**

0x1e020c6900000100147863444f54147863444f540a00010000000000000000000000000000000169010001000cf6a6a00200000000000000000000000000000000050411011da53b775b270400e7e61ed5cbc5a146ea70f53d5a3306ce02aaf97049cf181a1f720ca3a567a7892f51ba4eabe649ccffffffff1fcacbd218edc0eba20fc2308c778080181460006000fd

And each call individually:

**AssetManager.registerAsset**

0x6900000100147863444f54147863444f540a000100000000000000000000000000000000

**AssetManager.setAssetUnitsPerSecond**

0x69010001000cf6a6a002000000000000000000000000000000

**SetStorage

0x00050411011da53b775b270400e7e61ed5cbc5a146ea70f53d5a3306ce02aaf97049cf181a1f720ca3a567a7892f51ba4eabe649ccffffffff1fcacbd218edc0eba20fc2308c778080181460006000fd

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.

- `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 call are dispatch without checking origin filter. (This includes
bypassing `frame_system::Config::BaseCallFilter`).

# <weight>
- Complexity: O(C) where C is the number of calls to be batched.
# </weight>

:

We propose to register DOT from Polkadot as xcDOT on Moonbeam, with the xcDOT address being 0xFfFFfFff1FcaCBd218EDc0EbA20Fc2308C778080. The proposal hash is 0xdac719ae418394261f44f41d69b98d846fca956695a52950238798ef6deb089a, and the hex-encoded call data for the proposal is batchAll: 0x1e020c6900000100147863444f54147863444f540a00010000000000000000000000000000000169010001000cf6a6a00200000000000000000000000000000000050411011da53b775b270400e7e61ed5cbc5a146ea70f53d5a3306ce02aaf97049cf181a1f720ca3a567a7892f51ba4eabe649ccffffffff1fcacbd218edc0eba20fc2308c778080181460006000fd.

#34 Register DOT from Polkadot as xcDOT on Moonbeam