-
Notifications
You must be signed in to change notification settings - Fork 409
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Contract verification API doesn't work #1111
Comments
Hi thanks for the report. We had a server hiccup yesterday. Now I was able to verify: {
"result": [
{
"address": "0xC84A4835a95e1f7Caf968363DD3C0cC71265fB8C",
"chainId": "1313161554",
"status": "partial",
"libraryMap": {}
}
]
} Can you check again? |
It now works for me, thanks @kuzdogan! |
I'm still getting errors, not for all contracts but for some of them:
Result:
|
Uh oh, this is related to new scraping for the cliend-side rendered Blockscout instances #1092 I'll look into it thank you |
Since we are running puppeteer in the container, we are running it as root. This is not allowed without the --no-sandbox argument, hence #1111
@pustovalov This should be fixed now. Although with the given contract above the verification fails with |
@kuzdogan now it works, thx for the fix. That contract must be verified, perhaps additional settings should be passed to the compiler settings to prevent error. |
Closing this then. Feel free to reach out if you have trouble verifying |
Hi,
Endpoint:
https://sourcify.dev/server/verify/solc-json
Req:
Response:
also noticed that verification through etherscan also doesn't work:
but at the same time, etherscan API works:
If I run sourcify server locally, request to local API works fine:
View in Huly HI-433
The text was updated successfully, but these errors were encountered: