Supply Daily

The stablecoins.core.supply_daily table gives a daily snapshot of total supply for every tracked stablecoin deployment, alongside two circulating supply figures with different levels of adjustment, and registry metadata (issuer, peg mechanism, stablecoin type) joined in. Unique Key: date, chain, token_address

Table Columns

Column Name	Description
`is_verified`	True if this deployment has been manually verified by Allium.
`is_native`	True if this is the issuer’s canonical deployment on this chain, false if bridged/wrapped.
`stablecoin_type`	Classification of the stablecoin mechanism (e.g. fiat_backed, crypto_backed, yield_bearing).
`product_id`	Internal Allium identifier for the stablecoin product. Join key to `stablecoins.registry.catalog`.
`issuer_id`	Entity that issues or backs the stablecoin (e.g. circle, tether).
`currency`	Fiat or reference currency this stablecoin is pegged to, lowercase ISO code (e.g. usd, eur, jpy).
`peg_mechanism`	Mechanism used to maintain the peg (e.g. fiat_backed, crypto_overcollateralized, algorithmic).
`date`	The date of the supply snapshot.
`chain`	The blockchain network of this deployment.
`token_address`	The contract/mint address of the stablecoin on this chain.
`token_name`	The name of the token.
`token_symbol`	The symbol of the token.
`total_supply`	The token’s total supply, decimal-normalized, as reported by the deployment’s `totalSupply()` (or equivalent).
`total_supply_usd`	`total_supply` converted to USD. Null if it would exceed Allium’s sanity-check ceiling for a single chain/asset.
`circulating_supply`	`total_supply` minus issuer-basis exclusions (treasury, pre-mint, and issuer-reserve wallets). Matches what the issuer reports on their own transparency page.
`circulating_supply_usd`	`circulating_supply` converted to USD. Null if it would exceed Allium’s sanity-check ceiling.
`adjusted_circulating_supply`	`total_supply` minus a broader set of exclusions — issuer-basis plus bridge escrows, protocol collateral, savings vaults, and frozen/banned addresses. Allium’s estimate of the supply that is actually free-floating and tradeable.
`adjusted_circulating_supply_usd`	`adjusted_circulating_supply` converted to USD. Null if it would exceed Allium’s sanity-check ceiling.
`price_usd`	USD price used to derive the `_usd` supply columns for this date.
`_metadata`	JSON object with `price_source`, `supply_source`, and `integration_status` for this row.
`unique_id`	Unique identifier for the row.
`_created_at`	Timestamp this row was first created.
`_updated_at`	Timestamp this row was last updated.

Sample Query

Compare an issuer’s reported-style circulating supply against Allium’s adjusted circulating supply for a single product

select
    date,
    chain,
    token_symbol,
    total_supply,
    circulating_supply,
    adjusted_circulating_supply,
    circulating_supply - adjusted_circulating_supply as extra_supply_removed
from stablecoins.core.supply_daily
where product_id = 'usdt' -- example product_id
order by date desc
limit 30

Why `adjusted_circulating_supply` differs from other providers

Most third-party aggregators (issuer transparency pages, DeFiLlama, CoinGecko) publish a single “circulating supply” figure that is calculated as:

total_supply − issuer-reported exclusions (treasury, pre-mint, reserves)

Allium calculates that same figure as circulating_supply, and it should reconcile with those sources within a few percent. adjusted_circulating_supply is a second, more conservative figure that most providers don’t compute at all: it removes an additional layer of supply that is technically outstanding (it still counts toward total_supply) but is economically inert — locked away where it cannot trade or move without first passing through another contract.

Because this extra layer isn’t subtracted by most other sources, Allium’s adjusted_circulating_supply is expected to run lower than the “circulating supply” reported elsewhere for the same token. That is by design, not a data quality issue.

The two exclusion layers

Layer	What it removes	Reconciles with
Issuer-basis (folded into `circulating_supply`)	Treasury, pre-mint, and issuer-reserve wallets	Issuer transparency pages, and most third-party aggregators
Non-issuer-basis (additional exclusions in `adjusted_circulating_supply`)	Bridge escrows, collateral locked in other stablecoins/protocols, savings-vault deposits, and frozen/banned addresses	No public benchmark — this is Allium’s own methodology

The non-issuer-basis layer covers supply that is still sitting in the totalSupply() count, but isn’t free-floating:

Bridge escrows — when a stablecoin is bridged with a lock-and-mint design, the locked tokens on the source chain back a wrapped copy on the destination chain. They can’t move again until the wrapped copy is burned, so they aren’t part of the tradeable float.
Stablecoin/protocol collateral — tokens locked inside another stablecoin’s minting contract (e.g. USDC backing USDe) or a DeFi protocol’s treasury/reserve. These are committed to backing something else, not available to trade.
Savings-vault deposits — the underlying token held inside a yield-bearing wrapper for that same token (e.g. USDS inside sUSDS). The vault is a large holder, not an end user.
Frozen / banned addresses — balances the issuer has blacklisted. Still counted in totalSupply(), but permanently inaccessible.

stablecoins.core.supply_daily surfaces only the two final supply figures (circulating_supply and adjusted_circulating_supply) — it does not expose a separate exclusion-amount or per-address breakdown column. None of the excluded supply is “missing” — it all still exists on-chain and is included in total_supply. Allium just separates out the portion that is contractually or technically committed elsewhere, to answer a different question than “what has been minted”: what supply is actually free to trade in markets right now?

When to use which column

Use circulating_supply when reconciling against an issuer’s published circulating supply, CoinGecko, or DeFiLlama’s default figure.
Use adjusted_circulating_supply when you need the real, tradeable float — for example, market-cap-to-float ratios, liquidity analysis, or any use case where bridge-locked or collateral-locked supply would overstate what’s actually available.

Legacy Schema

crosschain.stablecoin.supply_beta is deprecated in favor of stablecoins.core.supply_daily above. It was never documented on this site; it exposed total_supply/circulating_supply/non_circulating_supply (plus USD variants) at a date, chain, token_address grain, without the adjusted-circulating-supply methodology described above.

Overview

Data Verticals

Solana

Hyperliquid

Lighter

Bitcoin Ecosystem

EVM

Cosmos Ecosystem

Move Ecosystem

Other Ecosystems

Table Columns

Sample Query

Why `adjusted_circulating_supply` differs from other providers

The two exclusion layers

When to use which column

​Table Columns

​Sample Query

​Why adjusted_circulating_supply differs from other providers

​The two exclusion layers

​When to use which column

Table Columns

Sample Query

Why `adjusted_circulating_supply` differs from other providers

The two exclusion layers

When to use which column