chore: Move proving inputs from DB to file#2068
Open
sergerad wants to merge 7 commits into
Open
Conversation
sergerad
added
the
no changelog
Mirko-von-Leipzig
approved these changes
May 13, 2026
Collaborator
Mirko-von-Leipzig
left a comment
Mirko-von-Leipzig
left a comment
There was a problem hiding this comment.
Some minor questions/nits but otherwise lgtm
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.
Closes #2014.
Summary
Moves block proving inputs out of the database and into the file-based block store, and decouples their persistence from the
apply_blockpipeline.Proving inputs storage
BlockProofRequest) are now written to the block store as files alongside blocks, rather than being stored in the database. This avoids holding large serialized blobs in SQLite and keeps proving inputs co-located with the block data they reference.Decoupling from
apply_blockState::apply_blockno longer acceptsproving_inputs: Option<BlockProofRequest>. Saving proving inputs is now the caller's responsibility, via the newState::save_proving_inputsmethod. Note that replicas apply blocks and do not store proving inputs.BlockProducerApi::apply_block, proving inputs are saved eagerly (before spawning the block-application task).