matter-labs / matter-labs/block-explorer

ETH not in tokens page for CBT

Open
#403 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
TypeScript
Stars
139
Forks
145
Avg merge
8h 3m
Merged PRs (30d)
3

Description

### 🐛 Bug Report

#### 📝 Description

When setting up price fetching in block explorer for Custom Base Token (CBT) chains, ETH does not show up on the token's page (example [Sophon](https://explorer.sophon.xyz/tokens)). ETH is bridged for CBT chains, which should be picked up by price fetching as it has an L1 address and liquidity on CoinGecko.

#### 🔄 Reproduction Steps

Enable off-chain data via CoinGecko API for explorer on a CBT ZK Chain.
Visit the explorer tokens page and see that Ether does not show up

#### 🤔 Expected Behavior

Ether should be listed as a bridged token, showing the price, L2 token address, and L1 token address

![Image](https://github.com/user-attachments/assets/9d83b04f-1f68-4810-9075-ad8e25e8db5b)

#### 😯 Current Behavior

Ether is not visible on the explorer tokens page

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

Start at the explorer tokens page and trace the CoinGecko API off-chain data path for a Custom Base Token (CBT) ZK Chain, reproducing the missing Ether entry. Compare the bridged-token data with the expected L1/L2 addresses and price; done means Ether appears with its price, L2 token address, and L1 token address.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
blockchain, frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.