Skip to content

feat(bam): Add parent identity to LeaderState - #1652

Draft
0xEdgar wants to merge 1 commit into
masterfrom
feat/mev-12835-leader-state-bank-identity
Draft

feat(bam): Add parent identity to LeaderState#1652
0xEdgar wants to merge 1 commit into
masterfrom
feat/mev-12835-leader-state-bank-identity

Conversation

@0xEdgar

@0xEdgar 0xEdgar commented Sep 12, 2026

Copy link
Copy Markdown
Contributor

Populate the parent_slot, parent_block_id and atomic_batches_enabled
fields from jito-labs/bam-protos#18 so BAM can create its bank for the
slot before any shred arrives (MEV-12789, MEV-12835).

Populate the `parent_slot`, `parent_block_id` and `atomic_batches_enabled`
fields from jito-labs/bam-protos#18 so BAM can create its bank for the
slot before any shred arrives (MEV-12789, MEV-12835).

- read the working bank and its readiness from one `SharedLeaderState`
  snapshot so a same-slot replacement cannot mix them
- bump `jito-protos/bam-protos` to the #18 commit
@0xEdgar 0xEdgar changed the title feat(bam): Add bank identity to LeaderState feat(bam): Add parent identity to LeaderState Sep 12, 2026
Comment thread core/src/bam_manager.rs
@@ -342,6 +344,9 @@ impl BamManager {
slot: bank.slot(),
tick: (bank.tick_height() % bank.ticks_per_slot()) as u32,
slot_cu_budget_remaining,

@buffalu buffalu Sep 12, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do we need to add the current bank id here too? i need to read into AG more, but think we need to target the bank slot/bank id when were sending the atomic tx batches so that our speculative bank is built properly

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants