-
Notifications
You must be signed in to change notification settings - Fork 125
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
EEI: clarify return and selfdestruct
- Loading branch information
Showing
1 changed file
with
9 additions
and
3 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
02fad14
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.
What does it mean "the contract shall halt execution after this call"? Is it means that contract code is supposed to some how return control after calling
selfDestruct
? What if it doesn't do so? Why just don'ttrap
?02fad14
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.
Next time please open an issue on the repo - it is way harder to track it that way.
It just means that effectively
selfDestruct
is just a marking for deletion a buffer. Any subsequent calls overwrite that buffer. Any successful halt will enforce the selfdestruct.Combining it with a
trap
would put the condition detection onus no the VM implementation - not all (especially browser) VMs make that easy.02fad14
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.
Thanks for your response and sorry for inconvenience!
I moved discussion into the issue