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

Error in plugin hardhat-ignition: Invalid API Key #5678 #6172

Open
samrathMobius opened this issue Jan 22, 2025 · 3 comments
Open

Error in plugin hardhat-ignition: Invalid API Key #5678 #6172

samrathMobius opened this issue Jan 22, 2025 · 3 comments
Assignees
Labels
status:needs-more-info There's not enough information to start working on this issue

Comments

@samrathMobius
Copy link

Version of Hardhat

2.22.18

What happened?

While verifying the contract, I consistently receive an 'Invalid API key' error.

Minimal reproduction steps

I am unable to find the solutions

Search terms

No response

@ChristopherDedominici
Copy link
Contributor

ChristopherDedominici commented Jan 27, 2025

Hi @samrathMobius, could you provide a code example (remember to omit your private key) of how you are passing the API key to Hardhat? Based on the information you’ve shared, it’s a bit difficult to determine what might not be working.
For reference, here’s the documentation on verifying a contract: https://hardhat.org/hardhat-runner/docs/guides/verifying

@ChristopherDedominici ChristopherDedominici added status:needs-more-info There's not enough information to start working on this issue and removed status:triaging labels Jan 27, 2025
@samrathMobius
Copy link
Author

samrathMobius commented Jan 29, 2025 via email

@ChristopherDedominici
Copy link
Contributor

Hi @samrathMobius, I don’t see any code sample in your message. Did you forget to include a link or post the code you used?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status:needs-more-info There's not enough information to start working on this issue
Projects
Status: Backlog
Development

No branches or pull requests

2 participants