MetaMask / MetaMask/metamask-extension

[Bug]: ZKSync Asset Link Broken

Open
#27,476 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

regression-prod-12.2.4 team-assets
Dominant language
TypeScript
Stars
13.2k
Forks
5.6k
Avg merge
2d 5h
Merged PRs (30d)
451

Description

Describe the bug

When on the ZKSync network, using the default block explorer when enabling the network, the "View asset in explorer" link takes users to an "Oops, we can't find anything" page. This is because the link goes to https://explorer.zksync.io/token/[address] (example) but the correct link for that block explorer is https://explorer.zksync.io/address/[address] (example)

Expected behavior

Be taken to a page on the blockexplorer with the token info.

Screenshots/Recordings

https://github.com/user-attachments/assets/7973e909-30d6-48b4-812f-7af46b9a14c2

Steps to reproduce
  1. Add ZKSync by selecting it from the default list in the "Add Network" panel
  2. Add or import an ERC-20 token
  3. Click on the token in your asset list
  4. Click on "View Asset in Explorer" in the "3 dots" menu on the asset detail screen
  5. Notice that you are taken to a no-op page
Error messages or log output

No response

Detection stage

In production (default)

Version

12.2.4

Build type

None

Browser

Chrome

Operating system

MacOS

Hardware wallet

No response

Additional context

No response

Severity

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Search the ZKSync network configuration and the asset detail screen’s “View Asset in Explorer” action to find where the explorer URL is assembled. Reproduce the steps with an ERC-20 token and verify that the link uses the explorer’s /address/[address] path and opens the token information page.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.