feat: Add unsafe-pre-merge feature for pre-merge blocks
#183
Conversation
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
Wollac
changed the title
unsafe-pre-merge feature for pre-merge blocks
capossele
approved these changes
Aug 5, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR introduces an unsafe-pre-merge feature flag to allow proving pre-merge (Proof-of-Work) blocks.
By default, reth-stateless does not correctly validate all difficulty constraints for these blocks, making the proofs unsound. This feature disables the default post-merge block check, enabling users to generate proofs for historical blocks at their own risk.
The feature is propagated from the zeth-host crate down to the guest binary to ensure consistent validation logic between the host and zkVM.