integrity: blk-range chk to pre-build "changed keys" index before calc state root#20302
Merged
AskAlexSharov merged 31 commits intorelease/3.4from Apr 3, 2026
Merged
integrity: blk-range chk to pre-build "changed keys" index before calc state root#20302AskAlexSharov merged 31 commits intorelease/3.4from
AskAlexSharov merged 31 commits intorelease/3.4from
Conversation
AskAlexSharov
requested review from
antonis19,
awskii and
taratorio
as code owners
sudeepdino008
approved these changes
Apr 3, 2026
AskAlexSharov
force-pushed
the
alex/blk_rng_idx_34
branch
from
ade35c7 to
8fe4247
Compare
sudeepdino008
pushed a commit
that referenced
this pull request
Apr 3, 2026
…c state root (#20302) 10_000x faster `check-commitment-hist-at-blk-range` in-mem index of "changed keys per each block" built once per 10K blocks Problem: each `HistoryKeyTxNumRange()` call it's full-scan of `.ef` file - and now it happening per-block. Solution: call it once per 10K blocks and process results into "blockNum -> changedKeys" idx
AskAlexSharov
added a commit
that referenced
this pull request
Apr 5, 2026
…c state root (#20302) 10_000x faster `check-commitment-hist-at-blk-range` in-mem index of "changed keys per each block" built once per 10K blocks Problem: each `HistoryKeyTxNumRange()` call it's full-scan of `.ef` file - and now it happening per-block. Solution: call it once per 10K blocks and process results into "blockNum -> changedKeys" idx
github-merge-queue Bot
pushed a commit
that referenced
this pull request
Apr 6, 2026
…x, xsync fix, warmuper fix, logs debug, unused code (#20337) Cherry-picks from release/3.4 to main: - integrity: blk-range chk to pre-build "changed keys" index before calc state root (#20302) - up gql and grpc (#20304) - stepSize: all tooling to use `tx.Debug().StepSize()` instead of `DefaultStepSize` constant (#20280) - db/state: fix CursorHeap tie-break to prefer RAM over DB over FILE (#20318) - xsync deprecated use fix (#20331) - warmuper.WaitAndClose: cancel work before wait (#20332) - logs: move some Info logs to Debug level (to simplify logs for Users) (#20329) - db: unused code remove (#20334) --------- Co-authored-by: moskud <sudeepdino008@gmail.com> Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
10_000x faster
check-commitment-hist-at-blk-rangein-mem index of "changed keys per each block" built once per 10K blocks
Problem: each
HistoryKeyTxNumRange()call it's full-scan of.effile - and now it happening per-block.Solution: call it once per 10K blocks and process results into "blockNum -> changedKeys" idx