You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On contract verification, blockscout differentiates source codes on partial and full matches. In case of partially verified
contracts re-verification of such contracts is allowed. But it is not possible to re-verify such contracts via Hardhat rn, as it always returns "The contract {contract_address} has already been verified on Etherscan."
Suggestion
We suggest to add a new flag on verify:verify subtask - --skip-is-verified-check. That should disable the if(isVerified) condition to prevent verification attempt.
Output (even though the contract has been verified only partially and can be re-verified):
The contract 0xcA30DBB0Cb79cef0194f6e212B49fa1EB7246b61 has already been verified on Etherscan.
https://eth-sepolia.blockscout.com/address/0xcA30DBB0Cb79cef0194f6e212B49fa1EB7246b61#code
Search terms
No response
The text was updated successfully, but these errors were encountered:
Description
On contract verification, blockscout differentiates source codes on partial and full matches. In case of partially verified
contracts re-verification of such contracts is allowed. But it is not possible to re-verify such contracts via Hardhat rn, as it always returns "The contract {contract_address} has already been verified on Etherscan."
Suggestion
We suggest to add a new flag on
verify:verify
subtask ---skip-is-verified-check
. That should disable theif(isVerified)
condition to prevent verification attempt.A kind of similar approach has been adopted by foundry - foundry-rs/foundry#6461.
I may try to create a PR with corresponding changes. Just would like to ensure that you are fine with suggested approach.
Minimal Reproducible Steps
Lock.sol
contract to have a contract namedModifiedMetadataHashLock
.npx hardhat verify 0xcA30DBB0Cb79cef0194f6e212B49fa1EB7246b61 --network sepolia 123
Search terms
No response
The text was updated successfully, but these errors were encountered: