page crash when hover on auto-verified ens address

[iampkuhz]

Description

When I move cursor on Address ENS name, the page crashed. It happened only when the to address is verified automatically in contract page. If the page is not verifed and only show orignal 0x*** format address, the hover won't cause this bug. However, this always happened after auto verified, no matter which page. transaction list page, contract list page, both of them would have such bug.

at the very begining, we're using v1.33.0. After upgrade to v1.33.2, this problem still occured.

hover here will cause 500 error. noted that we haven't have a chance to click it.

there is a exception in console:

TypeError: Cannot read properties of undefined (reading 'length')
    at HashStringShortenDynamic.tsx:94:28
    at ak (react-dom.production.min.js:167:135)
    at up (react-dom.production.min.js:197:256)
    at uc (react-dom.production.min.js:195:197)
    at us (react-dom.production.min.js:194:50)
    at i (react-dom.production.min.js:297:9)
    at oD (react-dom.production.min.js:280:383)
    at react-dom.production.min.js:280:319
    at oO (react-dom.production.min.js:280:319)
    at oE (react-dom.production.min.js:271:86)

Link to the page

local deployed network

Steps to reproduce

1. Go to main page
2. Click on a random txn which to address is a contract
3. switch to contract tab in contract page and try to trigger sc verifier service to auto verify this contract
4. go back to main page and this time the to address will be replaced by ERC1967Proxy ENS
5. hover on ERC1967Proxy and the crash happened

App version

v1.33.2

Browser

No response

Operating system

macOS

Additional information

No response

[yvaskov]

@iampkuhz could you provide a backend version as well, please?

[iampkuhz]

@yvaskov Backend: v6.6.0-beta

[yvaskov]

@iampkuhz this version is missing some of the proxy implementation preloads. I suggest upgrading to the latest version, as it has been fixed.

[iampkuhz]

@yvaskov change the front-end to the latest version but the problem still occurred

[yvaskov]

@iampkuhz I meant the backend version

[github-actions]

This issue is stale because it has been open for 14 days with no activity.

[iampkuhz]

after upgraded the backend version, this bug was fixed.