BAM writer service: Track BAM metrics #35
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
#### API - Added new endpoint bam_epoch_metrics - Returns bam metric info such as `bam_total_stake_weight`, `available_bam_delegation_stake`, `eligible_bam_validator_count` - Modified the endpoint `validators` to add new fields `jito_pool_eligible`, `jito_pool_directed_stake_target` #### Bam Writer Service - Service for BAM delegation calculations, tracking network-wide BAM validator participation and computing available JitoSOL delegation based on [JIP-28 specifications](https://forum.jito.network/t/jip-28-accelerate-bam-adoption/904).
ebatsell
reviewed
Nov 17, 2025
| │ Kobe API │ │ | ||
| │ (Data Access) │ ────────────────────────────────────────────────── | ||
| │ │ | ||
| └─────────────────┘ |
| /// Epoch number | ||
| epoch: u64, | ||
|
|
||
| /// Totoal JitoSOL TVL in lamports |
| allocation_bps: u64, | ||
|
|
||
| /// Available BAM delegation stake amount in lamports | ||
| available_bam_delegation_stake: u64, |
Collaborator
There was a problem hiding this comment.
can you update the comment to mention how this is the stake for JitoSOL delegation based on the current % of active stake running BAM
ebatsell
reviewed
Nov 18, 2025
api/src/main.rs
Outdated
| get(get_validator_histories), | ||
| ) | ||
| .route( | ||
| "/api/v1/bam_epoch_metric", |
Collaborator
There was a problem hiding this comment.
Everywhere in the PR that says "bam epoch metric" should be replaced with "bam epoch metrics"
ebatsell
reviewed
Nov 18, 2025
bam-writer-service/src/main.rs
Outdated
| args.epoch_progress_threshold, | ||
| poll_interval, | ||
| ) | ||
| .await |
Collaborator
There was a problem hiding this comment.
We can consider running this multiple times if we find that we need more redundancy or if validators are optimizing their BAM connectivity to be detected by this writer service
Collaborator
Author
There was a problem hiding this comment.
enabled to run multiple times like thresholds 50%, 75% 90% of epoch progress
bam-writer-service/src/lib.rs
Outdated
| } | ||
|
|
||
| self.bam_validators_store | ||
| .insert_many(&bam_validators) |
Collaborator
There was a problem hiding this comment.
Upsert is better practice here I think in the case that we run multiple times per epoch
Collaborator
Author
There was a problem hiding this comment.
make sense! switch to upsert method
aoikurokawa
commented
Nov 19, 2025
Comment on lines
+87
to
+128
| /// Retrieves the list of BAM (Block Auction Mechanism) validators based on the cluster configuration. | ||
| /// | ||
| /// # Behavior | ||
| /// | ||
| /// - **Localnet/Testnet**: Returns a static list of mock validators for testing purposes. | ||
| /// The mock data includes two validators with equal stake distribution (50% each). | ||
| /// | ||
| /// - **Mainnet**: Fetches the live validator list from the BAM API endpoint. | ||
| async fn get_bam_validators(&self) -> anyhow::Result<Vec<ValidatorsResponse>> { | ||
| match self.cluster { | ||
| Cluster::Localnet | Cluster::Testnet => { | ||
| let res = vec![ | ||
| ValidatorsResponse { | ||
| validator_pubkey: "FT9QgTVo375TgDAQusTgpsfXqTosCJLfrBpoVdcbnhtS" | ||
| .to_string(), | ||
| bam_node_connection: "testnet-bam-1".to_string(), | ||
| stake: 1500000.0, | ||
| stake_percentage: 0.50, | ||
| }, | ||
| ValidatorsResponse { | ||
| validator_pubkey: "141vSYKGRPNGieSrGJy8EeDVBcbjSr6aWkimNgrNZ6xN" | ||
| .to_string(), | ||
| bam_node_connection: "testnet-bam-1".to_string(), | ||
| stake: 1500000.0, | ||
| stake_percentage: 0.50, | ||
| }, | ||
| ]; | ||
|
|
||
| Ok(res) | ||
| } | ||
| Cluster::Mainnet => { | ||
| let bam_api_config = | ||
| bam_api_client::config::Config::custom(self.bam_api_base_url.clone()); | ||
| let bam_api_client = BamApiClient::new(bam_api_config); | ||
|
|
||
| bam_api_client | ||
| .get_validators() | ||
| .await | ||
| .map_err(|e| anyhow!("Failed to get bam validators: {e}")) | ||
| } | ||
| } | ||
| } |
Collaborator
Author
There was a problem hiding this comment.
Since the api for test is not ready, we will use fake values for testnet
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
API
bam_total_stake_weight,available_bam_delegation_stake,eligible_bam_validator_countvalidatorsto add new fieldsjito_pool_eligible,jito_pool_directed_stake_targetBam Writer Service
specifications.
Writer Service