-
Notifications
You must be signed in to change notification settings - Fork 153
Remove node build from semantics #786
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
|
Should be ready for re-review, I've tested locally, and the only thing I'm not convinced of is that the proofs will all pass. |
evm.md
Outdated
| rule #code?(EXTCODESIZE) => true | ||
| rule #code?(EXTCODECOPY) => true | ||
| rule #code?(OP) => false requires (OP =/=K EXTCODESIZE) andBool (OP =/=K EXTCODECOPY) | ||
| rule <k> #addr [ OP:OpCode ] => . ... </k> [owise] |
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.
pretty sure the java backend doesn't understand owise on non-function rules.
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.
@dwightguth I converted to an explicit side condition.
|
Looks fine. I wonder if we can make that side condition faster by converting it to structural matching, but we can worry about that later. |
The Node build is fully subsumed by the Web3 build now, so no need to keep it around, which should allow for some simplifications in the blockchain-k-plugin as well.