-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Update EVM to use new Generalized WT #17216
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
I see you updated files related to
|
9e3e596 to
33dfa69
Compare
bd403eb to
b79c831
Compare
cce3d86 to
e7cb471
Compare
0d5431c to
6c8cc15
Compare
3c6447a to
e06a6f9
Compare
|
|
||
| type Config struct { | ||
| // Address of the contract that will get the forwarded report | ||
| Address string |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a reason to leave this as config and not move to input? At least two user requests have a use case to dynamically set the address.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not aware of a reason why this couldn't be an input, but I think this discussion is out of scope for this PR and should be a followup
|




This PR includes the previous EVM WT Extraction that was reverted from
developas well as new changes to inject chain-specific code into the Generalized WT, along with expanded tests.Requires
Supports