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
Rewards
Rewards by Threat Level
Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2.3.
Reward Calculation for Critical Level Reports
For critical Blockchain/DLT bugs, the reward amount is 10% of the funds directly affected, capped at the maximum critical reward $100,000. However, a minimum reward of USD $50,000 is to be rewarded in order to incentivize security researchers against withholding on a bug report.
For critical Blockchain/DLT bugs with a non-funds-at risk impact, the reward will be paid out as follows:
- Network not being able to confirm new transactions (total network shutdown) - $100,000
- Unintended permanent chain split requiring hard fork (network partition requiring hard fork) - $100,000
- Permanent freezing of funds (fix requires hardfork) - $100,000
For critical Blockchain/DLT bugs, the reward is dependent on the ratio between the funds at risk, which includes all affected projects on top of the respective blockchain/DLT, and the market cap according to the average between CoinMarketCap.com and CoinGecko.com, calculated at the time the bug report is submitted.
Reward Calculation for High Level Reports
For high Blockchain/DLT non-funds-at risk impacts, the reward will be paid out as follows:
- Unintended chain split (network partition) - $50,000
- 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 - $50,000
Payouts are handled by the Jito Foundation directly and reward amounts are denominated in USD. However, payments are made in JTO on Solana.
The calculation of the net amount rewarded is based on the average price between CoinMarketCap.com and CoinGecko.com at the time the bug report was submitted. No adjustments are made based on liquidity availability.
Program Overview
For more information about the Jito - BAM Client, please visit https://bam.dev.
Any Bug Bounty relating to the BAM client will be provided in JTO, denominated in USD and pursuant to payment terms below.
For more details about the payment process, please view the Rewards by Threat Level section.
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.
The validator client supports traditional Solanar transactions as well as Jito Bundles on Solana. You can download the validator client here and pass a the closest BAM Node URL on the command line.
The BAM Validator operates in one of three distinct modes:
| Mode | Description | Scheduler | Bundle/Txn Source |
|---|---|---|---|
| Normal Agave | Standard Solana Validator | Internal Agave Scheduler | TPU Ingestion |
| Block Engine | Jito enhanced operation | Internal with Block Engine | Jito Block Engine & (Relayer TPU or TPU) |
| BAM | External scheduler Delegation | External BAM Scheduler | BAM Node via gRPC |
KYC Requirement
Jito - BAM Client will be requesting KYC information in order to pay for successful bug submissions. The following information will be required:
- Full name
- Date of birth
- Proof of address (either a redacted bank statement with address or a recent utility bill)
- Copy of Passport or other Government issued ID
- Likeness test to verify identity
Eligibility Criteria
Security researchers who wish to participate must adhere to the rules of engagement set forth in this program and cannot be:
- On OFAC's SDN list or the sanctions list of the United Kingdom or European Union or pursuant to sanctions imposed by the United Nations
- Official contributor, both past or present
- Employees and/or individuals closely associated with the project
- Security auditors that directly or indirectly participated in the audit review
Responsible Publication
Jito - BAM Client adheres to Category 3: Approval Required . This Policy determines what information researchers are allowed to make public from their submitted bug reports. For more information about the category selected, please refer to our Responsible Publication page.
Primacy of Impact vs Primacy of Rules
Jito - BAM Client adheres to the Primacy of Rules, which means that the whole bug bounty program is run strictly under the terms and conditions stated within this page.
Audits
KYC required
The submission of KYC information is a requirement for payout processing.
Additional information: Employees and/or individuals closely associated with the members of other Solana client teams are also not eligible to participate in this bug bounty program
Proof of Concept
Proof of concept is always required for all severities.
Responsible Publication
Category 3: Approval Required
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
- Any other actions prohibited by the Immunefi Rules
Feasibility Limitations
The project may be receiving reports that are valid (the bug and attack vector are real) and cite assets and impacts that are in scope, but there may be obstacles or barriers to executing the attack in the real world. In other words, there is a question about how feasible the attack really is. Conversely, there may also be mitigation measures that projects can take to prevent the impact of the bug, which are not feasible or would require unconventional action and hence, should not be used as reasons for downgrading a bug's severity.
Therefore, Immunefi has developed a set of feasibility limitation standards which by default states what security researchers, as well as projects, can or cannot cite when reviewing a bug report.