Add FUSDT token metadata

[jlainbr-prog]

Adding metadata for FUSDT (Flash USDT ERC20).

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

---

Note

High Risk
High risk because it removes all token/NFT metadata (name, symbol, decimals, logo, erc20/erc721) from contract-map.json, which will likely break any code paths expecting that data for UI display or token handling.

Overview
Massively changes contract-map.json from a metadata registry to an address allowlist. The previous per-contract fields (e.g., name, symbol, decimals, logo, erc20/erc721) are removed and every address now maps to {}.

Adds the FUSDT contract address 0x419ecA43dB68E868E68d1aB460c8AC32523c7540 to the list, but without any associated metadata.

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

[cursor]

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

[cursor]

All token metadata stripped to empty objects

High Severity

Every token entry in contract-map.json has been replaced with {}, removing all name, logo, erc20, symbol, and decimals metadata for hundreds of existing tokens. This includes critical tokens like USDC, USDT, WETH, DAI, and many others. The file is consumed via index.js as the module's primary export, so any downstream consumer will receive empty objects for every token address. The existing test suite (accessing contract.logo.length) will also crash on undefined.

 

[cursor]

FUSDT address not EIP-55 checksummed, fails validation

High Severity

The new FUSDT entry uses an all-lowercase address 0x419eca43db68e868e68d1ab460c8ac32523c7540 instead of the EIP-55 checksummed form 0x419ecA43dB68E868E68d1aB460c8AC32523c7540. The test suite explicitly validates that all keys pass isValidChecksumAddress, so this entry will fail the existing checksum test. Every other address in the file uses mixed-case checksummed format.

 

[cursor]

New FUSDT entry contains no token metadata

High Severity

The FUSDT token entry is {} with no metadata fields. According to the PR description, it needs name, decimals: 18, erc20: true, symbol: "FUSDT", and a logo. Without these fields, the token will be unrecognizable to consumers — no name, no symbol, no decimal precision, and no logo rendering. There's also no corresponding metadata JSON file under the metadata/eip155:1/ directory.