docs: the log index does not cover derived receipts - #358
Merged
Conversation
benaadams
approved these changes
Sep 5, 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
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.
Documents how the log index and the receiptless archive variant interact, following a question from the team. Verified against the code rather than assumed:
RegeneratingReceiptFinderdecorates the RPC read path only.LogIndexBuilderreads receipts throughIReceiptStorage, so for a block whose receipt write was skipped it gets nothing and stops advancing at that height - it stalls rather than leaving a silent gap in the index.IndexedLogFinderfalls back to the bloom-scan path, which re-executes every candidate block, bloom false positives included.So
Receipt.DeriveFromStateandLogIndex.Enabledare not mutually exclusive by configuration, but the index is inert exactly where receipts are absent - worth stating so nobody enables both and expects fasteth_getLogs.Follow-up to #356.