Practical overview
When it fits
Use Tokenlists when a dApp needs published token data by chain, or when a development team wants to run or contribute to the repository’s aggregation workflow.
Who it is for
- dApp developers who need token-list data for a particular blockchain.
- Developers maintaining or extending a multi-provider token aggregation workflow.
Documented uses
- Retrieve a chain-specific JSON token list for use in a dApp.
- Aggregate provider token lists using the repository’s two-list inclusion rule.
- Generate a README from aggregated data.
- Propose additional providers, tokens or chains through repository contributions.
Requirements & limits
The token data is published as raw JSON files in a public GitHub repository. The repository is licensed under MIT.
- A token must occur in at least two different provider lists to be included.
- The README presents JSON files for direct dApp use, not a maintained query endpoint for this repository’s data.
- Its listed providers include CoinGecko, 1inch, Uniswap, Sushiswap and OpenOcean.
- The README says chain token counts are approximate and may vary as providers update their lists.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Use a chain-specific JSON list in a dApp
Retrieve the published token data file for a supported chain for use in a dApp.
Before you start
- A dApp that can use a JSON token list.
- The raw JSON URL for the required chain.
Steps
Choose the blockchain whose token data the dApp needs.
Download that chain’s JSON file; the README gives Ethereum and Binance Smart Chain raw-file examples.
Use the downloaded list in the dApp.
Expected outcome
A chain-specific JSON token list is available for the dApp to consume.
Guide limitations
- The README gives example raw links for Ethereum and Binance Smart Chain; it does not document a query endpoint.
- The inclusion rule requires appearance in at least two different provider lists and is not a guarantee of token legitimacy.
Run the documented token aggregation workflow
Install the repository requirements and run its aggregation script.
Before you start
- Python 3 and pip3.
- A local copy of the repository.
Steps
From the repository, install dependencies with the command below.
pip3 install -r requirements.txtFrom the repository root, run the command below.
python3 aggregate_tokens.py
Expected outcome
The documented aggregation script has been run; the README does not specify further output handling in this workflow.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 15 October 2026
- Original website title
- viaprotocol/tokenlists · Official homepage title · retained in its source language

