Expose origin and the addresses of contracts being constructed in precompile handle #313
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
|
@sorpaas @boundless-forest @koushiro If you guys agree to merge these changes, I will add the follow-up changes to frontier. |
koushiro
approved these changes
May 3, 2025
This was referenced May 3, 2025
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.
Exposes the transaction origin in precompile handle, this can be used to identify if an address is an Externally Owner Account (EOA). (
tx.origin == msg.sender)This is necessary to distinguish addresses from contracts under-construction and real EOA's, since contracts under-construction only have code after the
init_codeis executed.Exposing the
originto precompiles will be required for supporting https://eips.ethereum.org/EIPS/eip-7702, since it adds the possibility for EOA to have code.