# @uniswap/unsupported-token-list

[![Tests](https://github.com/Uniswap/token-lists/workflows/Tests/badge.svg)](https://github.com/Uniswap/unsupported-token-list/actions?query=workflow%3ATests)
[![npm](https://img.shields.io/npm/v/@uniswap/unsupported-token-list)](https://unpkg.com/@uniswap/unsupported-token-list@latest/)

This NPM module and GitHub repo contains the unsupported token list used in the Uniswap interface.

Adding a new chain:

1. Add a new file in src/tokens with the chainname
2. update buildlist to include the chain
3. add a unit test in test/uniswap-unsupported.test.js to verify the chainId is in the list

Adding/updating tokens via DynamoDB script:

Prereqs
- Use Node 20+ locally, or keep Node 18 and use the pinned AWS SDK versions already in package.json
- Set AWS credentials in your shell:
  - export AWS_PROFILE=your-profile
  - export AWS_REGION=us-east-2

Steps
1. Populate target tokens at the top of `src/scripts/addTokensFromDynamo.ts` (array of `{ chainId, address }`).
2. Run:
   - `yarn add-tokens-from-dynamo`
3. The script:
   - Fetches `name`, `symbol`, `decimals` for those tokens from DynamoDB
   - Prints a table to the console
   - Upserts those tokens into the corresponding JSON files in `src/tokens/` based on `chainId`
   - Normalizes symbols (uppercase, no spaces) to satisfy the token list schema
4. Commit the JSON edits and bump `package.json` version (the list embeds this semver):
   - `npm version patch` (or minor/major)
5. Open PR and merge to `main`. CI will build/publish and pin to IPFS.