Add Blockscout explorer URLs for Humanity Protocol chains#2580
Conversation
Registers the Alchemy-hosted Blockscout instances for Humanity Protocol mainnet (6985385) and testnet (7080969) so contract ABIs can be fetched automatically (verified: /api/v2/smart-contracts returns verified ABIs on both). Based on v7.22.0 (the version pinned by safe-decoder-service). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
I have read the CLA Document and I hereby sign the CLA You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot. |
Please @stoneton, could you sign the CLA? Thanks |
What
Registers the Blockscout API endpoints for Humanity Protocol mainnet (chain
6985385) and Humanity Protocol testnet (chain7080969) inBlockscoutClient.NETWORK_WITH_URL.Why
The network enums and Safe deployment addresses for both chains are already present (added in v7.8), but no explorer client is registered, so contract metadata/ABI fetching is unavailable for these chains in downstream services (safe-transaction-service, safe-decoder-service).
Verification
Both explorers are Alchemy-hosted Blockscout instances; the v2 API returns verified contract ABIs:
https://humanity-mainnet.explorer.alchemy.com/api/v2/smart-contracts/0xD3f42c1DeBDCF75AB8204004b1CC9d7e7Ebf17Bd→UniswapV3Factory,is_verified: truehttps://humanity-testnet.explorer.alchemy.com/api/v2/smart-contracts/0x4e1DCf7AD4e460CfD30791CCC4F9c8a4f820ec67→SafeProxyFactory,is_verified: true🤖 Generated with Claude Code