docs: per-transaction changeset index on the flat archive - #364
Merged
Merged
Conversation
svlachakis
requested review from
LukaszRozmej,
benaadams,
kamilchodola and
stdevMac
September 21, 2026 09:43
LukaszRozmej
approved these changes
Sep 21, 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 the per-transaction changeset index added by NethermindEth/nethermind#13454 (which now also carries the parallel whole-block tracing from #13517).
fundamentals/archive-nodes.md: new section covering what the index speeds up (single-transaction traces, parallel whole-block traces, consecutive indexed blocks), how it is built (inline while syncing, at the tip, backwards via retrofit workers or the bulk fill), the fallback contract, the configuration table for the sevenFlatDb.HistoryTransactionIndex*options andJsonRpc.TraceModuleConcurrentInstances, and the contiguous-coverage caveat.interacting/json-rpc-server.md: the streaming section notes what changes for traces of indexed blocks.Defaults and numbers are left to the generated configuration reference, as on the rest of the page. Builds locally; the remaining broken-anchor warnings are the configuration anchors that appear with the next DocGen run, as before.