-
Notifications
You must be signed in to change notification settings - Fork 124
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
Do not transfer ETH with selfDestruct #98
Comments
@axic and I had a similar discussion about this yesterday (adding a seperate EEI method |
I'm aware of the cons of such transfer(). But you can emulate it in EVM1 by creating a temporary contract and selfdestructing it. Such ether transfer is unnoticed by the targeted contract. My questions is, can you implement fully compliant EVM1 SELFDESTRUCT having the EEI functions as described above? |
I think so. I'm still working on the K spec for the EEI, and my focus is on conforming to the type signatures that eth_interface specifies, while using the EEI functionality directly with KEVM (so moving the logic out of KEVM that is needed into KEEI). If the KEVM tests pass with the KEEI, then we know it's possible. |
Advantages of having an executable spec :P |
Changes proposed in #113. |
In EVM1 the SELFDESTRUCT is messy and complex due to the additional ETH transfer coupled with it.
The text was updated successfully, but these errors were encountered: