This repository has been archived by the owner on Oct 11, 2024. It is now read-only.
feat: Handler #27
Merged
feat: Handler #27
Conversation
This file contains 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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Introduce a handler that has a list of functions that are called from EVM.
This allows us to split additional requirements that differ from mainnet and be able to do it in a nice not intrusive way. Previously only way was to introduce a feature and a flag inside
CfgEnv.For now, it is partially done but it is good for optimism usecase (Will work on this later down the line).
I have split the
finalizationfunction and moved it inside the handler.This extends work from: #26