Extend precompiled contract to execute subsequent EVM code call in context #106
Conversation
This file contains hidden or 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
|
Rust EVM 1.0 now fully supports precompile subsequent EVM code call without using any hacks like this. :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This extends precompiled contract to add a second kind. For this kind of precompiled contracts, it returns subsequent EVM codes (with inputs) that is executed within the same context as the precompile. This "subsequent EVM code" has the full ability as a normal EVM contract and can modify states it is allowed to modify (issue other calls, create contracts, or modify the storage of the precompile).
This allows us to support use cases such as #105 without exposing too much internal state, which, if messed up, can actually cause the EVM to panic (for example, accidentally make the call stack unbalanced).