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.

Sign up for GitHub

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

Jump to bottom

Investigate failing Etherscan API tests #1835

Open
manuelwedler opened this issue Jan 7, 2025 · 1 comment
Open

Investigate failing Etherscan API tests #1835

manuelwedler opened this issue Jan 7, 2025 · 1 comment
Assignees
@manuelwedler

Comments

@manuelwedler
Copy link
Collaborator

Our etherscan instance tests are failing since last Friday. I think they might have changed something about their API. They sent an e-mail that you should move your instances API keys to main Etherscan.
@manuelwedler manuelwedler converted this from a draft issue Jan 7, 2025
@manuelwedler manuelwedler self-assigned this Jan 17, 2025
@manuelwedler manuelwedler moved this from Sprint - Up Next to Sprint - In Progress in Sourcify Public Jan 17, 2025
@manuelwedler
Copy link
Collaborator Author

Etherscan seems to have changed something about their instances. Some instances seem to not have required an API key, and for some of these we didn't set up a key in the CI or didn't configure them properly in the sourcify-chains-default.json.

Working on a fix.

@manuelwedler manuelwedler mentioned this issue Jan 17, 2025
Open
@manuelwedler manuelwedler moved this from Sprint - In Progress to Sprint - Needs Review in Sourcify Public Jan 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@manuelwedler manuelwedler

Labels
None yet
Projects
Sourcify Public
Status: Sprint - Needs Review
Milestone
No milestone
Development

No branches or pull requests
1 participant
@manuelwedler