Resonate
Program Overview
Resonate is the DeFi Yield futures protocol. Resonate splits apart the interest and principal components of a yield-bearing position. Those who hold tokens which may be deposited into yield-bearing systems can receive an instant, upfront payment on the present value of that future yield, in exchange for locking their tokens. An ideal solution for traders who want to receive guaranteed and consistent yield farming rewards for staking tokens or providing liquidity.
For those who want to purchase the Yield Futures, or the rights to future yield, Resonate places them in a position where they can do so at a discount to the expected future value of the interest. For protocols wanting to reduce their burn rate, this discount can offer a better way to incentivize providing LPs.
For more information about Resonate, please visit https://www.resonate.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.
All Critical/High/Medium 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.
Rewards for critical smart contract 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 reward of USD 40 000.
Critical website and application bug reports will be rewarded with USD 30 000 only if the impact leads to a direct loss in funds. All other impacts that would be classified as Critical would be rewarded no more than USD 15 000.
Known issues highlighted in the following audit report are considered out of scope:
- Zellic Audit Part 1
- Zellic Audit Part 2
- BlockSec Audit
- BlockSec Oracle Audit
- Bug Bounty Report by GalloDaSballo
Payouts are handled by the Resonate team directly and are denominated in USD. However, payouts are done in USDC or RVST, at the discretion of the team.
Smart Contract
- Critical
- Level
- USD $40,000 to USD $100,000
- Payout
- High
- Level
- USD $40,000
- Payout
- Medium
- Level
- USD $5,000
- Payout
- Low
- Level
- USD $1,000
- Payout
Websites and Applications
- Critical
- Level
- USD $15,000 to USD $30,000
- Payout
- High
- Level
- USD $5,000
- Payout
Assets in scope
- Smart Contract - ResonateType
- Smart Contract - Address Lock ProxyType
- Smart Contract - OutputReceiver ProxyType
- Smart Contract - Resonate Helper (unable to be verified, github link included below)Type
- https://github.com/Revest-Finance/ResonateContracts/blob/public/hardhat/contracts/ResonateHelper.solTargetSmart Contract - Resonate Helper (Github)Type
- Smart Contract - Sandwich Bot ProxyType
- Smart Contract - PriceProviderType
- Smart Contract - Smart Wallet CheckerType
- Smart Contract - Dev WalletType
- Smart Contract - Metadata HandlerType
- Smart Contract - Chainlink USD OracleType
- Smart Contract - PoolSmartWalletType
- Smart Contract - SmartWalletType
- Smart Contract - Yearn Adapter V2Type
- Smart Contract - Curve USD LP OracleType
- Smart Contract - Chainlink OracleType
- Smart Contract - Governance ControllerType
- Smart Contract - Curve ETH LP OracleType
- Smart Contract - LP OracleType
- Smart Contract - Velodrome TWAP OracleType
- Smart Contract - TWAP OracleType
- Smart Contract - Reaper Farms AdapterType
- Smart Contract - Yearn AdapterType
- Smart Contract - Beefy AdapterType
- Smart Contract - Stader sFTMx OracleType
- Websites and Applications - Web/AppType
- Websites and Applications - Web/AppType
All smart contracts of Resonate can be found at https://github.com/Revest-Finance. However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.
If any Critical or High severity impact can be caused to any other asset managed by Resonate 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.
Smart Contract
- Theft of user funds in O(1) transactional complexity, including the theft of user funds from multiple pools within the same transactionCriticalImpact
- Permanent freezing of user fundsCriticalImpact
- Theft of user funds in O(n) transactional complexity, including the theft of user funds from multiple pools requiring multiple transactionsHighImpact
- Temporary freezing of user funds for periods greater than one hour with no escape-hatch available during that periodHighImpact
- Price manipulation via oracle-based attacks that results in theft of value, excluding provider-based attacks such as ChainlinkHighImpact
- Temporary freezing of user funds for periods less than one hour but spanning multiple blocksMediumImpact
- Griefing and/or gas theftMediumImpact
- Admin-based attacks that allow for theft of user-valueMediumImpact
- Price manipulation via oracle-based attacks that results in loss of value, excluding provider-based attacks such as ChainlinkMediumImpact
- Unintentional release of funds ahead of timeMediumImpact
- Smart contract fails to deliver promised returns without losing valueLowImpact
- Price manipulation via oracle-based attacks that do not result in any loss of value, excluding provider-based attacks such as ChainlinkLowImpact
- MEV-based slippage attacks (sandwich bots)LowImpact
Websites and Applications
- Execute arbitrary system commandsCriticalImpact
- Retrieve sensitive data/files from a running server such as /etc/shadow, database passwords, and blockchain keys(this does not include non-sensitive environment variables, open source code, or usernames)CriticalImpact
- Taking state-modifying authenticated actions (with or without blockchain state interaction) on behalf of other users without any interaction by that user, such as, changing registration information, commenting, voting, making trades, withdrawals, etc.CriticalImpact
- Changing the NFT metadataCriticalImpact
- Subdomain takeover with already-connected wallet interactionCriticalImpact
- Direct theft of user fundsCriticalImpact
- Malicious interactions with an already-connected wallet such as modifying transaction arguments or parameters, substituting contract addresses, submitting malicious transactionsCriticalImpact
- Direct theft of user fundsCriticalImpact
- Injection of malicious HTML or XSS through NFT metadataCriticalImpact
- Injecting/modifying the static content on the target application without Javascript (Persistent) such as HTML injection without Javascript, replacing existing text with arbitrary text, arbitrary file uploads, etc.HighImpact
- Takedown of website for periods greater than four hoursHighImpact
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, that rely solely on malicious intent of governance systems, rather than direct takeovers.
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
- Curve reentrancy vulnerabilities, which are not a valid vector against our system.
Websites and Apps
- Theoretical vulnerabilities without any proof or demonstration
- Attacks requiring physical access to the victim device
- Attacks requiring access to the local network of the victim
- Reflected plain text injection ex: url parameters, path, etc.
- This does not exclude reflected HTML injection with or without javascript
- This does not exclude persistent plain text injection
- Self-XSS
- Captcha bypass using OCR without impact demonstration
- CSRF with no state modifying security impact (ex: logout CSRF)
- Missing HTTP Security Headers (such as X-FRAME-OPTIONS) or cookie security flags (such as “httponly”) without demonstration of impact
- Server-side non-confidential information disclosure such as IPs, server names, and most stack traces
- Vulnerabilities used only to enumerate or confirm the existence of users or tenants
- Vulnerabilities requiring un-prompted, in-app user actions that are not part of the normal app workflows
- Lack of SSL/TLS best practices
- DDoS vulnerabilities
- Feature requests
- Issues related to the frontend without concrete impact and PoC
- Best practices issues without concrete impact and PoC
- Vulnerabilities primarily caused by browser/plugin defects
- Leakage of non sensitive api keys ex: etherscan, Infura, Alchemy, etc.
- Any vulnerability exploit requiring browser bugs for exploitation. ex: CSP bypass
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