Ref Finance
Ref Finance is a community-led, multi-purpose DeFi platform built on NEAR Protocol. Ref takes full advantage of NEAR’s low fees, one-to-two second finality, and WebAssembly-based runtime (hello, Rust smart contracts!).
PoC Required
Vault program
Select the category you'd like to explore
Assets in Scope
Impacts in Scope
Direct theft of any user funds (with value > $250,000), whether at-rest or in-motion, other than unclaimed yield
Permanent freezing of user funds (with value > $250,000)
Miner-extractable value (MEV)
Manipulation of governance voting result deviating from voted outcome and resulting in a direct change from intended effect of original results
Protocol insolvency
Direct theft of any user funds (with value > $5,000 and < $250,000), whether at-rest or in-motion
Temporary freezing of funds (including unclaimed yield) for any amount of time
Permanent freezing of unclaimed yield
Unbounded gas consumption
Smart contract unable to operate due to lack of token funds
Block stuffing
Theft of gas
Out of scope
- Best practice critiques
- Issues related to the frontend without concrete impact and PoC
- Best practices issues without concrete impact and PoC
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