Skip to content

Remove blocksScanApi creation-tx fetcher - #2948

Open
kuzdogan wants to merge 1 commit into
stagingfrom
chore/remove-blocksscan-api
Open

Remove blocksScanApi creation-tx fetcher#2948
kuzdogan wants to merge 1 commit into
stagingfrom
chore/remove-blocksscan-api

Conversation

@kuzdogan

Copy link
Copy Markdown
Member

Summary

  • Remove the blocksScanApi option from FetchContractCreationTxMethods in lib-sourcify and the matching fetcher / branch in the server's getCreatorTx.

Why

The only chain that used blocksScanApi was XDC Apothem Testnet (51), pointing at https://apothem.xdcscan.io/. That endpoint is down (HTTP 521). The chain is auto-discovered by dRPC and Etherscan, and the Etherscan v2 API already returns its creation tx, so the manual override is being removed from sourcifyeth/sourcify-chains (companion PR linked in the comments) and this code path has no users left.

Notes

  • blocksScanApi is dropped from the lib-sourcify type, so a self-hosted sourcify-chains.json that still sets it will fail type-checking. Minor breaking change for lib-sourcify.

🤖 Generated with Claude Code

The only chain that used it was XDC Apothem (51), whose BlocksScan
instance at https://apothem.xdcscan.io/ is down (HTTP 521). The chain is
discovered by dRPC and Etherscan and Etherscan v2 returns its creation
tx, so the manual override is being removed from sourcify-chains and the
server no longer needs this code path.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@marcocastignoli

Copy link
Copy Markdown
Member

can we merge this after #2947 ?

@kuzdogan

Copy link
Copy Markdown
Member Author

Companion PR that removes the chain 51 override from the chain config: sourcifyeth/sourcify-chains#129

Posted with Claude Code

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

Labels

None yet

Projects

Status: Triage

Development

Successfully merging this pull request may close these issues.

2 participants