Revert develops analytics and management tools for liquidity providers in AMM protocols.
Revert Compoundor protocol allows for the automation through awarding executors (compoundors) a small fee to compensate for their gas costs, and a simple mechanism that incentivizes the compounding of positions as close to optimal as possible.
For more information about Revert, please visit https://revert.finance/.
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.
Critical/High severity 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. Critical/High severity bug reports must also come with a suggestion for a fix to be considered for a reward.
Prior to the official launch of Revert, this bug bounty program will also have a hard cap of USD 30 000. In the event that multiple bug reports are submitted that exceed this amount, the rewards will be provided on a first come first served basis. This program will be taken down once all USD 30 000 of rewards have been paid out.
The following known issues are considered to be out of scope of this program:
- Calling the autoCompound() function can be frontrun by MEV txs and recommend using flashbots for anyone who wants to do auto-compounding / build an auto-compounder bot.
- The function which swaps the two tokens into ratio to be added as liquidity is not 100% accurate (because of slippage, bonus calculation) but should always add the majority of the available tokens as liquidity to the position - and the remaining tokens MUST be added to the internal token balances.
- The protocol is not intended to work with any kind of deflationary, rebasing, fee-on-transfer, or any non-standard erc20 behavior tokens.
Payouts are handled by the Revert team directly and are denominated in USD. However, payouts are done in USDC.
- USD $100,000
- USD $5,000
- USD $2,000
- USD $1,000
Assets in scope
- Smart Contract - CompoundorType
- Smart Contract - ICompoundorType
All smart contracts of Revert can be found at https://github.com/revert-finance/compoundor. However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.
If any Critical/High severity impact can be caused to any other asset managed by Revert 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.
- Direct theft of any user principals (Uniswap V3 NFTs) other than unclaimed fees / bonuses / remaining balances from collected fees not compoundedCriticalImpact
- Permanent freezing of any user principals other than unclaimed fees / bonuses / remaining balances from collected fees not compoundedCriticalImpact
- Protocol InsolvencyCriticalImpact
- Theft of unclaimed fees / bonuses / remaining balances from collected fees not compoundedHighImpact
- Permanent freezing of unclaimed fees / bonuses / remaining balances from collected fees not compoundedHighImpact
- Smart contract unable to operate due to lack of token fundsMediumImpact
- Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)MediumImpact
- 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