We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
One of the contracts used during the SH attacks had the following payload:
3273d3e32594cedbc102d739142aa70d21f4caea56181415305773764d7849614e664f6646614161416153744c6255ff
Which is
[0] ORIGIN [21] PUSH20 0xd3e32594cedbc102d739142aa70d21f4caea5618 [22] EQ [23] ISZERO [24] ADDRESS [25] JUMPI [46] PUSH20 0x764d7849614e664f6646614161416153744c6255 [47] SUICIDE
Note the implicit PUSH from ADDRESS, which, if the check fails, becomes a JUMP-location (which obviously will fail).
PUSH
JUMP
Running that with evmdis produces the following:
2017/02/10 14:41:21 Entering block at 0 with stack height 0 panic: Error performing reaching analysis: 25: Could not determine jump location statically; source is 24 goroutine 1 [running]: main.main() /home/martin/go/src/github.com/Arachnid/evmdis/evmdis/main.go:23 +0x411
The text was updated successfully, but these errors were encountered:
Hm. We could work around it for this specific case, but it would be pretty trivial for them to pick another op that can't be statically verified.
Sorry, something went wrong.
No branches or pull requests
One of the contracts used during the SH attacks had the following payload:
Which is
Note the implicit
PUSH
from ADDRESS, which, if the check fails, becomes aJUMP
-location (which obviously will fail).Running that with evmdis produces the following:
The text was updated successfully, but these errors were encountered: