Dapp Listing Request Template
Referendum #99 on Moonbeam and Referendum #13 on Moonriver were voted on and passed to set a process for ERC-20s to be listed in the MBF Dapp.
To request listing on the MBF Dapp, a team member should post a complete request in this sub-category and tag it with Moonbeam or Moonriver. Gathering community engagement and feedback is encouraged during the review period, which should not exceed two weeks. The Moonbeam Foundation has the authority to list, not list, or delist a token at any time, with details provided in the forum thread.
Listing Request Template
Request for a ERC-20 Listing must follow a standardized Listing Request Template
a. Team/Project Overview
- Title: [ERC-20 Name] Request to list in MBF Dapp
- Contact: Email/TG/Discord handle to communicate with Requestor
- Overview: One sentence summarizing your ERC-20 and relevant links to your website, Twitter and social channels.
b. Token Info
- Token Name:
- Token Symbol :
- Decimals:
- Total Supply (at time of Request, note if variable):
- Number of Holders (at time of Request):
- Active Daily Users:
- Tokenomics (URL):
- Art Assets (URL):
- Have you completed full testing of this token on the Moonbase Alpha TestNet?
c. Token Pricing Information (if available)
- Listing URL (CMC, Coingecko etc.):
- Total Market Cap (at time of Request):
d. Etherscan Token Profile
- Token Profile URL Profile should be completed
- Verified Contract Token Contract Source Code must be verified
- Reference: Add Token Information on Moonscan | Moonbeam Docs
e. Signed Message
Using View, Sign, & Verify Message Signatures | Moonbeam or similar, the Requestor should include the following message as signed bytes:
[Moonbeam ChainID 1284/Moonriver ChainID 1285] I hereby declare that I am the creator of contract address[contractAddress]
This message will serve to show that the actual owner/deployer of the contract is submitting the Listing Request.
f. Key Disclosure
Requestor for a ERC-20 Dapp listing must provide the following as part of the Request:
-
Is the Contract Code Open-Source (and include GitHub link)? If parts of the code are not open source: please provide information on why not
-
(For Moonbeam Proposals Only) Does your token have a Moonriver deployment? *If yes, please provide token details and whether your Moonriver deployment has already integrated with other Parachains in Kusama
-
Is your Contract Code audited? If yes, please provide:
- The name of Auditors,
- Dates of audit reports and, if available,
- Links to audit reports
g. Network Support
- For each Parachain Supporting ERC-20 XCM Transfer: This section determines which parachains are listed as transfer destinations in the Dapp.
- Destination chain:
- Sufficient Asset Qty (minimum balance allowable:
- Asset remote id:
- Status (is parachain currently accepting token):
All projects must make a good-faith effort to keep this up to date so long as they are supported by the Moonbeam Dapp. In particular the Network Support section must be accurate in order for the Dapp to correctly list parachains the token may be sent to.