Skip to main content
rwa_multichain.supply_changes isolates events that increase or decrease onchain supply from ordinary wallet-to-wallet movement. Grain: one row per native supply-change event.

What it answers

  • How much of an asset was minted or redeemed, and when
  • Whether net flows are positive or negative over a period
  • Whether onchain mint and redeem events reconcile against what an issuer or custodian reports on their own books
That last one is the use case customers ask for most: an independent onchain check on issuer-reported subscription and redemption figures.

Table schema

Use direction for net flow

amount is always unsigned. Apply the sign from direction:
event_type explains why the supply moved. direction explains whether the onchain supply increased or decreased. For example, clawback is a decrease and interest_distribution is an increase.

Relationship to transfers

transfers is the canonical transfer surface and marks lifecycle rows with is_supply_event. On Tempo, zero-address TIP-20 issuance and redemption rows are retained in transfers with is_supply_event = true. This table derives each of those events once from the canonical transfer rows and verifies them against native TIP-20 Mint and Burn events.
A mint or burn can therefore be a row in both transfers and supply_changes. Use transfers with NOT is_supply_event for peer-to-peer movement, and use supply_changes for issuance and redemption. Do not union or sum the two surfaces.

Example query

Largest single subscriptions and redemptions:
Net flow by issuer: