fix: verification endpoint alignment with etherscan #367
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
API E2E Test Results207 tests 202 ✅ 19s ⏱️ For more details on these failures, see this check. Results for commit e3f982f. |
Unit Test Results 4 files 264 suites 11m 37s ⏱️ Results for commit e3f982f. |
|
Visit the preview URL for this PR: |
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.
What ❔
Resolved incompatibilities with the explorer's verification API endpoint.
Why ❔
For contract verification through Foundry and Hardhat, the API endpoint should function in the same way as it works on Etherscan.
This PR resolves the issue:
#351
Checklist