rwa_multichain.supply

rwa_multichain.supply tracks total outstanding supply per token per chain as a daily series. Grain: one row per token per chain per day. Use it for AUM and supply trends instead of aggregating every holder balance.

Why use it over aggregating balances

Summing balance from balances gives the same answer, but it scans every holder row for every day in the window — expensive for a metric you often want across all assets and a long history. This table is pre-aggregated, so supply trends and AUM charts read one row per token per day. It also carries supply_usd already valued with rwa_multichain.prices, so per-product AUM does not require a manual point-in-time join.

Table schema

Column	Type	Description
`blockchain`	`VARCHAR`	Chain for the token deployment
`day`	`DATE`	Supply snapshot date
`token_symbol`	`VARCHAR`	RWA token symbol
`token_address`	`VARCHAR`	Normalized native token identifier
`token_id`	`VARCHAR`	Normalized cross-chain token identifier, joins to `rwa_multichain.tokens`
`token_standard`	`VARCHAR`	Native token standard or asset namespace, including `tip20` for Tempo
`supply_raw`	`UINT256`	Total outstanding supply in native precision
`supply`	`DOUBLE`	Decimals-adjusted outstanding supply
`supply_usd`	`DOUBLE`	Supply valued with `rwa_multichain.prices.price_usd`
`last_updated`	`TIMESTAMP`	Block time of the latest supply change reflected in this snapshot

Supply is per chain, not per asset

An asset deployed on several chains has one row per chain per day. Cross-chain total supply for a single asset means summing across blockchain:

SELECT day, token_symbol, SUM(supply) AS total_supply
FROM rwa_multichain.supply
WHERE token_symbol = 'BUIDL'
GROUP BY 1, 2

Reading a single chain’s row as the asset’s total supply is the most common mistake on this table. Tempo is EVM-compatible but its supply rows use token_standard = 'tip20', not erc20. They inherit the balance reconstruction support boundary of 2026-05-05, which should not be interpreted as Tempo’s start date.

Example query

-- Supply trend for the largest assets
SELECT
  day,
  token_symbol,
  SUM(supply) AS supply,
  SUM(supply_usd) AS supply_usd
FROM rwa_multichain.supply
WHERE day >= CURRENT_DATE - INTERVAL '90' DAY
GROUP BY 1, 2
ORDER BY 1 DESC, 4 DESC NULLS LAST

Net supply change over the last 30 days, by asset class:

WITH windowed AS (
  SELECT
    r.product_asset_class AS asset_class,
    s.token_id,
    MIN_BY(s.supply_usd, s.day) AS supply_start,
    MAX_BY(s.supply_usd, s.day) AS supply_end
  FROM rwa_multichain.supply AS s
  INNER JOIN rwa_multichain.tokens_reference_data AS r
    ON r.blockchain = s.blockchain
    AND r.token_id = s.token_id
  WHERE s.day >= CURRENT_DATE - INTERVAL '30' DAY
  GROUP BY 1, 2
)
SELECT
  asset_class,
  SUM(supply_start) AS supply_usd_30d_ago,
  SUM(supply_end) AS supply_usd_now,
  SUM(supply_end) - SUM(supply_start) AS net_change_usd
FROM windowed
GROUP BY 1
ORDER BY 4 DESC NULLS LAST

Curated Data

Solana

Hyperliquid

Non-EVM Networks

Protocols

EVM Networks

Partner Data

Dune Index

rwa_multichain.supply

Why use it over aggregating balances

Table schema

Supply is per chain, not per asset

Example query

​Why use it over aggregating balances

​Table schema

​Supply is per chain, not per asset

​Example query

Why use it over aggregating balances

Table schema

Supply is per chain, not per asset

Example query