Moonpot

Moonpot is a win-win lottery on Binance Smart Chain (BSC) with the mission to help as many people as possible grow their assets safely and securely while having fun doing so. Moonpot savings vaults make it simple for anyone to access the bank-beating DeFi interest rates available in crypto. A weekly lottery gives everyone saving via Moonpot the thrill of a possible big win while never putting their deposit at risk.

For more information about Moonpot, please visit https://moonpot.com/.

This bug bounty program is focused on their smart contracts and is focused on preventing the following impacts:

• Loss of user funds staked (principal) by freezing or theft
• Theft of unclaimed yield
• Freezing of unclaimed yield
• Temporary freezing of funds
• Unable to call smart contract
• Smart contract gas drainage
• Smart contract fails to deliver promised returns

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.

A suggestion on how to fix the vulnerability is required for consideration of a reward.

Payouts are handled by the Moonpot team directly and are denominated in USD. However, payouts are done in POTS, BUSD, or BNB, at the discretion of the team.

The Moonpot GitHub is private, but if a PoC ends up being required for full validation of a bug report that is considered credible, access may be provided at the discretion of the team.

Impacts in Scope

Only the following impacts are accepted within this bug bounty program. All other impacts are not considered as in-scope, even if they affect something in the assets in scope table.

Smart Contracts

• Loss of user funds staked (principal) by freezing or theft
• Theft of unclaimed yield
• Freezing of unclaimed yield
• Temporary freezing of funds
• Unable to call smart contract
• Smart contract gas drainage
• Smart contract fails to deliver promised returns

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

Smart Contracts and Blockchain

• Re-entrancy
• Logic errors
  • including user authentication errors
• Solidity/EVM details not considered
  • including integer over-/under-flow
  • including rounding errors
  • including unhandled exceptions
• Trusting trust/dependency vulnerabilities
  • including composability vulnerabilities
• Oracle failure/manipulation
• Novel governance attacks
• Economic/financial attacks
  • including flash loan attacks
• Congestion and scalability
  • including running out of gas
  • including block stuffing
  • including susceptibility to frontrunning
• Consensus failures
• Cryptography problems
  • Signature malleability
  • Susceptibility to replay attacks
  • Weak randomness
  • Weak encryption
• Susceptibility to block timestamp manipulation
• Missing access controls / unprotected internal or debugging interfaces

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)
• 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

The following activities are prohibited by this 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