MetaMask / MetaMask/metamask-extension
[Bug]: ZKSync Asset Link Broken
Nobody has claimed this yet.
- 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
- Add ZKSync by selecting it from the default list in the "Add Network" panel
- Add or import an ERC-20 token
- Click on the token in your asset list
- Click on "View Asset in Explorer" in the "3 dots" menu on the asset detail screen
- 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
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- 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