Raydium
Raydium is an automated market maker (AMM) built on Solana.
PoC Required
Select the category you'd like to explore
Assets in Scope
Impacts in Scope
Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield
Permanent freezing of funds
Vulnerabilities that could freeze user funds permanently or involve the draining or theft of funds without user transaction approval
Theft of unclaimed yield
Permanent freezing of unclaimed yield
Temporary freezing of funds for any amount of time
Vulnerabilities that could freeze user funds temporarily or intentionally alter the value of user funds
Smart contract unable to operate due to lack of token funds
Block stuffing for profit
Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)
Theft of gas
Unbounded gas consumption
Out of scope
Raydium's AMMv4 is currently in Status 6, which means it does not share liquidity to OpenBook (or Serum). This Status will not change and AMMv4 is pending an upgrade to remove OpenBook depenencies, as such, bugs pertaining to OpenBook markets, OpenBook open orders, or anything related to the OpenBook codebase that is not being used are considered out of scope for this bug bounty program.
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