Davos-logo

Davos

Davos Protocol is an innovative lending and borrowing platform that introduces DUSD — an omnichain stablecoin with an unbiased monetary policy and fair borrowing rates. By leveraging Liquid Staking Tokens (LSTs), users can collateralize their assets to mint DUSD.

ETH
Polygon
Defi
Lending
Stablecoin
Solidity
Maximum Bounty
$500,000
Live Since
13 February 2023
Last Updated
08 April 2024
  • PoC required

Submit a Bug

Rewards by Threat Level

Smart Contract
Critical
Up to USD $500,000
High
Up to USD $50,000
Medium
Up to USD $5,000
Low
USD $1,000

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/davos-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.

Program Overview

Davos Protocol is an innovative lending and borrowing platform that introduces DUSD — an omnichain stablecoin with an unbiased monetary policy and fair borrowing rates. By leveraging Liquid Staking Tokens (LSTs), users can collateralize their assets to mint DUSD. Users can then maximize their yield by staking, boost-vaulting, or providing liquidity with the borrowed DUSD, all within a single low-interest debt position.

For more information about Davos, please visit https://davos.xyz/.

KYC not required

No KYC information is required for payout processing.

Prohibited Activities

Default prohibited activities
  • Any testing on mainnet or public testnet deployed code; all testing should be done on local-forks of either public testnet or mainnet
  • 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 that are executed against project assets
  • Automated testing of services that generates significant amounts of traffic
  • Public disclosure of an unpatched vulnerability in an embargoed bounty
  • Any other actions prohibited by the Immunefi Rules

Feasibility Limitations

The project may be receiving reports that are valid (the bug and attack vector are real) and cite assets and impacts that are in scope, but there may be obstacles or barriers to executing the attack in the real world. In other words, there is a question about how feasible the attack really is. Conversely, there may also be mitigation measures that projects can take to prevent the impact of the bug, which are not feasible or would require unconventional action and hence, should not be used as reasons for downgrading a bug's severity. Therefore, Immunefi has developed a set of feasibility limitation standards which by default states what security researchers, as well as projects, can or cannot cite when reviewing a bug report.