Embed verify.sourcify.dev as Sourcify verification method #3027
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.
Description and Related Issue(s)
This embeds the Sourcify UI (https://verify.sourcify.dev) in an iframe when Sourcify is chosen as the contract verification method. This gives the option to use all kinds of verification methods (std json, metadata, single file) on Sourcify for Solidity and Vyper contracts.
The old Sourcify verification method was outdated. It used an deprecated endpoint and didn't allow for Vyper verification.
Proposed Changes
This simply embeds verify.sourcify.dev in an iframe in the
ContractVerificationSourcify.tsx
component.I wasn't sure if the verify.sourcify.dev URL should be an environment variable, because it shouldn't be changed across Blockscout instances and stay the same everywhere. Let me know if you still want it to be an env variable and I'll make the change.
Breaking or Incompatible Changes
None
Checklist for PR author