Skip to content

Conversation

@zoowii
Copy link

@zoowii zoowii commented Dec 2, 2025

Add New Chain

Thanks for your pull request to add a new support in Sourcify.

If you haven't done so, please follow the instructions on how to request chain support in docs.

Please check the following items before submitting your pull request for a speedy review.

Checklist

  • The branch is named as add-chain-<chainId>.
  • I haven't modified the chains.json file directly.
  • In sourcify-chains.json file
    • I've set supported: true.
    • I haven't added an rpc field but the one in chains.json is used (if not, please explain why).
  • I've added a test in chain-tests.js file.
  • test-new-chain test in Circle CI is passing.

@kuzdogan
Copy link
Member

kuzdogan commented Dec 8, 2025

Hi I don't think the given explorer is an Etherscan instance. If it's a Blockscout instance you can add a blockscout field similar to other chains

@zoowii
Copy link
Author

zoowii commented Dec 8, 2025

Hi I don't think the given explorer is an Etherscan instance. If it's a Blockscout instance you can add a blockscout field similar to other chains

Yes, this is not an Etherscan block browser. We are planning to add Etherscan API-compatible contract verification APIs, such as the verify proxy contract API, to our block browser. Would this be okay? (Similar to https://docs.etherscan.io/api-reference/endpoint/verifyproxycontract)

@kuzdogan
Copy link
Member

kuzdogan commented Dec 8, 2025

@zoowii Yes that works but we don't use the verifyproxy endpoint

@zoowii
Copy link
Author

zoowii commented Dec 8, 2025

@zoowii Yes that works but we don't use the verifyproxy endpoint

sorry,I have typo error. we will implement the Verify Solidity Source Code rpc. is it enough?

@kuzdogan
Copy link
Member

the Verify Solidity Source Code rpc

wdym? We just need a standard chain rpc

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