dHEDGE is a one-stop location for managing investment activities on the blockchain where you can put your capital to work in different strategies based on a transparent track record. Multi-chain, non-custodial, decentralized asset management integrated with multiple protocols; allowing for trades, providing liquidity and yield farming.
For more information about dHEDGE, please visit https://app.dhedge.org/.
This bug bounty program is focused on their smart contracts and is focused on preventing:
- Loss of user funds by freezing or theft
- Loss of governance funds
- Theft of unclaimed yield
- Freezing of unclaimed yield
- Temporary freezing of funds for any amount of time
- Deposit and withdrawal bugs
- Protocol integration bugs
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 and smart contracts/blockchains, encompassing everything from consequence of exploitation to privilege required to likelihood of a successful exploit.
There is one exception for this bug bounty program, which overrides one vulnerability in the vulnerability scale, in the above Immunefi Vulnerability Severity Classification System:
- The vulnerability of: “Token holders temporarily unable to transfer holdings” will be classified under this bug bounty program as a medium vulnerability.
Vulnerabilities marked as “Acknowledged” in the https://www.certik.org/projects/dhedge are not eligible for a reward.
dHedge vaults are trust minimized, meaning that the vault manager may not follow a set strategy, or may make bad trades, including trades with poor slippage. A complete loss of funds is possible via poor risk-management strategies by the manager. These types of losses are not in scope for the bounty.
Payouts are handled by the dHEDGE team directly and are denominated in USD. However, payouts are done in USDC.
- USD $50,000
- USD $10,000
- USD $2,000
- USD $1,000
Assets in scope
- Smart Contract - GovernanceType
- Smart Contract - Pool Factory ProxyType
- Smart Contract - Pool FactoryType
- Smart Contract - Pool LogicType
- Smart Contract - Pool Manager LogicType
- Smart Contract - Asset HandlerType
- Smart Contract - ERC20 GuardType
- Smart Contract - Aave Lending Pool Asset GuardType
- Smart Contract - Balancer V2 GuardType
- Smart Contract - dUSD aggregatorType
- Smart Contract - ERC20 GuardType
All smart contracts of dHEDGE can be found at https://github.com/dhedge/V2-Public and https://github.com/dhedge/V2-Public/tree/production. dHEDGE deployed contracts that are currently linked to the Pool Factory are considered in scope, including other chains such as Optimism.
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.
- Loss of user funds staked (principal) by freezing or theftCriticalImpact
- Loss of governance fundsCriticalImpact
- Any governance voting result manipulationCriticalImpact
- Permanent freezing of fundsCriticalImpact
- Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yieldCriticalImpact
- Miner-extractable value (MEV)CriticalImpact
- Protocol InsolvencyCriticalImpact
- Theft of unclaimed yieldHighImpact
- Temporary freezing of funds for any amount of timeHighImpact
- Permanent freezing of unclaimed yieldHighImpact
- Unable to call smart contractMediumImpact
- Smart contract gas drainageMediumImpact
- Smart contract unable to operate due to lack of token fundsMediumImpact
- Block stuffing for profitMediumImpact
- Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)MediumImpact
- Theft of gasMediumImpact
- Temporary freezing of fundsMediumImpact
- Unbounded gas consumptionMediumImpact
- Smart contract fails to deliver promised returns, but doesn’t lose valueLowImpact
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, DAO)
- Attacks by privileged manager accounts which relate to poor trading practices or slippage.
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