Add JCC (JiuCaiBi) BEP-20 token

[simonkang123]

Adding JCC (JiuCaiBi) to MetaMask contract metadata.

Field	Value
Contract	0x992c30DD833E65586c6CEe32686dBE0cdCA077cc
Symbol	JCC
Decimals	18
Chain	BNB Smart Chain

---

Note

Low Risk
Low risk data-only change that adds a new token entry; main risk is incorrect contract metadata (address/symbol/decimals/logo) affecting display in wallets.

Overview
Adds MetaMask contract metadata for the JCC (JiuCaiBi) token at 0x992c30DD833E65586c6CEe32686dBE0cdCA077cc (name, symbol, decimals, and jcc.png logo reference) to contract-map.json.

Also cleans up minor JSON formatting artifacts and adjusts the file ending (newline/closing braces).

^{Reviewed by Cursor Bugbot for commit 30321c0. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Reviewed by Cursor Bugbot for commit 30321c0. Configure here.}

[cursor]

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.

 

^{Reviewed by Cursor Bugbot for commit 30321c0. Configure here.}