-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Collision in address is "possible" as per hevm, even though it's not #549
Labels
Comments
Aliasing bug |
Yay this should be fixed with #641 Took me a looooooong time. But got there eventually.
Then:
Without the PR:
|
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Should hevm enforce freshness conditions on newly created symbolic addresses?
I am working with this example:
running
hevm symbolic --sig "B()" --code <the-creation-code>
returnsthe same happens with
--initial-storage Empty
.Removing the assertion results in
QED
.The text was updated successfully, but these errors were encountered: