Skip to content

Remove outdated Routescan explorer entry - #651

Open
leonschh wants to merge 1 commit into
inkonchain:mainfrom
leonschh:patch-4
Open

Remove outdated Routescan explorer entry#651
leonschh wants to merge 1 commit into
inkonchain:mainfrom
leonschh:patch-4

Conversation

@leonschh

Copy link
Copy Markdown

Summary

image
  • Ink is no longer listed among the supported networks.
  • Removed the outdated Routescan explorer entry from the documentation.

## Summary

* Checked Routescan's official list of supported chains.
* Ink is no longer listed among the supported networks.
* Removed the outdated Routescan explorer entry from the documentation.
@leonschh
leonschh requested a review from a team as a code owner August 25, 2026 13:18

@kutluhaneth46 kutluhaneth46 left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Review

Diff is clean: drops the Routescan section and leaves Blockscout / OKX / Tenderly intact.

One thing I’d like confirmed before merge (I’m not a maintainer — advisory only):

  1. Is Routescan intentionally unsupported for Ink now, or just the 57073.routescan.io / sepolia.inkonscan.xyz URLs gone stale?
  2. If only the URLs changed, updating the links may be preferable to removing the explorer entirely.

If maintainers have already decided to delist Routescan, this looks good as-is.

@leonschh

leonschh commented Sep 6, 2026

Copy link
Copy Markdown
Author

Review

Diff is clean: drops the Routescan section and leaves Blockscout / OKX / Tenderly intact.

One thing I’d like confirmed before merge (I’m not a maintainer — advisory only):

  1. Is Routescan intentionally unsupported for Ink now, or just the 57073.routescan.io / sepolia.inkonscan.xyz URLs gone stale?
  2. If only the URLs changed, updating the links may be preferable to removing the explorer entirely.

If maintainers have already decided to delist Routescan, this looks good as-is.

Thanks for your reply!

  1. I checked their documentation (see screenshot above), and the Ink network isn't listed there.
  2. I went to the website, clicked on “Transactions,” then clicked on the filters at the top to select the Ink network, and it isn't listed there either.
image

Based on this, I conclude that they no longer support the Ink network.

@kutluhaneth46 kutluhaneth46 left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Verified against Routescan supported-chains docs — Ink no longer listed. LGTM.

@leonschh

leonschh commented Sep 7, 2026

Copy link
Copy Markdown
Author

@kutluhaneth46 Could you please tell me how often the maintainer reviews PRs? Do you notify them, or do they review them on their own when they have time?

@kutluhaneth46

Copy link
Copy Markdown

I'm not an Ink maintainer — just a community reviewer — so I don't have a special notify path. From what I've seen, maintainers typically pick up PRs on their own schedule when they have bandwidth; tagging them repeatedly usually doesn't speed it up.

Your Routescan delist looks solid given their supported-chains list no longer includes Ink. I'd leave this as-is and wait for a maintainer pass. Thanks for the careful write-up!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants