Need verifiable oracle data for your project?
DIA provides transparent, customizable price feeds across 50+ chains with fully auditable methodology.
Market cap
DeFiLlama estimate
DIA price
Total supply
Holders
48.1M iUSD
1,464holders
What the top-10 is
Shares of the same supply as Top-10, from public address labels covering 86.2% of the top-10 balance. Exchange custody is one address holding for many end holders. Unattributed means unlabelled, not self-custodied.
Measured on Ethereum. Shares are of the Ethereum supply, not the multi-chain total.
+1.5M iUSDsince Fri, Aug 28 UTC
Change in the supply DIA reads across this coin’s chains, between two daily snapshots. Not mints minus redeems: DIA does not publish issuance flow.
Market data · CoinGecko
Market data · CoinGecko
Circulating supply · DeFiLlama
Aggregator figure, not a contract read. DIA’s own onchain supply is the separate series below.
Percentage change in iUSD's circulating supply as reported by DeFiLlama, measured against that source's own past. It is not a change in the onchain supply above, which DIA reads from the contracts directly and which is a different measurement of the same coin. A dash means the map has no reading close enough to the start of the window, a stretch inside it where supply was not reported at all, or a starting figure too small for a percentage to describe. Hover a dash for which.
$8K
deployed across 1 market on 1 protocol
Lower bound: iUSD's balance inside lending markets DIA reads on-chain directly. Excludes DEX liquidity, CDP collateral, and any market on a chain or protocol DIA does not yet track. DIA has no price snapshot on file for iUSD, so this figure is converted using a DeFiLlama market price instead of DIA's own read.
DIA price
—
Peg deviation
—
Peg currency
USD
Primary use
—
Last snapshot
Fri, Sep 4 UTC
iUSD is a synthetic dollar stablecoin from InfiniFi. It is minted by depositing stablecoins into the protocol, which deploys them across its fractional-reserve model and distributes yield to holders.
InfiniFi is a DeFi protocol. iUSD is a yield-bearing synthetic dollar rather than a fiat-backed coin, so it carries no issuer licence. The model takes deposits and puts them to work, which is what funds the yield.
The token is deployed on Ethereum per the verified contract set DIA holds.
Sources: infinifi.xyz/, blockworks.com/news/yield-protocol-infinifi-banking-onchain
iUSD is synthetic. Its backing is stablecoin deposits deployed across the protocol's fractional-reserve model to earn yield. The peg and yield are managed by that deployment rather than by a segregated fiat reserve.
Because the mechanism is onchain, DIA's supply read and the protocol's state are the same class of evidence. This page does not present a fiat reserve that iUSD does not hold.
What DIA reads regardless. Supply is read from contract state on the chains DIA indexes.
Sources: infinifi.xyz/, blockworks.com/news/yield-protocol-infinifi-banking-onchain
The structural risk to state for iUSD is its fractional-reserve deployment: the peg and redemption depend on the protocol's deployed positions weathering stress, which differs from a fully reserved fiat coin.
A fractional reserve means the redeemable value depends on the deployed positions covering withdrawals, so a drawdown on the book is the risk vector. InfiniFi's issuer and licence posture was not fully documented in the evidence pull. The honest statement is a synthetic dollar with an onchain deployment.
Supply is read from the Ethereum leg of the onchain record as of the 2026-08-05 snapshot.
Sources: infinifi.xyz/, blockworks.com/news/yield-protocol-infinifi-banking-onchain
DIA reads iUSD supply from contract state on the chains it indexes. That is proof of onchain supply, not proof of a fiat reserve.
Sources: infinifi.xyz/, blockworks.com/news/yield-protocol-infinifi-banking-onchain
0x48f9e38f…22e3d89cExplorer ↗Supply on this page is read from these contracts. Addresses are verified by DIA against the issuer’s own published documentation.
0x48f9e38f…22e3d89cpaused()mint(address,uint256)Read from the deployed contract. “Not determined” means the contract’s full function set could not be enumerated, not that the capability is absent: a bytecode scan can confirm that a function exists and can never prove that one does not.