Token Lists primary sources
Reviewed: 2026-05-12 UTC
Core specification
- https://github.com/Uniswap/token-lists
- Canonical repository for the Token Lists specification.
- https://raw.githubusercontent.com/Uniswap/token-lists/main/README.md
- Best concise source for what Token Lists is, who can publish a list, how validation works, semantic-versioning rules, and preferred hosting patterns.
- https://raw.githubusercontent.com/Uniswap/token-lists/main/src/tokenlist.schema.json
- Canonical schema defining required fields, optional tags/keywords/extensions, list metadata, and token-level metadata.
- https://uniswap.org/tokenlist.schema.json
- Canonical schema ID referenced by the spec.
Launch framing and trust model
- https://blog.uniswap.org/token-lists
- Best source for the intended control-plane split: discovery and reputation should be decoupled from gatekeeping, projects attach reputation by hosting lists they control, and interfaces can combine multiple lists rather than rely on one default list.
Discovery layer
- https://tokenlists.org/
- Public discovery site for the ecosystem around Token Lists.
- https://github.com/Uniswap/tokenlists-org
- Repository for the list-discovery website.
- https://raw.githubusercontent.com/Uniswap/tokenlists-org/master/README.md
- Best concise source for the website’s role as a discovery surface rather than the specification itself.
Main takeaways from this pass
- Token Lists is most useful as a publisher-reputation and schema baseline for token discoverability, not as a neutral directory.
- The main layers are: publisher-authored lists, host-level identity via ENS/IPFS/HTTPS, schema-constrained metadata, client-side validation, and interface-specific import/aggregation policy.
- The launch post is especially important because it explicitly rejects a single centralized default list and instead pushes trust to public list publishers and interface aggregation logic.
- The schema is important because it shows what becomes canonical and reusable across the ecosystem: token identity fields, tags, keywords, optional extensions, and versioning conventions.
- Token Lists belongs in the active corpus because it gives the library a strong non-challenge-based comparison point beside Kleros-style token registries and app-maintained allowlists.