Remove inactive Hashscan self-hosted instance#73
Merged
Conversation
The Hashscan server (server-verify.hashscan.io) now redirects to the public sourcify.dev/server instance and no longer runs its own self-hosted Sourcify server. Remove the entry and its unused logo. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
✅ Deploy Preview for sourcify-dev ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
manuelwedler
approved these changes
Jun 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Removes the Hashscan entry from the self-hosted instances list on the landing page.
I checked all six self-hosted instances against their Sourcify
/healthand/chainsendpoints. Hashscan was the only inactive one:https://server-verify.hashscan.io/healthreturns a 308 redirect to the publicsourcify.dev/serverinstanceCannot GET /This indicates Hashscan has decommissioned their self-hosted server and now points at the public instance.
The other five instances (Ronin Chain, MonVision, VeChainStats, Reactive Network, Walnut) are all live and were kept. Walnut's
/chainsis auth-gated but its health endpoint responds normally.Changes
src/data/selfHostedInstances.jsonpublic/hashscan.webplogo🤖 Generated with Claude Code