Only code involving runtime pallets of Acala are considered as in-scope of the bug bounty program. Modules that are not in runtime pallets like tests, those under development, and those that are not live, are considered as out-of-scope of the bug bounty program. 

However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.

Acala is the decentralized finance network and liquidity hub of Polkadot. It’s a layer-1 smart contract platform that’s scalable, Ethereum-compatible, and optimized for DeFi with built-in liquidity and ready-made financial applications.

Blocking or modifying processes for governance or users from performing their tasks, generating not handled on-chain errors

Putting on-chain data into an unexpected state without interrupting the system or users from performing their tasks, e.g. generating redundant events, logs, etc.

Transaction/consensus manipulation

Double-spending

Unauthorized token minting

Getting access to an identity that can lead to unauthorized access to system’s or user’s assets

Governance compromise

Acala Codebase

Rewards are distributed according to the impact of the vulnerability based on the following severity scale:

__Critical__: transaction/consensus manipulation, double-spending, unauthorized token minting, governance compromise, getting access to an identity that can lead to unauthorized access to system’s or user’s assets. 

__High__: blocking or modifying processes for governance or users from performing their tasks, generating not handled on-chain errors. These actions can lead to blocking users or governance from accessing their assets or performing system functions.

__Medium__: Putting on-chain data into an unexpected state without interrupting the system or users from performing their tasks, e.g. generating redundant events, logs, etc.

Critical vulnerabilities involving a direct loss of user funds, double spending, or the minting of tokens are capped at 10% of the economic damage, taking primarily into consideration the funds at risk or the amount of tokens that can be minted but also branding and PR considerations, at the discretion of the team. However, there is a minimum reward of __USD 50 000__. Consensus manipulation or governance compromise results in the full __USD 500 000__. 

PoC is required for all submissions. Suggestion for a fix is not required, but its addition may be grounds for a bonus provided by the team at its discretion.

A reward can only be provided if:

  - The Bug wasn't reported before.
  - The Bounty Hunter does not disclose the Bug to other parties or publicity until it's fixed by the Acala Team.
  - The Hunter didn't exploit the vulnerability or allow anyone else to profit from it.
  - The Hunter reports a Bug without any additional conditions or threats.
  - The investigation was NOT conducted with Ineligible methods or Prohibited Activities, defined in this document.
  - The Hunter should reply to our additional questions regarding the reproduction of the reported bug (if they follow) within a reasonable time.
  - When duplicate bug reports occur, we reward only the first one if it's provided with enough information for reproduction.
  - When multiple vulnerabilities are caused by one underlying issue, we will reward only the first reported.
  - The vulnerability is found in runtime pallet of Karura (no tests, or modules that aren’t in runtime, e.g. live, can be considered as vulnerability)

Payouts are handled by the __Acala__ team directly in crypto tokens of their choices, valued at the US dollar market rates, e.g. __DOT, ACA, aUSD__.