fix(fast-inbox): replay published blocks by message count - #25408
Open
spalladino wants to merge 1 commit into
Open
fix(fast-inbox): replay published blocks by message count#25408spalladino wants to merge 1 commit into
spalladino wants to merge 1 commit into
Conversation
This was referenced Sep 4, 2026
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
1 participant
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.
Context
The message-only Inbox rolling hash survives an L1 reorg that re-mines the same ordered leaves under different bucket boundaries. An already-published block remains valid in that case, but a fresh node could not replay it when an intermediate committed leaf count was no longer a boundary in the current Inbox partition.
Approach
Historical message retrieval now reads exact compact leaf-count ranges directly from the archiver's indexed message log, validates that each range is fully synced, and no longer resolves its bounds through current bucket metadata. World-state applies those ranges block by block without a silent empty fallback, and validator checkpoint reconstruction uses the same count-addressed semantics for its historical start while retaining the current-bucket requirement at the final endpoint.
The shared archiver mocks now keep indexed leaves separate from replaceable bucket metadata, enabling a fresh-world-state regression that replays published blocks after a same-message bucket merge. Live bucket-range selection and proposal validation remain unchanged.
Stacked on #25398
Fixes A-1924