DODO
DODO is a decentralized exchange platform powered by the Proactive Market Maker (PMM) algorithm. It features highly capital-efficient liquidity pools that support single-token provision, reduce impermanent loss, and minimize slippage for traders. The trading platform also offers SmartTrade, a decentralized liquidity aggregation service that routes to and compares various liquidity sources to quote the optimal prices between any two tokens.
PoC required
Select the category you'd like to explore
Assets in Scope
Impacts in Scope
Any governance voting result manipulation
Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield
Permanent freezing of funds
Miner-extractable value (MEV)
Protocol insolvency
Theft of unclaimed yield
Permanent freezing of unclaimed yield
Temporary freezing of funds
Smart contract unable to operate due to lack of token funds
Block stuffing for profit
Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)
Theft of gas
Out of scope
The following contracts are out of scope and NO bounty will be paid:
-
contracts/CollateralVault/
-
contracts/DODODrops
-
contracts/Factory/Registries/DODONFTRegistry.sol
-
contracts/Factory/DODONFT.sol
-
contracts/Factory/DODONFT1155.sol
-
contracts/Factory/NFTTokenFactory.sol
-
contracts/GeneralizedFragment/
-
contracts/NFTPool/
-
contracts/SmartRoute/helper/DODONFTRouteHelper.sol
-
contracts/SmartRoute/proxies/DODODropsProxy.sol
-
contracts/SmartRoute/proxies/DODONFTPoolProxy.sol
-
contracts/SmartRoute/proxies/DODONFTProxy.sol
-
contracts/SmartRoute/DODONFTApprove.sol
-
Best practice critiques
- FeeRouteProxy exclusions: FeeRouteProxy.sol won't left any tokens in normal swap, so we don't abandon using tokens in the proxy through specific swap method
Smart Contract specific
- Incorrect data supplied by third party oracles
- Not to exclude oracle manipulation/flash loan attacks
- Impacts requiring basic economic and governance attacks (e.g. 51% attack)
- Lack of liquidity impacts
- Impacts from Sybil attacks
- Impacts involving centralization risks
All categories
- Impacts requiring attacks that the reporter has already exploited themselves, leading to damage
- Impacts caused by attacks requiring access to leaked keys/credentials
- Impacts caused by attacks requiring access to privileged addresses (including, but not limited to: governance and strategist contracts) without additional modifications to the privileges attributed
- Impacts relying on attacks involving the depegging of an external stablecoin where the attacker does not directly cause the depegging due to a bug in code
- Mentions of secrets, access tokens, API keys, private keys, etc. in Github will be considered out of scope without proof that they are in-use in production
- Best practice recommendations
- Feature requests
- Impacts on test files and configuration files unless stated otherwise in the bug bounty program
- Impacts requiring phishing or other social engineering attacks against project's employees and/or customers