-
-
Notifications
You must be signed in to change notification settings - Fork 129
sourcify fails with 500 error code #197
Comments
Hmm. Since this issue only appears for Sourcify (with a status code 500), I'm tagging @marcocastignoli to see if he knows what might be the issue here. |
@d10r hey can you please try to verify the contracts directly using the UI? https://sourcify.dev/#/verifier |
I was able to verify the contract on our staging server: https://staging.sourcify.dev/#/lookup/0x1BD3b6522102F9ea406807f8ecaeB2D96278a83f but it fails on production. The staging works because we now make use of the |
thx @kuzdogan !
Would it be possible to provide some more info on what went wrong when something goes wrong? Is that currently a limitation of the sourcify API or of the plugin? |
I see the plugin does not provide the server response to the user and only |
thanks @kuzdogan |
Thanks I got the response without
|
Just published v0.6.3 which now does a better job at conveying these error messages. I reckon that Sourcify has also been updated since this issue was opened. If not, it will likely be updated soon. |
I just tried to verify a new set of contracts across 8 chains using v0.6.0 of the plugin.
All requests to etherscan-ish instances succeeded while all requests to sourcify failed.
This problem persists over days now.
Attached is the debug output for one of them.
sourcify_500.txt
The text was updated successfully, but these errors were encountered: