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
This removes essentially all token/contract metadata (name/symbol/decimals/logo/erc flags) from contract-map.json, leaving only address keys with empty objects, which is likely to break any consumers relying on that metadata. It also adds the FUSDT address but does not include its metadata, suggesting an unintended destructive change.

Overview
contract-map.json is rewritten from a large address→metadata registry to an address-only map where each entry’s value is an empty object.

The new FUSDT contract address (0x419ecA43dB68E868E68d1aB460c8AC32523c7540) is included, but its metadata (and all other contracts’ metadata) is removed in this change.

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

[cursor]

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

[cursor]

All existing token metadata wiped to empty objects

High Severity

Every existing token entry in contract-map.json has been replaced with an empty object {}, destroying all metadata (name, logo, erc20, symbol, decimals) for hundreds of tokens. This package is @metamask/contract-metadata, consumed via index.js which does module.exports = require("./contract-map.json"). Any application relying on this data (e.g. MetaMask wallets looking up token names, symbols, decimals, or logos) will get empty objects instead of token information, effectively breaking token display for all listed assets.

 

[cursor]

New FUSDT entry has no metadata at all

High Severity

The new FUSDT entry at 0x419eca43db68e868e68d1ab460c8ac32523c7540 is an empty object {} — it doesn't include name, symbol, decimals, logo, or erc20 fields described in the PR. Additionally, the address is all-lowercase rather than EIP-55 checksummed, violating the repository's documented requirement that "All address keys follow the EIP 55 address checksum format."