-
Notifications
You must be signed in to change notification settings - Fork 277
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
fix(trace): add more opcode handlings #128
Conversation
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.
LGTM. Just a little worry about the size of trace for contract code maybe large, and we may have recorded duplicated code in the block trace. Maybe it would be better to record all codes being accessed in "storageTrace" block or something similar? (It can be left as an optimization later)
gonna merge first and run sushi-test. will revert the changes for |
update: The sushi test (which involves |
according to https://github.com/scroll-tech/zkevm-circuits/blob/scroll-dev-0714/bus-mapping/src/circuit_input_builder/access.rs#L114
related PR: scroll-tech/scroll-prover#29
question
In fact I don't know why I have
traceCaller
forCALL
&CALLCODE
, but looks like we should usetraceContractAccount
?