Jito - BAM Client
The BAM Client extends the Jito-Solana client to interface with external schedulers (BAM Nodes) that run inside Trusted Execution Environments (TEEs) via gRPC, receiving pre-sequenced transaction bundles and executing them in FIFO order with respect to account locks. This design maintains network security while enabling sophisticated transaction ordering strategies.
PoC Required
KYC required
Arbitration enabled
Select the category you'd like to explore
Assets in Scope
Impacts in Scope
Network not being able to confirm new transactions (total network shutdown)
Unintended permanent chain split requiring hard fork (network partition requiring hard fork)
Direct loss of funds
Permanent freezing of funds (fix requires hardfork)
Unintended chain split (network partition)
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
Causing network processing nodes to process transactions from the mempool beyond set parameters
RPC API crash affecting programs with greater than or equal to 25% of the market capitalization on top of the respective layer
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
A bug in the respective layer 0/1/2 network code that results in unintended smart contract behavior with no concrete funds at direct risk
Shutdown of greater than 10% or equal to but less than 30% of network processing nodes without brute force actions, but does not shut down the network
Out of scope
Bounties apply only to vulnerabilities discovered in the listed repositories and code maintained by Jito Labs/Jito Foundation. This project is a fork of https://github.com/anza-xyz/agave; vulnerabilities that are present only in the upstream project and are not introduced or affected by the BAM Client fork are out of scope for rewards under this Bug Bounty Program. If a reported issue exists both in the BAM client fork and upstream, and we can verify it affects the BAM client, it may be eligible for bounty consideration. Please provide evidence that the issue is present in this repo (see “Proof of concept” requirements). Reports that describe issues that were already fixed upstream before the reporter submitted them to this repository are out of scope. If the issue existed upstream but you reported it to us before the upstream patch and it still affects the BAM Client fork, provide timestamps and evidence for consideration.
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