rwa.registry.deployments table.Tables
All new RWA work should build on therwa.* schema below. It replaces the crosschain.rwa.* tables (see Legacy Tables at the bottom of this page), which are deprecated but still queryable.
| Table Name | Description |
|---|---|
rwa.registry.catalog | Product-grain registry of tracked RWA tokens with public-safe taxonomy — issuer, asset class/type, and deployment count. |
rwa.registry.deployments | Deployment-grain registry of RWA token contracts across chains, including native vs. derivative (bridged/wrapped) classification, underlying asset ticker, and active status. |
rwa.core.transfers | Raw RWA token transfer events across chains with sender, receiver, token metadata, and USD valuation. |
rwa.core.supply_daily | Daily RWA token supply, price, and market cap by chain and token, with issuer/platform/product metadata. |
rwa.core.supply_latest | Most recent (last 3 days) daily supply snapshot per chain/token, deduplicated to one row per token. |
rwa.core.supply_change | RWA token supply change (mint/burn) events across chains with token metadata and USD valuation. |
rwa.core.balances_daily | Daily forward-filled RWA token balances by holder address across chains, with circulating-supply classification. |
rwa.core.balances_latest | Most recent end-of-day RWA token balance per holder address/token, joined to product/issuer registry metadata and latest price. |
RWA Classification
Products are classified by a two-levelasset_class / asset_type pair:
Blockchain Coverage
RWA data is available for the following blockchains:Frequently Asked Questions
Why is a token I know of not showing up in Allium's RWA data?
Why is a token I know of not showing up in Allium's RWA data?
rwa.registry.deployments for a few different reasons:- Not yet onboarded. Allium’s RWA coverage is actively expanding, and there is always a queue of legitimate products we haven’t added yet. This is the most common reason for a genuine gap.
- No verifiable price/NAV source. Every product needs either an on-chain price feed, an oracle partnership, or a public off-chain NAV source (e.g. SEC fund filings) before it can be added. See Classification Framework. Some issuers simply don’t publish NAV anywhere publicly, so the product can’t be priced even if the on-chain token exists.
- Insufficient documentation. If we can’t verify what a token actually represents from issuer disclosures, we don’t guess. It stays excluded until documentation surfaces.
- Doesn’t meet our RWA definition. See the next question. Some tokens that other trackers list as “RWA” are intentionally excluded under Allium’s classification framework, such as crypto-collateralized yield tokens or payment-instrument stablecoins.
I'm an RWA issuer or platform. How do I get my product's price integrated?
I'm an RWA issuer or platform. How do I get my product's price integrated?
getPrice(), getNav()), or a public off-chain feed such as an SEC fund filing. On-chain and oracle sources are the fastest to integrate and the most durable over time, so those are preferred where available. Once a verifiable source is confirmed, the product can be added to the RWA registry and priced going forward.Why do Allium's RWA totals differ from other data providers?
Why do Allium's RWA totals differ from other data providers?
- Native supply only, not bridged duplicates. When a token is bridged across chains, some trackers sum the native deployment and every bridged/wrapped derivative as if they were independent supply. Allium counts only native deployments (tokens the issuer can mint directly) toward supply. Bridged tokens and other derivative wrappers are tracked separately and excluded from supply to avoid double-counting.
- Classification differences. The same product can land in a different bucket depending on the framework. See Classification Framework for how Allium draws these lines, including where we intentionally exclude crypto-native “active strategy” products that other trackers count as RWA.
Why aren't crypto funds (e.g. tokens tracking BTC/ETH basis trades, funding rates, or MEV) classified as RWA?
Why aren't crypto funds (e.g. tokens tracking BTC/ETH basis trades, funding rates, or MEV) classified as RWA?
Does Allium include private credit or other off-chain-reported loan books in RWA totals?
Does Allium include private credit or other off-chain-reported loan books in RWA totals?
rwa.* tables focus on the portion that is actually tokenized and distributed on-chain, since that’s the figure Allium can verify end-to-end. Some private-credit platforms report a much larger “assets under management” figure that includes loans administered off-chain, where the blockchain is used only as an internal record and no token is issued or transferred to on-chain investors. Allium tracks that represented value too, but it isn’t part of the distributed totals in the rwa.* tables documented here.How is native vs. derivative (bridged/wrapped) classification determined?
How is native vs. derivative (bridged/wrapped) classification determined?
chain + address deployment as native or derivative (bridged, lending-receipt, vault-share, or other wrapped representation), the same native/derivative model used for stablecoins. The test is whether the issuer can mint new tokens on that chain directly, without relying on an external bridge protocol:- Native. The issuer’s own contract or wallet controls minting on that chain. Most major institutional RWA issuers (BlackRock, Franklin Templeton, Ondo, etc.) deploy natively on each chain they support, rather than bridging a single deployment around.
- Derivative. The token exists on that chain only because a bridge (e.g. LayerZero, Wormhole, CCIP) transported supply there, or a DeFi protocol wrapped it (lending receipt, yield vault, etc.). Derivatives are tracked in
rwa.registry.deploymentsfor reference but excluded from supply and market-cap totals, since the underlying value is already counted at its native deployment.
Legacy Tables
Legacy Tables
crosschain.rwa.*. They are deprecated in favor of the rwa.* tables above, but remain queryable for existing use cases.| Table Name | Description | Replacement |
|---|---|---|
crosschain.rwa.tokens | Master reference table for RWA tokens with metadata, issuer, and platform information. | rwa.registry.deployments |
crosschain.rwa.transfers | All transfers of RWA tokens across different blockchains. | rwa.core.transfers |
crosschain.rwa.supply | Daily supply snapshots of RWA tokens across different blockchains. | rwa.core.supply_daily |
crosschain.rwa.supply_latest | Latest supply snapshot per RWA token. | rwa.core.supply_latest |
crosschain.rwa.supply_change | Transfers that resulted in supply changes (mints and burns) of RWA tokens. | rwa.core.supply_change |
crosschain.rwa.balances_daily | Daily historical balances for RWA token holders across different blockchains. | rwa.core.balances_daily |
crosschain.rwa.balances_latest | Latest balances for RWA token holders. | rwa.core.balances_latest |
crosschain.rwa.metrics_daily | Daily metrics combining supply, transfer, transaction, and user activity metrics for RWA tokens. | No replacement yet — table remains available |
crosschain.rwa.trades | All RWA trades across different blockchains and platforms (RWA platforms and DEXs). | No replacement yet — table remains available |
crosschain.rwa.equities_trades | Trades executed on tokenized equities across different blockchains. | No replacement yet — table remains available |