Unable to verify Raffle contract on goerli etherscan

[Roee-87]

I am able to deploy the contract to the goerli testnet, but I am unable to verify the contract when executing:

hh deploy --network goerli

I attempted to manually input the constructor parametrs using:

hh verify --network goerli <constructor args>

but this approach also failed. I'm not sure what's impeding the ability to verify.
I thought it might be an issue with indexing the contract on goerli, so I added a time delay in the deploy code, but this also failed to resolve the issue.

Github link to 01-deploy, Raffle.sol, verify.js, hardhat.config, helper-hardhat-config, and the deployments output file:

https://github.com/Robbe98/Raffle_2

[RoboCrypter]

@Robbe98 : You are not correctly verifying (manually) I will make a PR in your repo for your help to verify manually!

[Roee-87]

Sorry, I forgot to place code demarcation around the relevant section and it didn't show the (constructor args). Console line commands work, I just receive the same error (failed to verify).

[RoboCrypter]

@Robbe98 : I have made PRs in your repo, You can merge them!

In your helper-hardhat-config.js your were using incorrect gasLane and also incorrect vrfCoordinatorV2 address.

You were using rinkeby ones, But they will not work on goerli they are different!

I have corrected both of them, In my PR!

After merging my PRs run this command :

hh verify --network goerli --constructor-args arguments.js < DEPLOYED_CONTRACT_ADDRESS >

It will resolve your issue!

[RoboCrypter]

@Robbe98 : Let me know after that 👍

[RoboCrypter]

@Robbe98 : Oh boy!! , I have found the mistake, I have made a PR in your repo, You can merge it!

It was a problem in your 01-deploy-raffle.js file.

Problem was in your requires.

After that re deploy your contract on goerli and verify it by verify.js script.

It will resolve your issue!

[RoboCrypter]

@Robbe98 : I did not knew that you have a different repo in your setup and different one on github.

So, It did resolve by deploying to rinkeby and verify it as well!

Kindly mark the discussion as answered to close this as answered! ThankYou

Have a good one!

[Roee-87]

Unfortunately, the verification is still failing with the updated values (thank you for pointing out that error though).

Here is the first error I get:

NomicLabsHardhatPluginError: Failed to send contract verification request.
Endpoint URL: https://api-goerli.etherscan.io/api
Reason: The Etherscan API responded that the address 0x8413DFcE991bA6dC067dFBb6B31cAb1C80D44f12 does not have bytecode.
This can happen if the contract was recently deployed and this fact hasn't propagated to the backend yet.
Try waiting for a minute before verifying your contract. If you are invoking this from a script,
try to wait for five confirmations of your contract deployment transaction before running the verification subtask.

so then I run the manual verify from the command line using:

hh verify --network goerli 0x8413DFcE991bA6dC067dFBb6B31cAb1C80D44f12 0x2Ca8E0C643bDe4C2E08ab1fA0da3401AdAD7734D 998 0x79d3d8832d904592c0bf9818b621522c988bb8b0c05cdc3b15aea1b6e8db0c15 30 100000000000000000 50000

which gives me the following output:

Nothing to compile
Successfully submitted source code for contract
contracts/Raffle.sol:Raffle at 0x8413DFcE991bA6dC067dFBb6B31cAb1C80D44f12
for verification on the block explorer. Waiting for verification result...

We tried verifying your contract Raffle without including any unrelated one, but it failed.
Trying again with the full solc input used to compile and deploy it.
This means that unrelated contracts may be displayed on Etherscan...

Successfully submitted source code for contract
contracts/Raffle.sol:Raffle at 0x8413DFcE991bA6dC067dFBb6B31cAb1C80D44f12
for verification on the block explorer. Waiting for verification result...

Error in plugin @nomiclabs/hardhat-etherscan: The contract verification failed.
Reason: Fail - Unable to verify

[RoboCrypter]

@Robbe98 : Kindly follow my method: and merge my PRs and then pull them in your code and try exactly what I told above!

OR

Add arguments.js file in your directory just like my PR! and copy & paste :

module.exports = [
    "0x2Ca8E0C643bDe4C2E08ab1fA0da3401AdAD7734D",
    "998",
    "0x79d3d8832d904592c0bf9818b621522c988bb8b0c05cdc3b15aea1b6e8db0c15",
    "30",
    "10000000000000000",
    "500000",
]

Inside it!

then run the command I told above!

[RoboCrypter]

@Robbe98 : This one :

hh verify --network goerli --constructor-args arguments.js < DEPLOYED_CONTRACT_ADDRESS >

[Roee-87]

I am still running into the error:

Error in plugin @nomiclabs/hardhat-etherscan: The contract verification failed.
Reason: Fail - Unable to verify

even after using in the command line:

hh verify --network goerli --constructor-args arguments.js 0x8413DFcE991bA6dC067dFBb6B31cAb1C80D44f12

[RoboCrypter]

@Robbe98 : It verified your code by using the verify script as you can see.

Note: I did use rinkeby, because it was in my setup.

[Roee-87]

Could it be an issue with using the goerli testnet?

[RoboCrypter]

@Robbe98 : I don't think so, But my verify.js script is in my utils folder and 01-deploy-raffle.js script in my deploy folder,

you can try to do the same and if it is verifying successfully or not

[Roee-87]

Do you get a deployments folder containing a solcinputs folder which has a bunch of json files?

[RoboCrypter]

@Robbe98 Yes!

[krakxn]

Is your repo updated with all the changes? I will look into it; this is a common problem which can be fixed easily.

[Roee-87]

Yes. The verify.js is in a utils folder, otherwise everything is as it appears in my directory.

I browsed the q&a section and I saw that other similar errors stemmed from spelling errors. I've been victim of those before in an unrelated issue...but I don't think that's the case right now.

[Roee-87]

At this point, I can get the deployment, verification, and testing steps to execute successfully on Rinkeby but not on Goerli. The code is the exact same, except different chainIds, gasLane, and vrfcoordinatorv2 addresses for the goerli network.

Moving on at this point...will try to revisit this later next week.

[krakxn]

I have gone through everything, and made some changes. Besides them, the logic should be correct.

External factors such as a dependency collison (re-install w/ recommended versions to eliminate this possibility), silly errors such as the vrfCoordinatorV2Mock in the PR/incorrect data input seemingly are the only plausible explanations; consequently, you should check for them if possible.

Of course, do not waste much time if you understood the conceptual side of it, and also tried your best at debugging--if so, then you should continue forwards!

Good luck!

[Roee-87]

Beautiful and thank you!
https://goerli.etherscan.io/address/0xdf6df37a31104ccccb827081f934b9d32f9aee33#code

[RoboCrypter]

@Robbe98 : Oh boy!! , I have found the mistake, I have made a PR in your repo, You can merge it!

It was a problem in your 01-deploy-raffle.js file.

Problem was in your requires.

After that re deploy your contract on goerli and verify it by verify.js script.

It will resolve your issue!

And let me know if it resolved your issue!