XCM Disclosure: Acala

XCM/HRMP XCM Disclosures
1

Network Information:

Acala is an appchain powering Web3 finance. Acala’s Ethereum-compatible blockchain has built-in DeFi protocols for application developers to leverage, including a trustless staking derivative (liquid DOT — LDOT), a decentralized exchange, the over-collateralized aUSD stablecoin, and the EVM+, a hybrid EVM offering fully Ethereum-compatible development environment plus full compatibility with Substrate. Karura is Acala’s sister parachain to serve the Kusama ecosystem and shares the same codebase as Acala.

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

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

  • A2: Sudo is disabled for both the Acala and the Karura(The canary network of Acala deployed on Kusama). The network is controlled by the ACA holders via governance

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

  • A3: No. The Acala Network is controlled by the ACA holders via governance, who can propose any changes via referenda

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

  • A4: Yes

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: Yes, we have a canary network on Kusama, called Karura. And Karura is connected with Moonriver through the HRMP Channel.

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.