In an upcoming Runtime upgrade(2400 or 2500) the capability will be added for any native ERC-20 to be bridged from Moonriver 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 Moonriver.

Although the ERC-20 does not require any permission from Moonriver 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/referendum-13-request-process-for-moonriver-native-xcm-enabled-erc-20-xc-20-mbf-dapp-listing/834).

Make some on-chain remark.

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

- **Problem Statement:** Requesting funding for retroactive costs of running high-performance public infrastructure for Moonbeam, Moonriver, and Moonbase Alpha in Q3 2023.
- **Significance:** Setting up blockchain infrastructure is challenging, time-consuming, and costly, requiring expertise, continuous node running, and global scalability.
- **Proposed Solution:** OnFinality offers a shared node API service to reduce barriers to accessing new protocols, managing nodes globally, and handling production workloads efficiently.
- **Expected Outcomes:** Mitigating the challenges of starting on Moonbeam Networks, reducing costs of secure node access, and providing reliable infrastructure for dApps.

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