Mars Protocol

Mars Protocol consists of a money market, called Red Bank, and a generalized credit primitive called Rover. Mars Protocol utilizes a so-called hub and outpost topology, whereby its base, Mars Hub is the command center for Mars outposts. Each outpost can consist of instances of Red Bank and/or Rover. The first outpost containing both Red bank and Rover is on Osmosis, and the second outpost which currently contains the Red Bank only has now been deployed to Neutron.

Built for the Cosmos ecosystem, Mars Protocol is Built using the Cosmos SDK. Mars Hub will serve as the homebase for all of Mars’ outposts throughout the Cosmos galaxy. Each outpost consists of an instance of Red Bank and optionally Rover, which are deployed onto independent chains. Outposts are bound together by Mars Hub which is responsible for governance and treasury including protocol revenue distribution.

A new MARS token was minted on Mars Hub and will circulate freely throughout the Cosmos ecosystem.

For more information about the Mars Protocol, please visit whitepaper.marsprotocol.io.

Rewards are distributed according to the impact of the vulnerability based on the ImmuneFi Vulnerability Severity Classification System V2.2. This is a simplified 5-level scale, with separate scales for websites/apps, smart contracts, and blockchains/DLTs, focusing on the impact of the vulnerability reported.

All bug reports must come with a PoC with an end-effect impacting an asset-in-scope in order to be considered for a reward. Explanations and statements are not accepted as PoC and code is required.

Rewards for critical blockchain/DLT and critical smart contract vulnerabilities are further capped at 10% of the economic damage potentially caused. However, there is a minimum reward of USD 20 000 and a maximum reward of USD 100 000.

All issues highlighted in the following audit reports are considered out of scope of the program:

• Audits reports for Mars Hub, Periphery contracts and the Osmosis outposts

Payouts are handled by the Mars Protocol contributors and are denominated in USD. However, payouts are denominated in USDC.

Blockchain/DLT

Smart Contract

Assets in scope are as follows:

• Mars Hub testnet
• Mars Hub mainnet
• Periphery contracts on Mars Hub testnet and mainnet
• Osmosis Mars Outpost: ‘red-bank’, and ‘v2-fields-of-mars’ repositories (only)
• Neutron Mars Outpost: ‘red-bank’

The codebase associated with Mars Hub’s testnet and mainnet can be found at https://github.com/mars-protocol/hub. The smart contracts that are deployed on Mars Hub testnet and mainnet (can be found at https://github.com/mars-protocol/periphery. Red Bank related smart contracts deployed onto the Osmosis, and Neutron blockchains can be found at https://github.com/mars-protocol/red-bank. Fields of Mars smart contracts deployed onto Osmosis blockchain can be found at https://github.com/mars-protocol/v2-fields-of-mars.

If an impact can be caused to any other asset managed by Mars Hub or its Osmosis outpost,that isn’t on this table but for which the impact is in the Impacts in Scope section below, you are encouraged to submit it for consideration by the project.

The following vulnerabilities are excluded from the rewards for this bug bounty program:

• Attacks that the reporter has already exploited themselves, leading to damage
• Attacks requiring access to leaked keys/credentials
• Attacks requiring access to privileged addresses (governance, strategist)
• Attacks found in an underlying Cosmos SDK standard module dependency (vulnerabilities found in code that is not Mars Protocols code, but Mars Protocol has a dependency on through Cosmos SDK)

Smart Contracts and Blockchain

• Incorrect data supplied by third party oracles
  • Not to exclude oracle manipulation/flash loan attacks
• Basic economic governance attacks (e.g. 51% attack)
• Lack of liquidity
• Best practice critiques
• Sybil attacks
• Centralization risks
• Lack of funding for contracts that require topping up from an external address e.g.contracts pertaining to incentives e.t.c. (where applicable)
• DoS related attacks

The following activities are prohibited by this bug bounty program:

• Any testing with mainnet contracts; all testing should be done on private testnets. Any testing on public testnets should be done with care to not disclose vulnerabilities to blackhats.
• Any testing with pricing oracles or third party smart contracts
• Attempting phishing or other social engineering attacks against our employees and/or customers
• Any testing with third party systems and applications (e.g. browser extensions) as well as websites (e.g. SSO providers, advertising networks)
• Any denial of service attacks
• Automated testing of services that generates significant amounts of traffic
• Public disclosure of an unpatched vulnerability in an embargoed bounty