feat: added commitments in block header #346
Merged
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
kkovaacs
approved these changes
Nov 17, 2025
eitanm-starkware
changed the base branch from
master
to
release/v0.10.0-rc.1
eitanm-starkware
merged commit f261bb6
into
starkware-libs:release/v0.10.0-rc.1
2 checks passed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Changes
Added commitments to the block header (for confirmed blocks), which affects the following methods:
starknet_getBlockWithTxHashesstarknet_getBlockWithTxsstarknet_getBlockWithReceiptsIncluding commitments allows clients to compute the block hash themselves without performing the most expensive commitment calculations.
Checklist:
npm run validate_allnpm run format