Tempo Token List Registry

A Uniswap Token Lists-compatible API for token metadata and icons on Tempo.

As an example, here's Tempo's tokenlist, fetched from tokenlist.tempo.xyz/list/4217:

Token list API endpoints

Adding a New Token

1. Fork tempoxyz/tempo-apps

2. Add token to data/<chain_id>/tokenlist.json in apps/tokenlist:

   {
     "name": "piUSD",
     "symbol": "PiUSD",
     "decimals": 6,
     "chainId": 4217,
     "address": "0x...",
     "extensions": {
       "chain": "tempo",
       "coingeckoId": "pi-usd"
     }
   }

3. Add icon to data/<chain_id>/icons/<address>.svg (lowercase address) in apps/tokenlist

   Separately, TIP-20 tokens can also carry an optional on-chain logoURI (TIP-1026) that wallets and explorers read directly from the token contract. Because that icon is fetched from an untrusted source, TIP-1026 recommends a square, rasterized PNG or WebP (max 256 bytes; https, http, ipfs, or data scheme). Setting it is optional and independent of this PR — registering here still adds richer metadata (coingeckoId, bridgeInfo, display label) and a fallback icon for clients that don't read on-chain logoURI.

4. Submit PR with as much information as you think is helpful for review.

Token Extensions

Tokens support optional extensions for richer metadata:

For bridged tokens, include bridgeInfo so aggregators like DeFi Llama can automatically map to the canonical asset:

{
  "extensions": {
    "chain": "tempo",
    "coingeckoId": "usd-coin",
    "bridgeInfo": {
      "sourceChainId": 1,
      "sourceAddress": "0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48"
    }
  }
}

For native tokens (e.g., PathUSD), omit bridgeInfo:

{
  "extensions": {
    "chain": "tempo",
    "coingeckoId": "pathusd"
  }
}

Icon Requirements

• Format: SVG
• Address filename must be lowercase (e.g., 0xabcd...1234.svg)
• Recommended: square aspect ratio, minimal whitespace

Full OpenAPI Spec →