-
Notifications
You must be signed in to change notification settings - Fork 103
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
Feature request: support Routescan-based explorers #89
Comments
@iJaack thanks for this proposal. One idea to implement it is simply to support providing etherscan like API URL (and secret?) as query parameter. This way many other explorers would work out of the box. This requires probably further research. |
Hi @krzkaczor thank you for the prompt response. We currently support all the Etherscan endpoints, so it should be pretty easy. Let me know if you need other input from us :) |
@krzkaczor specifically this ones: https://routescan.io/documentation/etherscan-compatibility/contracts We already support Snowtrace: https://snowtrace.deth.net/address/0x6e84a6216eA6dACC71eE8E6b0a5B7322EEbC0fDd But you'd need to enable support from your side for the other chains as well. We aim to support 100 EVM chains by end of 2024, and they'll all have this same explorer type. LMK |
@krzkaczor any feedback here? |
Routescan is a block explorer platform.
It currently hosts many Single and Ecosystem Explorers, of which fully supported are:
Routescan offers two types of APIs:
We'd like to request integration for Routescan and, specifically, for the explorers mentioned above.
I'm available for further questions.
The text was updated successfully, but these errors were encountered: