Skip to main content
rwa_multichain.tokens_reference_data is the reference table for every token in rwa_multichain.tokens. Grain: one row per token per chain, keyed on (blockchain, token_standard, token_id).

Why it is separate from tokens

tokens answers “does this token exist and what is its identifier”. tokens_reference_data adds the issuer label, balance behavior and product reference fields. Tokens without an associated product remain available with product_id and the attached product fields null. The token inventory is broader than active researched product metadata. Tokens linked to products outside the metadata research scope retain available product, issuer and platform identity, while fields sourced from the filtered product_reference_data view can be null. Excluding a product’s archived enrichment does not delete its token registration or historical activity. An inner join to product_reference_data limits the result to research-scope products. A product and a token are not the same thing. One product — say Franklin Templeton’s BENJI fund — has a row per chain it is deployed on, and the product-level columns repeat identically across those rows. Deduplicate on product_id when you are counting products rather than deployments. For the product catalog itself, use product_reference_data.

Join keys

Do not join balances_enriched on product_id. One product has many chain tokens, so that join fans out.

Product classification

asset_id identifies the shared asset referenced by a research-scope product. The linked asset supplies asset_class (broad exposure), asset_subclass (narrower exposure) and asset_type (financial form). These are mirrored through product_reference_data for token-grain queries. The product reference page lists all allowed values. Multiple tokenized Tesla products can therefore share an asset classification while retaining different issuers and tokenisation terms. Unknown asset links and classifications remain null. Archived products can retain a non-null product_id and identity fields while researched classification is null. issuer is the token-list label. issuer_name is the legal issuer from product metadata. They are not interchangeable.

Table schema

Token identity Product attach (null when product_id is null)

Do not join on symbol

Token symbols are not a safe product key. The same product carries different tickers across access channels, unrelated products share tickers, and scam tokens squat real tickers on other chains. Join on (blockchain, token_id) or token_product_id, never on symbol or underlying_ticker.

Example queries

AUM, holders, and product count by economic asset class:
Join enriched balances on token_product_id: