Can not verify deployed contract

[piavgh]

Component

Forge

Have you ensured that all of these are up to date?

• Foundry
• Foundryup

What version of Foundry are you on?

forge 0.1.0 (2ff2b33 2022-03-06T00:10:54.403068+00:00)

What command(s) is the bug in?

forge verify-contract

Operating System

macOS (amd)

Describe the bug

The code of contract is here: https://github.com/piavgh/simple-ens-foundry

I deployed the contract using this command:

forge create --rpc-url https://eth-ropsten.alchemyapi.io/v2/<alchemy-key> --constructor-args "geek" --private-key <my-private-key> src/Domains.sol:Domains

Then I verified it with

forge verify-contract --chain-id 3 --num-of-optimizations 200 --constructor-args 0x000000000000000000000000000000000000000000000000000000000000002000000000000000000000000000000000000000000000000000000000000000046765656b00000000000000000000000000000000000000000000000000000000 --compiler-version v0.8.10+commit.fc410830 0x19f4cd4bc239b8c32f264bf13efbe31a0fc4194d src/Domains.sol:Domains <my-etherscan-api-key>

I tried with different values of --num-of-optimizations: 0, 200 (default), 1000000, and even skip this argument, but all of them give the same value when I tried the forge verify-check:

Error:
   0: Contract verification failed:
      Response: `NOTOK`
      Details: `Fail - Unable to verify`

Location:
   cli/src/cmd/verify.rs:126

Backtrace omitted.
Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.

[mattsse]

perhaps related to #811

[nnnnicholas]

I believe the root of the problem is the Etherscan API Key

An API request with Invalid API Key:
{"status":"0","message":"NOTOK","result":"Invalid API Key"}

source: https://info.etherscan.com/api-return-errors/

However I am having the same issue despite attempting to verify with multiple API Keys and via the Etherscan website, too.

The problem may have to do with using unversioned OpenZeppelin imports in the contract. See here https://forum.openzeppelin.com/t/how-to-verify-a-contract-on-etherscan-bscscan-polygonscan/14225#use-versioned-imports-in-remix-10

[piavgh]

I believe the root of the problem is the Etherscan API Key

An API request with Invalid API Key:
{"status":"0","message":"NOTOK","result":"Invalid API Key"}

source: https://info.etherscan.com/api-return-errors/

However I am having the same issue despite attempting to verify with multiple API Keys and via the Etherscan website, too.

The problem may have to do with using unversioned OpenZeppelin imports in the contract. See here https://forum.openzeppelin.com/t/how-to-verify-a-contract-on-etherscan-bscscan-polygonscan/14225#use-versioned-imports-in-remix-10

I don't think so. I use the same key but I was able to verify contract with hardhat

[adamxyzxyz]

hey guys, has this been resolved? having the exact same issue

[pyk]

It seems that this caused by the forge flatten is only stripping the license and solidity version but not the pragma

for example:

pragma solidity 0.8.11;
pragma experimental ABIEncoderV2;

pragma solidity 0.8.11; is removed but not the pragma experimental ABIEncoderV2;

[piavgh]

@pyk : I can verify a simple counter contract with the newest version of foundry.

But somehow with this contract, it's still failed: https://github.com/piavgh/simple-ens-foundry

• To get the constructor args:

cast abi-encode "constructor(string)" "geek"

0x000000000000000000000000000000000000000000000000000000000000002000000000000000000000000000000000000000000000000000000000000000046765656b00000000000000000000000000000000000000000000000000000000

• To deploy the contract:

forge create --rpc-url https://eth-ropsten.alchemyapi.io/v2/<my_alchemy_key> --constructor-args 0x000000000000000000000000000000000000000000000000000000000000002000000000000000000000000000000000000000000000000000000000000000046765656b00000000000000000000000000000000000000000000000000000000 --private-key <my_private_key> src/Domains.sol:Domains

• To verify the contract:

forge verify-contract --chain-id 3 --constructor-args 0x000000000000000000000000000000000000000000000000000000000000002000000000000000000000000000000000000000000000000000000000000000046765656b00000000000000000000000000000000000000000000000000000000 --compiler-version v0.8.10+commit.fc410830 0x50d496f74a36ff6c4397440b31d26c8108eae5b5 src/Domains.sol:Domains <my_etherscan_key>

• To verify check:

forge verify-check --chain-id 3 7janbc6hd9kicjdvvcj6fcacmnzpegijkytn5flhdxmgkivcv9 <my_etherscan_key>

The result is still:

Error:
   0: Contract verification failed:
      Response: `NOTOK`
      Details: `Fail - Unable to verify`

[wminshew]

haven't had any luck on the latest foundry master branch (includes #1242) as well with the below setup. Not entirely sure if I should be opening up a new issue or tagging on to this one

repo https://github.com/0xSplits/splits-vesting; commands:
make contract=VestingModuleFactory deploy-ropsten (need ALCHEMY_ROPSTEN_KEYand PRIVATE_KEY set in .env.local)
then
make contract=VestingModuleFactory address={address} chain-id=3 verify

[sambacha]

haven't had any luck on the latest foundry master branch as well with the below setup. Not entirely sure if I should be opening up a new issue or tagging on to this one

repo https://github.com/0xSplits/splits-vesting; commands:

make contract=VestingModuleFactory deploy-ropsten (need ALCHEMY_ROPSTEN_KEYand PRIVATE_KEY set in .env.local)

then

make contract=VestingModuleFactory address={address} chain-id=3 verify

I forked this repo and was able to duplicate your issue. Have you tried adding extra output metadata to your build? I think etherscan needs the additional information in metadata for deployments that have multiple libraries etc

[wminshew]

I forked this repo and was able to duplicate your issue. Have you tried adding extra output metadata to your build? I think etherscan needs the additional information in metadata for deployments that have multiple libraries etc

hi -- would love to try this.. where can I learn more about how to do this?