Skip to content

Conversation

@akhi3030
Copy link
Contributor

@akhi3030 akhi3030 commented Jan 16, 2026

This is a proposal to address #486, on how we could use block ids in various places instead of block hashes with Alpenglow.

@akhi3030 akhi3030 requested a review from AshwinSekar January 16, 2026 15:23
@akhi3030
Copy link
Contributor Author

@AshwinSekar: did you have something like this in mind for addressing #486?

.unwrap()
.get(new_root)
.expect("Root bank doesn't exist");
root_bank.register_recent_blockhash(block_id, &BankWithScheduler::no_scheduler_available());
Copy link
Contributor

Choose a reason for hiding this comment

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

this is not the correct place to do it, we need to be registering the blockhash when we replay the end of the block.

This is currently done via register_tick. Alpenglow blocks still have one fake tick at the end so I think this is a good place to do it:

  • If it's a TowerBFT block, use the tick's hash as the blockhash
  • If it's an Alpenglow block, we need register_tick to instead use the block_id.

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.

3 participants