Registry - Token Terminal Docs

The identity table behind every token figure. Every other table about tokens joins to it, and Coverage names the chains.

Columns

Column	Type	Description
`token_id`	`STRING`	Token identifier: `{token_address}-{chain_id}`. The key every other token table joins on, and every row has a real address in it.
`chain_id`	`STRING`	Chain the contract is deployed on.
`token_address`	`STRING`	Contract address. Hex addresses are stored lowercase, and base58 addresses as the chain writes them.
`symbol`	`STRING`	Symbol read from the contract, unverified. Any contract can call itself USDC, so read `token_address` to know what a token is, or the `asset_id` on `dimensions.asset_tokens` where somebody has already made that judgment.
`name`	`STRING`	Name read from the contract, unverified.
`decimals`	`INT64`	How many decimal places to move to turn a raw amount into a token amount.
`created_at`	`TIMESTAMP`	When the token launched onchain.

Sample queries

By address
Its curated asset

token_id is the address and the chain joined by a dash, so one literal names one contract on one chain. symbol and name come off the contract, so read the address to know what the token is.

select
    token_id,
    chain_id,
    token_address,
    symbol,
    name,
    decimals,
    created_at
from `dimensions.tokens`
where token_id = '0xdac17f958d2ee523a2206206994597c13d831ec7-ethereum'

Whether a token is a tokenized asset, and which one, lives on dimensions.asset_tokens, one row per deployment, joined on the same token_id. The join keeps the tokens somebody has matched to a curated asset.

select
    tokens.token_id,
    tokens.symbol,
    deployments.asset_id,
    deployments.bridged_status
from `dimensions.tokens` as tokens
join `dimensions.asset_tokens` as deployments
    using (token_id)
where tokens.token_id = '0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48-ethereum'