About the XCM Disclosures category

Key Disclosures of XCM channels

Referendum #86 passed by the Moonbeam community outlined that any network that wants Moonbeam Dapp support must provide Key Disclosures and make a good-faith effort to keep them up to date.

XCM Proposals once passed should be re-assigned to the current sub-category (i.e. XCM Disclosures).

Network Information:

Brief description of Network such as “[SAMPLE NETWORK] is a EVM compatible smart contract platform that enables developers to build applications using popular Ethereum tools with over 300 projects deployed.”

  • Network website:
  • Network Twitter:
  • Network Discord:
  • Network Telegram:

Key Disclosures

Q1: Is the Blockchain Code Open-Source (and include Github link)?:

If parts of the code are not open source: please provide information on why not

  • A1:

Q2: Is Sudo-enabled on the Network? If Sudo is disabled, is the Network controlled by a select group of addresses?

  • A2:

Q3: Is the Network controlled by a select group of addresses (<50 addresses)?

  • A3:

Q4: Have you completed full testing of this integration in Moonbase Alpha?

  • A4:

Q5: (For Moonbeam XCM/HRMP Proposals Only) Does your network have a Kusama deployment? If yes, please provide Network name and whether your Kusama deployment is integrated with Moonriver

  • A5:

Q6: Is your blockchain code Audited? If yes, please provide: i. the name of Auditors, ii. dates of audit reports and, if available, links to audit reports.

  • A6: