This repository has been archived by the owner on Feb 26, 2024. It is now read-only.
Reject SolidityAST contracts verified on Etherscan #6082
Merged
Conversation
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
As of Solidity 0.8.20, it's now possible to use the Solidity compiler in a mode where, instead of passing
language: "Solidity"orlanguage: "Yul", you passlanguage: "SolidityAST", and put in the AST of what you want compiled (it's the long-awaited companion to the stop-after-parsing option).I got worried about the possibility that Etherscan might allow verifying input in this form. I haven't actually yet tested whether it does, I intend to test that later. But I thought it would be good to put in a bit of defensive coding against that possibility right now, since there's no way we can reasonably handle it (at least, not quickly right now).