Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

verification on etherscan doesn't work for holesky #5459

Closed
novaknole opened this issue Jun 29, 2024 · 2 comments
Closed

verification on etherscan doesn't work for holesky #5459

novaknole opened this issue Jun 29, 2024 · 2 comments
Assignees
Labels
status:needs-more-info There's not enough information to start working on this issue

Comments

@novaknole
Copy link

novaknole commented Jun 29, 2024

Version of Hardhat

2.22.3

What happened?

Hi.

I am trying to deploy on holesky testnet.

For the etherscan configuration via hardhat, I use the following:

{
        network: 'holesky',
        chainId: 17000,
        urls: {
          apiURL: 'https://api-holesky.etherscan.io/api',
          browserURL: 'https://holesky.etherscan.io',
        },
}

It turns out contracts get verified successfully except one contract which is deployed inside another contract via new keyword. Etherscan verification results in:

Reason: Fail - Unable to verify. Compiled contract deployment bytecode does NOT match the transaction deployment bytecode.

Does anyone know why ? Exact same thing successfuly gets verified on sepolia. I even tried using etherscan manually, but same thing.

@kanej
Copy link
Member

kanej commented Jul 8, 2024

Hey @novaknole, does the newed up contract take constructor arguments?

@kanej kanej added status:needs-more-info There's not enough information to start working on this issue and removed status:triaging labels Jul 8, 2024
@kanej
Copy link
Member

kanej commented Jul 22, 2024

I am closing as I suspect the issue is no longer relevant.

@kanej kanej closed this as completed Jul 22, 2024
@github-project-automation github-project-automation bot moved this from Backlog to Done in Hardhat Jul 22, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 21, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status:needs-more-info There's not enough information to start working on this issue
Projects
Archived in project
Development

No branches or pull requests

2 participants