Rules

✔ Public disclosure of a vulnerability would make it ineligible for a reward.

✔ Technical knowledge is required for the process.

✔ Duplicated issues are not eligible for a reward. The first submission would be the eligible one.

✔ If you want to add more information to a provided issue, create a new submission with a reference to the initial one.

✔ Rewards will be decided on a case-by-case basis, and the bug bounty program, terms, and conditions are at the sole discretion of the MarsDoge team.

✔ Rewards will vary depending on the severity of the issue. Other variables considered for rewards include the quality of the issue description, the instructions for reproducibility, and the quality of the fix (if included).

✔ Determinations of eligibility, score, and all terms related to an award are at the sole and final discretion of the MarsDoge team.

✔ Submissions need to be related to the Bounty Scope. Submissions outside of the Bounty Scope won’t be eligible for a reward.

✔ Any interference with the protocol, client, or platform services, on purpose or not, during the process will make the submission process un-valid.

✔ Our bug bounty programe follows a similar approach as Ethereum Bug Bounty. The severity of the issues will be based according to the OWASP risk rating model based on Impact and Likelihood.

✔ The terms and conditions of the bug bounty process may vary over time.

✔ All payouts are done by the MarsDoge team and are pegged to the USD values set here and are payable in MarsDoge.