Revault
Submit a BugProgram Overview
Revault brings the power of easy search navigation to the DeFi ecosystem, enabling anyone to find and deposit funds in the best performing vaults on any blockchain at any given time.
The REVA token incentivizes users to use Revault as their go-to gateway to DeFi. Using Revault, users will receive all the rewards from their selected vault plus rewards of our REVA tokens, making depositing through Revault’s search & maximize engine the best choice for any asset. Revault simply relays funds — they don’t compete with other vault projects on strategies or APY.
For more information about Revault, please visit https://www.revault.network/.
This bug bounty program is focused on their smart contracts and is focused on preventing the following impacts:
- Thefts and freezing of principal of any amount
- Thefts and freezing of unclaimed yield of any amount
- Theft of governance funds
- Governance activity disruption
- Leak of user data
- Deletion of user data
- Access to sensitive pages without authorization
Rewards by Threat Level
Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System. This is a simplified 5-level scale, with separate scales for websites/apps and smart contracts/blockchains, encompassing everything from consequence of exploitation to privilege required to likelihood of a successful exploit.
For smart contract bugs, a PoC must be provided for High and Critical vulnerabilities, and a suggestion for a fix must be provided for Medium smart contract bug reports and higher.
Please note that all resolved issues, and any open or partially resolved issues from either of our audits (Certik, Paladin) are out of the scope of the bug bounty.
Critical vulnerabilities are further capped at 10% of economic damage, with the main consideration being the funds affected in addition to PR and brand considerations, at the discretion of the team. However, there is a minimum of USD 50 000 for Critical bug reports.
Payouts are handled by the Revault team directly and are denominated in USD. However, payouts are done in BUSD or REVA, at the discretion of the team.
Smart Contract
- Critical
- Level
- Up to USD $250,000
- Payout
- High
- Level
- USD $25,000
- Payout
- Medium
- Level
- USD $10,000
- Payout
- Low
- Level
- USD $1,000
- Payout
Assets in scope
- Smart Contract - REVA TokenType
- Smart Contract - vREVA TokenType
- Smart Contract - vREVA Token DeploymentType
- Smart Contract - Reva Chef (Proxy)Type
- Smart Contract - Reva Chef (Implementation)Type
- Smart Contract - Revault (Proxy)Type
- Smart Contract - Revault (Implementation)Type
- Smart Contract - REVA Fee Receiver (Proxy)Type
- Smart Contract - REVA Fee Receiver (Implementation)Type
- Smart Contract - REVA LP Fee Receiver (Proxy)Type
- Smart Contract - REVA LP Fee Receiver (Implementation)Type
- Smart Contract - REVA Staking Pool (Proxy)Type
- Smart Contract - REVA Staking Pool (Implementation)Type
- Smart Contract - REVA LP Staking Pool (Proxy)Type
- Smart Contract - REVA LP Staking Pool (Implementation)Type
- Smart Contract - Zap (Proxy)Type
- Smart Contract - ZAP (Implementation)Type
- Smart Contract - ZapAndDeposit (Proxy)Type
- Smart Contract - ZapAndDeposit (Implementation)Type
- Smart Contract - REVA autocompund Stacking Pool (Proxy)Type
- Smart Contract - REVA autocompund Stacking Pool (Implementation)Type
Further information about Revault can be found at https://github.com/Revault-network. However, only those in the assets in scope table are considered as in-scope of the bug bounty program.
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.
Smart Contract
- Any governance voting result manipulationCriticalImpact
- Permanent freezing of fundsCriticalImpact
- Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yieldCriticalImpact
- Miner-extractable value (MEV)CriticalImpact
- Protocol InsolvencyCriticalImpact
- Theft of unclaimed yieldHighImpact
- Permanent freezing of unclaimed yieldHighImpact
- Temporary freezing of fundsHighImpact
- Smart contract unable to operate due to lack of token fundsMediumImpact
- Block stuffing for profitMediumImpact
- Unbounded gas consumptionMediumImpact
- Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)MediumImpact
- Theft of gasMediumImpact
- 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