Skip to content
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

VM read-only mode check: operation.writes not op.isMutating() #798

Merged
merged 1 commit into from
Aug 12, 2019

Conversation

libby
Copy link
Contributor

@libby libby commented Aug 9, 2019

op.isMutating() was added for checking mutating VM operation, but operation.writes
should be used now as it registers all mutating ops and is consistent with upstream.
Additionally there is a new op code added CREATE2 that is mutating, but has not been added to the op.isMutating() set. The VM is in read-only mode when a private contract calls a public contract.

`op.isMutating()` was added for checking mutating VM operation, but `operation.writes`
should be used now as it registers all mutating ops and is consistent with upstream.
Additionally, there is a new  mutating opcode `CREATE2`, but `CREATE2` has not been added to the
`op.isMutating()` set. The VM is in read-only mode when a private contract calls a public contract.
@libby libby requested review from vsmk98, trung and jpmsam August 9, 2019 18:56
@libby libby merged commit 7e87e40 into Consensys:master Aug 12, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants