Revert
Revert develops analytics and management tools for liquidity providers in AMM protocols.
PoC required
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.
Program Overview
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/.
KYC not required
No KYC information is required for payout processing.
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.