Jito
The Jito Foundation
PoC Required
KYC required
Select the category you'd like to explore
Assets in Scope
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.
Direct loss of funds
Permanent freezing of funds (fix requires hardfork)
Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield
Permanent freezing of funds
Network not being able to confirm new transactions (total network shutdown)
Unintended permanent chain split requiring hard fork (network partition requiring hard fork)
Unintended chain split (network partition)
Theft of protocol revenue
Theft of Yield
Temporary freezing of network transactions by delaying one block by 500% or more of the average block time
Increasing network processing node resource consumption by at least 30% without brute force actions, compared to the preceding 24 hours
Shutdown of greater than or equal to 30% of network processing nodes without brute force actions, but does not shut down the network
Out of scope
- Any affected code, from dependant Solana client implementations (eg. Agave or Firedancer) should be reported upstream.
- Example code (https://github.com/jito-foundation/jito-programs/tree/master/example-programs)
- any findings should be exploitable without being a trusted third party, findings involving a trusted third party for example BAM node may be considered on a discretionary basis since these would be more defense in depth controls rather than a direct exploit path
- any findings which assume misconfiguration, for example a deployment of a program gone wrong or a validator misconfigured are not in scope
- any findings which can only be demonstrated using unit tests only are out of scope. The attack must be a possible attack vector under realistic network/deployment conditions to be considered. A unit test can be used to demonistrat and can be a sufficient POC if it meets this criteria but can not be the sole determining factor.
Blockchain/DLT 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