DODO V3-logo

DODO V3

DODO V3 is a vault maintained jointly by LPs (Liquidity Providers) and SPs (Strategy Providers), with LPs providing funds to the pool and SPs offering strategies. Both LPs and SPs share the fee income.

Arbitrum
Aurora
Avalanche
Base
ETH
Linea
Optimism
Polygon
Scroll
Defi
Crosschain Liquidity
DEX
Yield Aggregator
Solidity
Maximum Bounty
$10,000
Live Since
29 November 2023
Last Updated
18 November 2024
  • PoC required

Rewards

DODO V3 provides rewards in USDC on Avalanche, Arbitrium, denominated in USD.

Rewards by Threat Level

Smart Contract
Critical
Max: $10,000Min: $5,000
Primacy of Impact
High
Max: $5,000Min: $2,000
Primacy of Impact
Medium
Flat: $1,500
Primacy of Impact
Low
Flat: $1,000
Primacy of Impact
Critical Reward Calculation

Mainnet assets:

Reward amount is 10% of the funds directly affected up to a maximum of:

$10,000

Minimum reward to discourage security researchers from withholding a bug report:

$5,000

Rewards are distributed according to the impact the vulnerability could otherwise cause based on the Impacts in Scope table further below.

Reward Calculation for Critical Level Reports.

For critical Smart Contract bugs, the reward amount is 10% of the funds directly affected up to a maximum of USD 10,000. The calculation of the amount of funds at risk is based on the time and date the bug report is submitted. However, a minimum reward of USD 5,000 is to be rewarded in order to incentivize security researchers against withholding a bug report.

Reward Calculation for High Level Reports

  • High vulnerabilities concerning theft/permanent freezing of unclaimed yield/royalties are considered at the full amount of funds at risk, capped at the maximum high reward. This is to incentivize security researchers to uncover and responsibly disclose vulnerabilities that may have not have significant monetary value today, but could still be damaging to the project if it goes unaddressed.
  • In the event of temporary freezing, the reward doubles from the full frozen value for every additional 24h that the funds are temporarily frozen, up until a max cap of the high reward. This is because as the duration of the freezing lenghents, the potential for greater damage and subsequent reputational harm intensifies. Thus, by increasing the reward proportionally with the frozen duration, the project ensures stronger incentives for bug disclosure of this nature.

Repeatable Attack Limitations

  • If the smart contract where the vulnerability exists can be upgraded or paused, only the initial attacks within the first hour will be considered for a reward. This is because the project can mitigate the risk of further exploitation by upgrading or pausing the component where the vulnerability exists. The reward amount will depend on the severity of the impact and the funds at risk.
  • For critical repeatable attacks on smart contracts that cannot be upgraded or paused, the project will consider the cumulative impact of the repeatable attacks for a reward. This is because the project cannot prevent the attacker from repeatedly exploiting the vulnerability until all funds are drained and/or other irreversible damage is done. Therefore, this warrants a reward equivalent to 10% of funds at risk, capped at the maximum critical reward.

Proof of Concept (PoC) Requirements

A PoC is required for the following severity levels:

  • Smart Contract + Critical + PoC Required
  • Smart Contract + High + PoC Required
  • Smart Contract + Medium + PoC Required
  • Smart Contract + Low + PoC Required

All PoCs submitted must comply with the Immunefi-wide PoC Guidelines and Rules. Bug report submissions without a PoC when a PoC is required will not be provided with a reward.

Reward Payment Terms

Payouts are handled by the DODO V3 team directly and are denominated in USD. However, payments are done in USDC.

Program Overview

DODO V3 is a vault maintained jointly by LPs (Liquidity Providers) and SPs (Strategy Providers), with LPs providing funds to the pool and SPs offering strategies. Both LPs and SPs share the fee income.

For more information about DODO v3, please visit https://dodoex.io/en

DODO v3 provides rewards in USDC. For more details about the payment process, please view the Rewards by Threat Level section further below.

Primacy of Impact vs Primacy of Rules

DODO V3 adheres to the Primacy of Impact for the following severity levels:

  • Smart Contract - Critical
  • Smart Contract - High
  • Smart Contract - Medium
  • Smart Contract - Low

If a category’s severity level is covered within the Primacy of Impact, it means that even if the impacted asset is not in-scope but is owned by the project, then it would be considered as in-scope of the bug bounty program as long as it involves an impact under that respective severity level. When submitting a report, just select the Primacy of Impact asset placeholder. If the team behind this project has multiple projects, those other projects are not covered under the Primacy of Impact of this program. Instead, check if those other projects have a bug bounty program on Immunefi.

Testnet and mock files are not covered under the Primacy of Impact.

All other severity levels not listed here are considered under the Primacy of Rules, which means that they are bound by the terms of the bug bounty program.

KYC not required

No KYC information is required for payout processing.

Proof of Concept

Proof of concept is always required for all severities.

Responsible Publication

Category 3: Approval Required

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.

Severity
Min. - Max.
Critical
$5k -$10k
High
$2k -$5k
Medium
$1.5k
Low
$1k
Total Assets in Scope
12