Market cap
DIA price
Total supply
Holders
6.7B USDS
16,440holders
What the top-10 is
Shares of the same supply as Top-10, from public address labels covering 91.7% 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.
-$54.4Msince 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 USDS'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.
3 of the 4 chains DIA holds a verified USDS contract on carry a deployment date and are plotted here. The other 1 was verified without one and is left off the curve rather than dated to the day DIA read it.
$744.2M
deployed across 4 markets on 4 protocols
Lower bound: USDS'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 price
$1.0002
Peg deviation
2 bps
Peg currency
USD
Primary use
—
Last snapshot
Fri, Sep 4 UTC
USDS is the US dollar stablecoin of the Sky Protocol. It sits alongside DAI, and the two convert into each other through the DAI USDS converter at a fixed 1:1 ratio with no fees, a route Sky's documentation states cannot have fees enabled later (Sky Protocol Docs).
The contract
The token is an ERC-20 with permit support and EIP-1271 smart contract signature validation. It is deployed behind an ERC-1967 proxy using the UUPS pattern, so the implementation is upgradeable by whoever holds the upgrade authorization (Sky Protocol Docs).
This map records USDS on Ethereum, Base, Arbitrum and Solana. Supply outside Ethereum is bridged representation.
Sources: Sky Protocol Docs, USDS token
What the disclosure shows
USDS is issued against collateral held in Sky vaults. Sky's documentation describes the vault system, the collateral parameters that govern it, and the liquidation machinery that unwinds an undercollateralised position (Collateral Liquidation).
Sky publishes a live collateral and financials dashboard in place of a reserve attestation. That dashboard is JS-rendered and returned no readable values in this research, so no collateral total, category split or counterparty figure is stated here. Those numbers are not machine-readable at source.
What it leaves out
No reserve attestation or audit opinion for USDS was found in this research. Nothing was located that names an accounting firm, a standard such as ISAE 3000 or AT-C 105, or a reporting period.
The collateral position of USDS is documented as a mechanism, not as an audited balance. A reader can read the vault and liquidation rules in Sky's own documentation. No third-party sign-off on what the system holds has been published.
Sources: Sky Protocol Docs, Collateral Liquidation, Sky Protocol Docs, USDS token
Liquidation is auction-dependent
Sky's documentation describes Dutch auctions run by the Dog and Clipper contracts, priced off the Oracle Security Module, and it lists the failure modes itself: price curves that fall too fast or too slow, oracle delays producing stale prices, parameter changes hitting live auctions, and incentive farming (Collateral Liquidation).
The contract is upgradeable
The token contract is upgradeable through a UUPS proxy. Holders depend on Sky governance not authorizing a harmful implementation (Sky Protocol Docs).
The disclosure gap
With the financials dashboard not machine-readable and no attestation published, the size and composition of the collateral backing USDS cannot be independently confirmed from a source that returns readable content.
Sources: Sky Protocol Docs, Collateral Liquidation, Sky Protocol Docs, USDS token
The Global Stablecoin Map tracks USDS across Ethereum, Base, Arbitrum and Solana.
Covered on chain: token supply on each of the four networks, market price against the USD peg, and the venues where USDS trades. The same reads back DAI, the other Sky token on this map.
Not covered: the collateral behind it. The trust boundary for the collateral position is Sky governance and its counterparties, and no on-chain read closes it. Supply on the three non-Ethereum networks is bridged representation, so a supply read there is a claim about the bridge as much as about USDS (Sky Protocol Docs).
Sources: Sky Protocol Docs, USDS token
USDS is issued against collateral held in Sky vaults. Sky publishes a live collateral dashboard, but it is JS-rendered and returned no readable values in this research, so no collateral total or category split is stated here.
No reserve attestation or audit opinion for USDS was found. Nothing was located naming an accounting firm, a standard such as ISAE 3000 or AT-C 105, or a reporting period.
Sky's DAI USDS converter swaps the two at a fixed 1:1 ratio with no fees, and Sky's documentation states fees cannot be enabled on that route later.
DIA tracks USDS on Ethereum, Base, Arbitrum and Solana. Supply outside Ethereum is bridged representation.
Yes. USDS is deployed behind an ERC-1967 proxy using the UUPS pattern, so the implementation is upgradeable by whoever holds the upgrade authorization.
0x6491c05a…749b876bExplorer ↗0x820c137f…168921dcExplorer ↗0xdC035D45…e407384FExplorer ↗USDSwr9Apd…R81vTwcAExplorer ↗Supply on this page is read from these contracts. Addresses are verified by DIA against the issuer’s own published documentation.
0x6491c05a…749b876bmint(address,uint256)eip1967-uups0x820c137f…168921dcmint(address,uint256)eip1967-uups0xdc035d45…e407384fmint(address,uint256)eip1967-uupsUSDSwr9Apd…R81vTwcAfreezeAuthoritymintAuthorityRead 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.
Reserve attestation cadence
A continuously-updating reserve feed rather than a periodic report.