Davos
Submit a BugProgram Overview
Davos is a leading cross-chain lending and borrowing platform that allows users to borrow the DAVOS Stable Asset against at first their staked MATIC assets, and earn additional yields from the DAVOS yield-bearing Stable Asset in a single debt position against a low interest.
For more information about Davos, please visit https://davos.xyz/.
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, smart contracts, and blockchains/DLTs, focusing on the impact of the vulnerability reported.
All bug reports must come with a PoC with an end-effect impacting an asset-in-scope in order to be considered for a reward. Explanations and statements are not accepted as PoC and code is required. Bug reports are required to include a runnable PoC in order to prove impact. Exceptions may be made in cases where the vulnerability is objectively evident from simply mentioning the vulnerability and where it exists. However, the bug reporter may be required to provide a PoC at any point in time.
All rewards for the project bug bounty program are scaled based on an internally established team criteria, taking into account the exploitability of the bug, the impact it causes, and the likelihood of the vulnerability presenting itself, which is especially factored in with bug reports requiring multiple conditions to be met that are currently not in-place. However, there is a minimum reward of USD 1 000 for each severity level, rewards will be provided at the determined fair value by the team depending on these conditions, assuming that the bug report is in-scope of the bug bounty program.
All vulnerabilities marked in https://github.com/davos-money/new-davos-smart-contracts/tree/main/audits are not eligible for a reward.
Payouts are handled by the Davos team directly and are denominated in USD. However, payouts are done in USDT, USDC and BUSD, with the choice of the ratio at the discretion of the team.
Smart Contract
- Critical
- Level
- Up to USD $500,000
- Payout
- High
- Level
- Up to USD $50,000
- Payout
- Medium
- Level
- Up to USD $5,000
- Payout
- Low
- Level
- USD $1,000
- Payout
Assets in scope
- Smart Contract - ABACIType
- Smart Contract - ClipType
- Smart Contract - DogType
- Smart Contract - GemJoinType
- Smart Contract - DavosJoinType
- Smart Contract - JugType
- Smart Contract - DavosType
- Smart Contract - SpotType
- Smart Contract - VatType
- Smart Contract - VowType
- Smart Contract - Davos ProviderType
- Smart Contract - Ceros RouterType
- Smart Contract - Ceros Yield Converter StrategyType
- Smart Contract - Waiting PoolType
- Smart Contract - Master VaultType
- Smart Contract - CeVaultType
- Smart Contract - InteractionType
- Smart Contract - Auction ProxyType
- Smart Contract - JarType
- Smart Contract - dMaticType
All smart contracts of Davos can be found at https://github.com/davos-money. However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.
Though only the proxy contracts are listed as in-scope, current implementation and any further updates to the implementation contracts are considered in scope. When reporting a bug, please make sure to select the relevant proxy smart contract as the target.
If an impact can be caused to any other asset managed by Davos that isn’t on this table but for which the impact is in the Impacts in Scope section below, you are encouraged to submit it for the consideration by the project.
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
- Theft of unclaimed yieldHighImpact
- Theft of unclaimed royaltiesHighImpact
- Permanent freezing of unclaimed yieldHighImpact
- Permanent freezing of unclaimed royaltiesHighImpact
- Temporary freezing of funds for at least 30 daysHighImpact
- 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
- 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, 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
- 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