Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 8 additions & 3 deletions contract-map.json
Original file line number Diff line number Diff line change
Expand Up @@ -307,7 +307,6 @@
"symbol": "NRG",
"decimals": 18
},

"0x0d88eD6E74bbFD96B831231638b66C05571e824F": {
"name": "Aventus",
"logo": "aventus.svg",
Expand Down Expand Up @@ -2071,7 +2070,6 @@
"symbol": "MLN",
"decimals": 18
},

"0xba358B6f5b4c0215650444B8C30D870B55050D2D": {
"name": "Hub Token",
"logo": "hub.svg",
Expand Down Expand Up @@ -4518,5 +4516,12 @@
"erc20": true,
"symbol": "FPS",
"decimals": 18
},
"0x992c30DD833E65586c6CEe32686dBE0cdCA077cc": {
"name": "JiuCaiBi",
"logo": "jcc.png",
"erc20": true,
"symbol": "JCC",
"decimals": 18
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

BEP-20 token incorrectly added to Ethereum mainnet registry

High Severity

The PR description states JCC is a BEP-20 token on BNB Smart Chain (chain 56), but it's added to contract-map.json, which is the Ethereum mainnet (chain 1) token registry. All other entries in this file are Ethereum ERC-20 tokens. BNB Smart Chain tokens belong in metadata/eip155:56/ as individual JSON files, following the CAIP-19 standard used throughout the repository. This will cause MetaMask to incorrectly present JCC as an Ethereum mainnet token.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 30321c0. Configure here.

}
}
}
Binary file added images/jcc.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.