Hedera Sourcify search views have different behavior

[ed-marquez]

Description

The search tool from the following link does not work as expected: https://repository-verify.hashscan.io/select-contract/

See repro steps below for details.

Steps to reproduce

• Contract address: 0x00000000000000000000000000000000002e7a5d

• HashScan View (Partial Match ✅): https://hashscan.io/mainnet/contract/0.0.3045981

• Search result from this view: https://verify.hashscan.io/#/lookup

  

• Search result from this view: https://repository-verify.hashscan.io/select-contract/

  

For clarity, the verification results exist in Hedera Sourcify: https://repository-verify.hashscan.io/contracts/partial_match/295/0x00000000000000000000000000000000002E7A5D/

The search functionality from one of the views is what is broken.

Additional context

No response

Hedera network

mainnet, testnet

Version

Latest

Operating system

macOS

[Reccetech]

This lookup page doesn't work and should be deprecated: https://repository-verify.hashscan.io/select-contract/

All lookups should route to: https://verify.hashscan.io/#/lookup

[svienot]

The issue is:

• the lookup page (https://verify.hashscan.io/#/lookup) support both plain address and mixed-case checksum address (per ERC-55). If you enter 0x00000000000000000000000000000000002e7a5d it converts it into 0x00000000000000000000000000000000002E7A5D
• the select-contract form (https://repository-verify.hashscan.io/select-contract/) actually works but only supports the mixed-case checksum address, i.e. 0x00000000000000000000000000000000002E7A5D Hence the disconnect. (note the mixed-case checksum form just happens to be fully upper-case here, but most often, it is mixed-case)

This code is a dependency (furthermore an indirect one) of hedera-sourcify, and code that we currently do not control, so we need to investigate what is the best way to mitigate.