mStable

Released in May 2020, mStable is a protocol that unites stablecoins, lending and swapping into one robust and easy to use standard. Three major problems confront stablecoin users: significant fragmentation in same-peg assets; lack of native yield when it is being increasingly demanded by users; lack of insurance against permanent capital loss. mStable’s products (SWAP, SAVE and EARN) are built specifically to address these pain-points.

This bug bounty program is further covered by the Armor Alliance Bug Bounty Challenge.

Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System. 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.

Payouts up to USD 50 000 are handled by mStable directly and are denominated in USD. Payouts are made in mUSD. Payouts higher than USD 50 000 are further covered by the Armor Alliance Bug Bounty Challenge and remaining amounts are paid in ARMOR and are subject to a vesting schedule of up to 24 months.

Any Proxy contracts listed in the Assets in Scope table also include the currently active logic contracts, and any external or internal libraries that are used in these.

We are especially interested in receiving and rewarding vulnerabilities of the following types:

• Loss of collateral or unfair payouts in the mStable StakedToken contracts, resulting in a loss of user funds
• Loss of collateral or stealing of funds from the mAsset, resulting in it becoming under-collateralized
• Unfair payouts through SAVE, MINT, REDEEM or SWAP functionalities that results in under-collateralized or affected system
• Manipulating or circumvention of mStable governance mechanism
• Locking or freezing or any of the mStable contracts or inability to upgrade
• Ineffective or error prone forge validation mechanisms

Additionally, mStable seeks reports of the following Immunefi Common Vulnerabilities.

The following Immunefi Commonly Excluded Vulnerabilities are excluded from the mStable bug bounty program.

The following activities are prohibited by bug bounty program:

• Any testing with mainnet or public testnet contracts; all testing should be done on private testnets
• 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