foundry: trouble verifying w blockscout (on arbitrum-goerli)
Component
Forge
Have you ensured that all of these are up to date?
- Foundry
- Foundryup
What version of Foundry are you on?
forge 0.2.0 (3a462eb 2022-09-22T03:37:08.364254Z)
What command(s) is the bug in?
forge verify-contract
Operating System
macOS (Intel)
Describe the bug
I am trying to verify two recently deployed contracts on arbitrum-goerli:
- https://goerli-rollup-explorer.arbitrum.io/address/0x0a2841630f198745a55C4dab3fE98f77271949E5
- https://goerli-rollup-explorer.arbitrum.io/address/0x652a2A2876B855d9c30d9265F882F0a486608976
from terminal (I also tried w /api appended to verifier-url w no luck):
$ forge verify-contract 0x0a2841630f198745a55C4dab3fE98f77271949E5 src/VestingModuleFactory.sol:VestingModuleFactory --chain-id 421613 --compiler-version v0.8.13+commit.abaa5c0e --num-of-optimizations 200 --verifier-url https://goerli-rollup.arbitrum.io --verifier blockscout
2022-09-23T20:57:42.762566Z ERROR etherscan: Failed to deserialize response: EOF while parsing a value at line 1 column 0 response=""
Submitting verification for [src/VestingModuleFactory.sol:VestingModuleFactory] "0x0a2841630f198745a55C4dab3fE98f77271949E5".
2022-09-23T20:57:48.035755Z ERROR etherscan: Failed to deserialize response: EOF while parsing a value at line 1 column 0 response=""
^C
I also tried manual verification thru the site but wasn’t sure how to manipulate the json in out/ to get it to succeed (it didn’t accept as is – i tried deleting keys it was complaining about going off the solidity docs to match solc input json but wasn’t able to solve it)
note: bug may be due to blockscout service being degraded or something – the explorer has been very funky the past couple of days (e.g. it isn’t even recognizing 0x652a2A2876B855d9c30d9265F882F0a486608976 as a contract)
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 15 (8 by maintainers)
closing this on account of me being an idiot
I was using the subdomain
goerli-rollupinstead ofgoerli-rollup-explorer. Should have known from the bizarre server error.Sorry for the hassle here