-
Notifications
You must be signed in to change notification settings - Fork 143
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
EVMOR
is rewritten to |Int
#291
Comments
|Int appears due to this rule:
You have 2 solutions (from the top of my mind, there might be more):
Note that split must be added at semantics level, not as trusted spec rule, because spec rules work differently (see kprove tutorial).
|
We are using the latest commit at We should move to these? |
@nrryuya No I don't recommend using KEVM-imap, it is very much work in progress. If you use KEVM-gnosis, then you can USE |
In your case you can try |
@denis-bogdanas |
I tried to verify a spec of a simple code in written in Vyper(0.1.0b4) and it fails with
Halt! Terminating branch.
.full spec (gist)
In the final step, the
<output>
cell reaches to this.full log of the final step (gist)
My first question is why
_|Int__INT(A_1367:Int,, B_1368:Int)
is there because in the evm.md, it says:i.e. using
|Word
not |Int` .I found
EVMOR
is rewritten to|Int
around STEP 941 (gist).The second question is how to prove the spec correctly. The precondition in eDSL is
andBool (A ==Int 1 orBool B ==Int 1)
and it's translated to this in the conjunctive formula:and it doesn't go well with
_|Int__INT(A_1367:Int,, B_1368:Int)
.I tried with
andBool (A |Int B) ==Int 1
, which is translated to_==K_(_|Int__INT(A_1385:Int,, B_1386:Int),, Int(#"1"))
but it also failed (==K
should be==Int
here?).Can we prove the spec if we add SMTLib translation for
|Int
?The text was updated successfully, but these errors were encountered: