Drift Protocol
Program Overview
Drift Protocol is a decentralized, fully on-chain perpetual swap exchange built on Solana. Drift Protocol also is the first perpetual swap exchange to leverage a Dynamic AMM. A Dynamic AMM is based on a virtual AMM (vAMM), but its key innovative is that it introduces repegging and adjustable k mechanisms to recalibrate liquidity in a trading pool based on participant demand. DAMMs, as a result, have the ability to be more flexible than traditional vAMMs and AMMs, which lead to better capital efficiency and reduced slippage. Drift’s exchange gives traders the ability to take on cross-margined long or short positions with up to 5x leverage with minimal slippage thanks to the protocol’s Dynamic Automated Market Maker (DAMM). The exchange currently has 12 markets available: SOL, BTC, ETH, MATIC, LUNA, AVAX, ATOM and BNB. Since inception, the exchange has traded $1B in cumulative volume as of a month after launch.
For more information about Drift Protocol, please visit https://www.drift.trade/.
This bug bounty program is focused on their smart contracts and is focused on preventing:
- Thefts and freezing of principal of any amount
- Thefts and freezing of unclaimed yield of any amount
- Theft of governance 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.
All Critical Smart Contract bug reports require a PoC and a suggestion for a fix to be eligible for a reward. All High Smart Contract bug reports require a PoC to be eligible for a reward. Explanations and statements are not accepted as PoC and code is required.
Critical smart contract vulnerabilities are capped at 10% of economic damage, primarily taking into consideration funds at risk, but also PR and branding aspects, at the discretion of the team. However, there is a minimum reward of USD 50 000.
Payouts are handled by the Drift Protocol team directly and are denominated in USD. However, payouts are done in USDC.
Smart Contract
- Critical
- Level
- Up to USD $500,000
- Payout
- High
- Level
- USD $50,000
- Payout
- Medium
- Level
- USD $25,000
- Payout
- Low
- Level
- USD $5,000
- Payout
Assets in scope
- Smart Contract - ClearinghouseType
Assets are Listed Below.
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 Contract
- Any governance voting result manipulationCriticalImpact
- Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yieldCriticalImpact
- Permanent freezing of fundsCriticalImpact
- Miner-extractable value (MEV)CriticalImpact
- Protocol InsolvencyCriticalImpact
- Oracle failure/manipulationCriticalImpact
- Theft of unclaimed yieldHighImpact
- Permanent freezing of unclaimed yieldHighImpact
- Temporary freezing of fundsHighImpact
- 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
- Unbounded gas consumptionMediumImpact
- 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, strategist)
Smart Contracts
- Basic economic governance attacks (e.g. 51% attack)
- Lack of liquidity
- Best practice critiques
- Sybil attacks
- Centralization risks
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