Is A New Instance of an Already Verified Smart Contract Considered Already Verified

Smart Contracts
1

While testing some deployment and verification scripts, we deployed a smart contract and verified it on testnet etherscan.

Then redeployed the smart contract again and tried to verify the new contract address on testnet etherscan.

The verification failed with Reason: Already Verified.

Is verification not related to every new contract instance address?

If anyone has knowledge on this, thank you for any insight!

2

Answered here. Etherscan currently does not let you verify it further because the bytecode matches with an existing contract. But you can still use the hardhat-upgrades verify task for completeness which would also help verify the implementation and link the proxy to the implementation ABI on Etherscan.

1 Like