In an upcoming Runtime upgrade(2400 or 2500) the capability will be added for any native ERC-20 to be bridged from Moonbeam to any other parachain in the relay chain’s network - given that the receiving chain supports the ERC-20 and has opened a bidirectional XCM channel with Moonbeam.

Although the ERC-20 does not require any permission from Moonbeam to be XCM enabled, a process is necessary for ERC-20s to be listed in the MBF Dapp, which is proposed here.

Regardless of the process used to determine a listing, a token’s listing in the MBF Dapp should not be taken as an endorsement by the Moonbeam Foundation nor a testament to the future performance or safety of the token.

Check the full proposal text [here](https://forum.moonbeam.foundation/t/proposal-27-status-proposed-request-process-for-moonbeam-native-xcm-enabled-erc-20-xc-20-mbf-dapp-listing/7984).

Make some on-chain remark.

# <weight>
- `O(1)`
# </weight>

- In an upgrade, Moonbeam will allow ERC-20 tokens to be transferred to other parachains.
- ERC-20 tokens need to go through a process to be listed in the MBF Dapp.
- Being listed in the MBF Dapp doesn't mean Moonbeam endorses the token or guarantees its future performance or safety.
- You can read the full proposal text [here](https://forum.moonbeam.foundation/t/proposal-27-status-proposed-request-process-for-moonbeam-native-xcm-enabled-erc-20-xc-20-mbf-dapp-listing/7984).
- Tl;dr: Moonbeam is making it easier to transfer ERC-20 tokens, but being listed in the MBF Dapp doesn't mean the token is guaranteed to be good.

#99 Request Process for Moonbeam Native XCM Enabled ERC-20 (XC-20) MBF Dapp Listing

No Active Proposals