[Forum Post](https://forum.moonbeam.network/t/proposal-mb109-voting-migrating-all-substrate-based-assets-to-evm-foreign-assets-on-moonbeam/2122)



**Abstract**

Moonbeam introduced the XC-20 token standard three years ago to support seamless cross-chain token functionality across the Polkadot ecosystem, while maintaining compatibility with Ethereum-based DeFi applications. This standard has become foundational in positioning Moonbeam as Polkadot’s interoperability hub, enabling use cases like Moonbeam Routed Liquidity (MRL). XC-20s represent both native Moonbeam tokens and those from other parachains, with “foreign assets” referring to tokens like DOT (xcDOT on Moonbeam) whose canonical source exists outside Moonbeam but are made usable within it.

Currently, foreign assets on Moonbeam are assigned ERC-20-style addresses via pre-compiled contracts rather than smart contracts, which limits compatibility with Ethereum development tools and environments. To resolve this, a multi-phase migration initiative began in late 2024 to replace the pre-compile model with true EVM-native implementations. This process has progressed through several runtime updates—RT3400, RT3501, and RT3600—each advancing the infrastructure to support the new model and migration capabilities.

This proposal requests approval to whitelist all current XC-20 foreign assets on Moonbeam as part of the first step in their migration to EVM-native format. It does not initiate the migration itself, but enables these assets to be included in the upcoming transition. This marks a key milestone in completing the broader initiative to modernize Moonbeam’s asset model and improve cross-chain integration and tool compatibility.

## **Details**

This proposal has been tested on Moonbeam Runtime 3600 using Chopsticks and with the following details:

* **Call data**: 0x2503c092e562030a1817df874317d6cad2fc3a1206b4c6269125c7200e2e14b65a8171c28d673cd773e2eb99fb3c69e6778fd57a3ce381bc01a57bb6b11040b8d9e043d7dee8acf39d719622ad2115fe9a8286ab3e9a8eb489f77413a08846b70849ecb270fd9f140728c807f50d217de1576c6b79167e78c839d6e1766a4b1924d7314f46911edf06834cfb87caed65e3905ee3eab6ed789ecfd1250be2fe2f9dbd4499e4b12687b011d23438f2ba0717da8c7365cb24eb1b38e5de7872bf44eb5d5dcc3fe7214349eb24f08de9da4dc45d345ba780a7f575d18749751bf0f6124a64d6f6f0a4fb6d578c63a0d840e067628f96bc1ab395e9ef5b258616eac91a1d2e32f9ced9144b74fd44105db6d577396abf9a89eb4d39bc13d81d97dfe3b7e115d4288b1b3f73f453fe354283a9ffcfa9472c43a391fc6f863df74957acb14b1bc6fd055771b18fcf7583264d21d7a25dcfb579d4d4780dc172e140e519ad93a8eea9f2c495f65845c64dea3402be64967dadc06a974252e2a81cf01a760b2b7d597d489a187e1588014e0f7fae29f26a90ac50ff2b086e38a351c4c00b56b44353d9e2459240de6bf8f6f22f08d5076859cf69e8e65142be113bdb614e93e9ab6c6fe9fd48fda6ba22eae08d1abeda994e69bf67ed5b72728918bf4eb436978a7933d4ae41435f2799aee750fb052adadaec24d6b2f7b6b2f497bb57926ac5521dcdcb91b148cd7512fd82d006fb09ea3d56b34fe114a16d465e93beaf8f4730f1ef9da9c06d1c57fab918b17cba96e8528ae97fdf5e3827c5f5931aa5f9c15a41e8b411c662038deb09450d4675387dab75a3184f6d430297339775d9bc1c4cd201862cc665120a351b20f7bd6ac07c47a952404f2b1568e6881efeb58c89188080778c30c20fa2ebc0ed18d2cbca1fd0771d7d6df4d4e0cd1a5e342f6257229faaddfca4355a6e4a106645f9fe22a9c1f44ce9855c2985b2b77665ead00acd6ed263572473434c1a233976c432c75544e54652e7d504a7beea57768e9c22b3565e5277b4f1786cec640f1dbd56c554ed6c7b0f903e80d0b5a7b88ecc4ed263
* **Preimage hash**: 0xf454592095f221db13f2a8f95d0dea086c6755f601fd7ecf9bd35f05d5a39bcc

As a result 48 XC-20s on Moonbeam have been approved for migrating to EVM bytecode.

#109 Proposal for migrating all substrate based assets to EVM foreign assets on Moonbeam