plans for migrating to etherscan v2 API #569
Closed
technophile-04
started this conversation in
General
Replies: 2 comments 1 reply
-
|
hey, yes I think I should be able to easily support v2 api. I already implemented it for hardhat-deploy v2 (which supports hardhat v3) and the code is mostly the same. will do soon. Thanks for creating this issue |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
available in v1.0.4 let me know if there are any issues |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Description:
At Scaffold-eth 2, we recommend that developers verify via
etherscan-verifyas the first option. We still use hardaht v2 since v3 is in alpha.Etherscan has already started deprecating the v1 API from May 31 and suggests to V2 API which supports multichain with the same API interface. https://docs.etherscan.io/etherscan-v2
It would be really nice if hardhat-deploy v1 starts supporting the v2 API apart from deprecation it also has nice DX so that users don't need to have different etherscan API key for each network and if it's handled by hardhat-deploy internally, currently we suggest developer to do it this way:
https://github.com/scaffold-eth/scaffold-eth-2/blob/9ef99cf12e83ac4db7ab71b496c38adbdedced18/packages/hardhat/hardhat.config.ts#L20-L22
Would love to know if there is plan to support etherscan v2 in hardhat-deploy v1 🙌
Thanks for building and maintaining this amazing tool!!
Beta Was this translation helpful? Give feedback.
All reactions