The Moonriver parachain on Kusama and the Moonbeam parachain on Polkadot (estimated launch in Jan 2022) are both included in the assets-in-scope. 

All source code of Moonbeam can be found at [https://github.com/PureStake/](https://github.com/PureStake/). However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.

Moonbeam is an Ethereum-compatible smart contract platform on the Polkadot network that makes it easy to build natively interoperable applications. This Ethereum compatibility allows developers to deploy existing Solidity smart contracts and DApp frontends to Moonbeam with minimal changes. As a parachain on the Polkadot network, Moonbeam benefits from the shared security of the Polkadot relay chain and integrations with other chains that are connected to Polkadot.

An attack triggering the network not being able to confirm new transactions (Total network shutdown)

An attack causing an unintended permanent chain split requiring hard fork (Network partition requiring hard fork)

An attack causing direct loss of funds

An attack causing permanent freezing of funds (fix requires hardfork)

An attack causing the minting/creation of network utility tokens (MOVR/GLMR) outside of the normal, on-chain inflation mechanism

Ability to execute system commands

Extract Sensitive data/files from the server such as /etc/passwd

Stealing User Cookies

Signing transactions for other users

Redirection of user deposits and withdrawals

Wallet interaction modification resulting in financial loss

Subdomain takeover resulting in financial loss (applicable for subdomains with addresses published)

Direct theft of user funds

Tampering with transactions submitted to the user’s wallet

Submitting malicious transactions to an already-connected wallet

An attack causing an unintended chain split (Network partition)

An attack causing transient consensus failures; which recover without manual intervention

Spoofing content on the target application (Persistent)

Users Confidential information disclosure such as Email

Privilege escalation to access unauthorized functionalities

Taking down the application/website

An attack causing high compute consumption by validator/mining nodes

Attacks that are limited to thin clients and cannot be exploited against full nodes

DoS of greater than 30% of validator or miner nodes and does not shut down the network

An attack causing an RPC API crash

Changing details of other users without direct financial impact (CSRF)

Third-Party API keys leakage that demonstrates loss of funds or modification on the website

Redirecting users to malicious websites (Open Redirect)

A bug in layer 1 blockchain code resulting in unintended smart contract behavior (no concrete funds at risk)

DoS of greater than 10% but less than 30% of validator or miner nodes and does not shut down the network

An exploit underpricing transaction fees relative to computation time

Framing sensitive pages leading to financial loss (ClickJacking)

Any impact involving a publicly released CVE without a working PoC

Rewards are distributed according to the impact of the vulnerability based on the [Immunefi Vulnerability Severity Classification System V2.2](https://immunefi.com/immunefi-vulnerability-severity-classification-system-v2-2). This is a simplified 5-level scale, with separate scales for websites/apps and smart contracts/blockchains, encompassing everything from consequence of exploitation to privilege required to likelihood of a successful exploit.

All web/app bug reports must come with a PoC in order to be considered for a reward. For smart contract bug reports, at the discretion of the team, a PoC may be required in order to determine if the bug exists, and if necessary, to calculate the extent of the damage the bug could have if exploited. 

The payout for __critical vulnerabilities__ is dependent on the ratio between the funds at risk and the combined __market cap__ (as listed on coinmarketcap on the day of the report) of the Moonbeam and Moonriver Blockchains. 

This ratio is known as the __“risk ratio”__, i.e.:

Risk Ratio = Funds at Risk / ( Moonbeam Market Cap + Moonriver Market Cap)

The exact payout is determined as follows:

  - If the risk ratio is at or below 0.5, the payout is calculated linearly between 0$ and 250K.
  - If the risk ratio is above 0.5, the payout is calculated linearly between $250K and $1M; with a maximum cap of $1M

This results in the following payout graph:
![MoonbeamNEW](//images.ctfassets.net/t3wqy70tc3bv/1qjh15sfrhugcw7vcTgam4/6cef8abcb10e83f0d255bb2ed7337515/MoonbeamNEW)

Note that a bug reported for one of either the Moonbeam or Moonriver networks that applies to both will be treated as a single report and paid only once. 

The Moonbeam Foundation requires KYC to be done for all bug bounty hunters submitting a report and wanting a reward. The information needed is an ID scan along with a selfie to verify identity. 

Payouts are handled by the __Moonbeam Foundation__ team directly and are denominated in USD. However, payouts are done in __USDT__ or __USDC__.

The Moonriver parachain on Kusama and the Moonbeam parachain on Polkadot (estimated launch in Jan 2022) are both included in the assets-in-scope. 

All source code of Moonbeam can be found at [https://github.com/PureStake/](https://github.com/PureStake/). However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.

Moonbeam Network

Resources & Documentation