Mars Protocol
Mars Protocol consists of a money market, called Red Bank, and a generalized credit primitive called Credit Accounts. 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 Credit Accounts.
PoC required
Rewards by Threat Level
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 mainnet 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:
Reward Payment Terms
Payouts are handled by the Mars Protocol Foundation and are denominated in USD. However, payouts are done in MARS.
The calculation of the net amount rewarded is based on the average price between CoinMarketCap.com and CoinGecko.com at the time the bug report was submitted. No adjustments are made based on liquidity availability.
Program Overview
Mars Protocol consists of a money market, called Red Bank, and a generalized credit primitive called Credit Accounts. 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 Credit Accounts. The first outpost containing both Red bank and Credit Accounts (dubbed Mars v2) is on Osmosis, and the second outpost which currently contains only the Red Bank is 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 Credit Accounts, 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.
KYC not required
No KYC information is required for payout processing.
Prohibited Activities
- Any testing on mainnet or public testnet deployed code; all testing should be done on local-forks of either public testnet or mainnet
- 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 that are executed against project assets
- Automated testing of services that generates significant amounts of traffic
- Public disclosure of an unpatched vulnerability in an embargoed bounty
- Any other actions prohibited by the Immunefi Rules
Feasibility Limitations
The project may be receiving reports that are valid (the bug and attack vector are real) and cite assets and impacts that are in scope, but there may be obstacles or barriers to executing the attack in the real world. In other words, there is a question about how feasible the attack really is. Conversely, there may also be mitigation measures that projects can take to prevent the impact of the bug, which are not feasible or would require unconventional action and hence, should not be used as reasons for downgrading a bug's severity. Therefore, Immunefi has developed a set of feasibility limitation standards which by default states what security researchers, as well as projects, can or cannot cite when reviewing a bug report.