Force DAO is a collective of investment strategists working to identify and productize alpha across DeFi. ForceDAO started with building out strategies on Ethereum and have now expanded strategies to Polygon.
Force DAO’s governance token is $FORCE. The token is designed to be used as the basis for the token governed organization, aligning incentives while keeping it 100% decentralized.
Further resources regarding the ForceDAO can be found on their website, https://www.forcedao.com/.
The bug bounty program is focused around its smart contracts and is mostly concerned with the loss of user funds.
Rewards by Threat Level
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.
Critical payouts are further capped at 10% of economic damage, primarily taking into account the user funds at risk.
Payouts are handled by the ForceDAO team directly and are denominated in USD. However, payouts are done in FORCE.
- Up to USD $100,000
- USD $10,000
- USD $5,000
Assets in scope
- Smart Contract - Storage ContractType
- Smart Contract - Vault ContractType
- Smart Contract - SushiHodlStrategyFactory ContractType
- Smart Contract - MasterChefHodlStrategy ContractType
- Smart Contract - StaticsHelper ContractType
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.
- Critical Smart Contract ImpactCriticalImpact
- High Smart Contract ImpactHighImpact
- Medium Smart Contract ImpactMediumImpact
Out of Scope & Rules
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)
- Incorrect data supplied by third party oracles
- Not to exclude oracle manipulation/flash loan attacks
- Purely informational or optimizational findings of low severity
- Basic economic governance attacks (e.g. 51% attack)
- Lack of liquidity
- Best practice critiques
- Sybil attacks
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