chore(levm): avoid duplicate BackupHook in L2 stateless_execute #5249
+3
−1
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
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.
Motivation
Redundant BackupHook in L2 when using stateless_execute.
Description
This change prevents adding a second BackupHook during stateless_execute when running in L2 mode. L2 already installs BackupHook via its default hook set, so adding another caused redundant finalize_execution work and a second identical tx_backup write. Restricting the injection to VMType::L1 preserves stateless behavior for L1 while removing unnecessary duplication for L2, with no functional change to execution semantics.