All code of Range Protocol can be found at [https://github.com/Range-Protocol/contracts.](https://github.com/Range-Protocol/contracts) Documentation for the assets provided in the table can be found at [https://range-protocol.gitbook.io/range-protocol/. ](https://range-protocol.gitbook.io/range-protocol/)

SkateFi is an infrastructure provider for on-chain money managers. This bug bounty program pertains to the SkateFi’s vaults smart contracts that are built on top of Uniswap V3-like concentrated liquidity AMMs for arbitrary liquidity provision: one-sided, lop-sided, and balanced. The vaults provide a Uniswap-V2 like interface which enables providing fungible liquidity.

Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield

Permanent freezing of funds

Protocol insolvency

Theft of unclaimed yield

Permanent freezing of unclaimed yield

Temporary freezing of funds

Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)

Rewards are distributed according to the impact the vulnerability could otherwise cause based on the Impacts in Scope table further below. 

__Reward Calculation for Critical Level Reports__

For critical Smart Contract bugs, the reward amount is 10% of the funds directly affected up to a maximum of USD 50 000. The calculation of the amount of funds at risk is based on the time and date the bug report is submitted. However, a minimum reward of USD 20 000 is to be rewarded in order to incentivize security researchers against withholding a bug report.

__Repeatable Attack Limitations__

In cases of repeatable attacks for smart contract bugs, only the first attack will be counted, regardless of whether the smart contract is upgradable, pausable, or killable.

__Public Disclosure of Known Issues__

Bug reports covering previously-discovered bugs acknowledged below are not eligible for any reward through the bug bounty program. 
- All of the issues described in the following audit reports should be considered known.

__Previous Audits__

SkateFi has provided these completed audit review reports for reference. Any unfixed vulnerability mentioned in these reports are not eligible for a reward.
- [https://github.com/Range-Protocol/vertex-vault/blob/main/Vertex-Vault-Report.pdf](https://github.com/Range-Protocol/vertex-vault/blob/main/Vertex-Vault-Report.pdf)
- [https://github.com/Range-Protocol/contracts/blob/master/audits/Halborn-Audit.pdf](https://github.com/Range-Protocol/contracts/blob/master/audits/Halborn-Audit.pdf)
- [https://github.com/Range-Protocol/contracts/blob/master/audits/Veridise-Audit.pdf](https://github.com/Range-Protocol/contracts/blob/master/audits/Veridise-Audit.pdf)
- [https://github.com/Range-Protocol/contracts/blob/izumi-implementation/audits/Salusec-Audit.pdf](https://github.com/Range-Protocol/contracts/blob/izumi-implementation/audits/Salusec-Audit.pdf)
- [https://github.com/Range-Protocol/contracts/blob/master/audits/Certik-Audit.pdf](https://github.com/Range-Protocol/contracts/blob/master/audits/Certik-Audit.pdf)
- https://github.com/Range-Protocol/contracts/blob/master/audits/range-veridise-vault-diff-audit.pdf

__Feasibility Limitations__

Bug reports that require an attack that involve one or more other protocols (e.g. utilizing flash loans from a margin protocol or manipulating the spot prices on a DEX), either to make an attack more severe than it would be in isolation, or to achieve an attack that would otherwise be impossible or infeasible, would be both a reduction in the severity level and a corresponding decrease in the payout. However, they will be considered as in-scope and categorized according to the program rules as long as all of the following are true:
- Losses or other negative effects of the attack are inflicted upon Range Protocol ecosystem participants 
- The additional protocols used must have enough liquidity in various assets to allow the attack to succeed at the time of bug report submission. For example: if an attack requires an ETH flash loan, but the amount is larger than all the ETH available for loan across the ecosystem

__Proof of Concept (PoC) Requirements__

A PoC is required for the following severity levels:
- Smart Contract - Critical - PoC Required
- Smart Contract - High - PoC Required
- Smart Contract - Medium - PoC Required

All PoCs submitted must comply with the Immunefi-wide [PoC Guidelines and Rules.](https://immunefisupport.zendesk.com/hc/en-us/articles/9946217628561-Proof-of-Concept-PoC-Guidelines-and-Rules) Bug report submissions without a PoC when a PoC is required will not be provided with a reward.

__Other Terms and Information__

All the listed assets above are branches from the same repository. The codebase across all of the branches is similar in functionality and is built on top of either Uniswap V3, Pancakeswap V3 or Algebra, with Swapsicle using Algebra Integral The following files/directories are included in audit scope from all branches.
- contracts/RangeProtocolVaultStorage.sol
- contracts/RangeProtocolVault.sol
- contracts/RangeProtocolFactory.sol
- contracts/access/OwnableUpgradeable.sol
- contracts/interfaces
- contracts/errors

The following additional files/directories are included in the branches named next to them:
- [https://github.com/Range-Protocol/contracts/tree/wrap-bnb-implementation-one/contracts/libraries](https://github.com/Range-Protocol/contracts/tree/wrap-bnb-implementation-one/contracts/libraries) (wrap-bnb-implementation-one)
- [https://github.com/Range-Protocol/contracts/tree/izumi-implementation/contracts/libraries ](https://github.com/Range-Protocol/contracts/tree/izumi-implementation/contracts/libraries)(izumi-implementation)

__Reward Payment Terms__

Payouts are handled by the Range Protocol team directly and are denominated in USD. However, payments are done in USDT.

SkateFi

Resources & Documentation