Jito
The Jito Foundation
Maximum Bounty
$250,000Live Since
28 August 2024Last Updated
04 September 2024PoC 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.
Critical
Network not being able to confirm new transactions (total network shutdown)
Critical
Unintended permanent chain split requiring hard fork (network partition requiring hard fork)
Critical
Direct loss of funds
Critical
Permanent freezing of funds (fix requires hardfork)
Critical
Permanent freezing of funds
Critical
Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield
High
Unintended chain split (network partition)
High
Temporary freezing of network transactions by delaying one block by 500% or more of the average block time of the preceding 24 hours beyond standard difficulty adjustments
High
Theft of protocol revenue
Medium
Causing network processing nodes to process transactions from the mempool beyond set parameters
Medium
Increasing network processing node resource consumption by at least 30% without brute force actions, compared to the preceding 24 hours
Medium
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
Program's Out of Scope information
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
- Impacts requiring phishing or other social engineering attacks against project's employees and/or customers.
- 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
- Any affected code, from dependant Solana client implementations (eg. Agave) should be reported upstream.
Blockchain/DLT & 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
- Example code (https://github.com/jito-foundation/jito-programs/tree/master/example-programs)
Websites and Apps
All websites and apps
Prohibited Activities:
- Any testing on mainnet or public testnet deployed code; all testing should be done on local-forks of either public testnet or mainnet
- 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 that are executed against project assets
- Automated testing of services that generates significant amounts of traffic
- Public disclosure of an unpatched vulnerability in an embargoed bounty