Reserve
The Reserve Protocol is the first platform that allows for the permissionless creation of asset-backed, yield-bearing & overcollateralized stablecoins on Ethereum. The end goal of the Reserve Protocol is to provide highly scalable, decentralized, stable money in contrast to volatile cryptocurrencies such as Bitcoin and Ether.
PoC required
KYC 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 assets
Theft of unclaimed yield
Permanent freezing of unclaimed yield
Protocol insolvency
Temporary freezing of RToken ERC20 functionality
Temporary freezing of funds
Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)
Contract fails to deliver promised returns, but doesn't lose value
Theft of gas
Unbounded gas consumption, that does not cause a more severe bug
Out of scope
- Broken link hijacking is out of scope
- Best practice critiques
| Category | Additional specific vulnerabilities and/or attacks to exclude |
|---|---|
| Smart Contract | RToken minting can be DoS’d by a grief-attack where the attacker redeems an amount equal to the available mint throttle, then mints that amount in the same transaction. |
| Smart Contract | RToken redeeming can be DoS’d by a grief-attack where the attacker mints an amount equal to the available redeem throttle, then redeems that amount in the same transaction. |
| Smart Contract | Malicious governance. We assume governance is trusted and competent for all protocol configurations over which it has control |
| Smart Contract | Malicious guardians. We assume guardians are trusted and competent for their given duties. |
| Smart Contract | Malicious long-freezers. We assume long-freezers are trusted and competent for their given duties. |
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
5.5k