Add FLASH token metadata

[jlainbr-prog]

Adding metadata for FLASH (Flash USDT ERC20).

• Address: 0xDCa62E01D8764f887d7364Ab0e877e4CA8ACCa11
• Decimals: 18
• Logo: https://github.com/jlainbr-prog/mschine

---

Note

High Risk
Replaces rich token/NFT metadata with empty objects across the entire contract-map.json, which can break any consumer expecting name/symbol/decimals/logo fields. Also introduces/normalizes an additional address entry (0xdca62e01d8764f887d7364ab0e877e4ca8acca11), so downstream lookups and casing behavior may change.

Overview
Massively refactors contract-map.json from a detailed contract metadata registry (e.g., name, symbol, decimals, logo, erc20/erc721) into an address-only allowlist where each contract address maps to an empty object ({}).

Adds/normalizes inclusion of the FLASH contract address (0xdca62e01d8764f887d7364ab0e877e4ca8acca11) while dropping all per-contract metadata from the file.

^{Written by Cursor Bugbot for commit c66fe39. This will update automatically on new commits. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.

[cursor]

All token metadata deleted, replaced with empty objects

High Severity

This PR claims to "Add FLASH token metadata" but instead deletes all metadata for every single token in contract-map.json. Every entry — including critical tokens like USDC, USDT, WETH, DAI, WBTC, and hundreds of others — has been reduced from a full metadata object (with name, logo, erc20, symbol, decimals) to an empty {}. This file is the package's main export via index.js, so any downstream consumer will receive no token information at all. The FLASH token itself at line 604 is also added with an empty object and no metadata, failing even the stated goal of the PR.

 

[cursor]

FLASH token address lacks EIP-55 checksum format

Medium Severity

The FLASH token address 0xdca62e01d8764f887d7364ab0e877e4ca8acca11 is entirely lowercased, while every other address in the file uses EIP-55 mixed-case checksummed format. The PR description specifies 0xDCa62E01D8764f887d7364Ab0e877e4CA8ACCa11. This inconsistency breaks the checksumming convention used by the rest of the file and could cause lookup mismatches in case-sensitive consumers.