bump max tracer history to support forced transactions#82
Merged
matkt merged 1 commit intoConsensys:mainfrom Apr 14, 2026
Merged
Conversation
Signed-off-by: garyschulte <garyschulte@gmail.com>
Merged
2 tasks
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.
PR Description
Tracer history is a concurrent queue that retains the most recent zk tracers and their corresponding hub state in order to filter bonsai accumulator when building trielogs.
Forced transactions will use this same mechanism to build trielogs, but not against the head worldstate. This PR bumps up the cache size from 3 to 5 to accomodate forced transaction proving.
Fixed Issue(s)
Documentation
doc-change-requiredlabel to this PR if updates are required.Changelog
Note
Low Risk
Low risk change that only increases the in-memory tracer FIFO from 3 to 5 entries; potential impact is slightly higher memory retention and different eviction timing.
Overview
Increases zk tracer retention depth. Bumps
ZkBlockImportTracerProvider.MAX_TRACER_HISTORY_SIZEfrom3to5, keeping more recent tracer/header tuples before FIFO eviction to support workflows (e.g., forced transactions) that need older tracers when building trielogs.Reviewed by Cursor Bugbot for commit b08119b. Bugbot is set up for automated code reviews on this repo. Configure here.