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
75.2M lisUSD
+1.9K lisUSDsince Thu, Aug 27 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 lisUSD'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.
$27.7M
deployed across 6 markets on 2 protocols
Lower bound: lisUSD'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 lisUSD, 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
Thu, Sep 3 UTC
lisUSD is a borrow-side stablecoin on BNB Chain. Users lock crypto collateral in Lista DAO vault contracts and draw lisUSD against the deposit, then repay to unlock the collateral. Lista's documentation describes lisUSD as collateral backed and soft-pegged to the US dollar. The FAQ says it is "fully over-collateralized by crypto assets such as BNB, ETH, slisBNB and wBETH". The minimum draw is 15 lisUSD. The borrow interest rate is a fixed number set through Lista governance.
That puts lisUSD in the crypto-backed category. Its collateral is other crypto assets held in smart contracts, not cash at a bank. The map records 75.16 million lisUSD in supply, all of it on BNB Chain, and holds no price and no holder count for the token.
Sources: Lista Docs, lisUSD overview, Lista Docs, FAQ (backing, peg, audits, risks), Lista Docs, Borrow lisUSD (minimum draw), Lista Docs, CDP mechanics (collateral ratio, borrow rate)
What the CDP holds
Lista's collateral page describes the accepted range as L1 tokens, LSTs and LRTs, naming ETH and BNB as the classic cases. The FAQ names BNB, ETH, slisBNB and wBETH. Since 22 September 2025 the CDP Zone also accepts PancakeSwap LP tokens, so a liquidity provider can borrow lisUSD while the position keeps earning pool fees. The developer docs define the collateral ratio as total lisUSD minted divided by total collateral value.
The second route in
A Peg Stability Module mints lisUSD from USDT or USDC at a 1:1 ratio. Float that enters this way is backed by a centralized stablecoin rather than by overcollateralized crypto. Lista's documentation put the cap on the module at 5 million lisUSD at launch.
What is not published
Lista publishes no reserve attestation and no accountant's opinion on backing. Its security page lists code audits by module, firm and month, including a HashDit review of the Liquidation Vault in July 2026 and Bailsec, CertiK and HashDit reviews of the Collateral Yield Vault in June 2026. Those are smart contract audits, not statements about what collateral stands behind the outstanding supply. The documentation carries no per-asset collateral composition table.
Sources: Lista Docs, FAQ (collateral assets named), Lista Docs, CDP collateral types, Lista Docs, Stable Pool and Price Stability Module, Lista Docs, audit reports index, The Block press release, Lista DAO introduces LP collateral (22 Sep 2025)
Lista's FAQ states that lisUSD may not always be perfectly pegged to the dollar and can deviate in both directions under stressful market conditions. The Peg Stability Module is the tool that pulls it back. Minting lisUSD from USDT or USDC carries a 0% fee at 1:1. Redeeming lisUSD back into those stablecoins costs 2%, is capped at 500,000 lisUSD a day, and is bounded by what the vault holds. Lista's documentation says the zero mint fee is temporary and may increase if lisUSD trades at a premium. The map holds no price for lisUSD, so no peg deviation is measured on this page.
Sources: Lista Docs, FAQ (peg deviation statement), Lista Docs, Stable Pool and Price Stability Module (fees, caps)
Collateral and liquidation
The collateral set is concentrated in BNB and BNB-denominated liquid staking tokens on a single chain. Liquidation runs as a Dutch auction whose starting price carries a 2% buffer and then decreases linearly. The worked example in Lista's docs uses a 66% collateral ratio and a 10% liquidation penalty on the debt, with the penalty fixed by Lista governance. Liquidators also take a flat 5 lisUSD tip for starting an auction.
Oracle and parameter risk
Lista previously drew collateral prices from the Atlas Oracle, Chainlink, RedStone and API3. The docs say collateral assets are gradually transitioning to a Resilient Price Oracle that compares and validates prices across several sources, so during the transition different collateral types sit on different pricing setups. The borrow rate, the liquidation penalty and the module caps are governance parameters. Float minted through the Peg Stability Module carries the redemption risk of the USDT and USDC behind it.
Sources: Lista Docs, loan liquidation (auction, penalty, tip), Lista Docs, multi-oracle and Resilient Price Oracle, Lista Docs, CDP mechanics (governance-set rate)
What is read
The Global Stablecoin Map reads lisUSD at a single contract on BNB Chain, 0x0782b6d8c4551b9760e74c0545a9bcd90bdc41e5, and records 75.16 million tokens in supply there. Lista's CDP documentation is published for BNB Chain, and the map holds no other deployment. No holder count and no price are stored for lisUSD.
What is not read
The map does not read the collateral standing behind the debt. That sits in Lista's vault contracts, and the documentation publishes no per-asset composition of it. The map also does not read the Peg Stability Module balance, so the split between overcollateralized CDP debt and float minted from USDT and USDC is not visible here.
Sources: Lista Docs home (products, lisUSD description), Lista Docs, Collateral Debt Position - lisUSD
Two things. Most lisUSD is borrowed against crypto collateral locked in Lista DAO's CDP vaults, which the FAQ describes as fully over-collateralized by assets such as BNB, ETH, slisBNB and wBETH, with PancakeSwap LP tokens accepted since September 2025. The rest is minted through a Peg Stability Module that swaps USDT or USDC into lisUSD at 1:1, and that portion is backed by a centralized stablecoin.
No. Lista's security page lists smart contract audits by module, firm and month, including HashDit on the Liquidation Vault in July 2026 and Bailsec, CertiK and HashDit on the Collateral Yield Vault in June 2026. Those are code reviews. No accountant's opinion on the collateral behind outstanding lisUSD is published, and the documentation carries no per-asset collateral composition table.
Through the Peg Stability Module and through liquidations. Minting lisUSD from USDT or USDC costs a 0% fee at 1:1, while redeeming back into those stablecoins costs 2% and is capped at 500,000 lisUSD a day. Lista's FAQ states that lisUSD may not always be perfectly pegged and can deviate in both directions under stressful market conditions.
The Global Stablecoin Map reads lisUSD on BNB Chain only, at contract 0x0782b6d8c4551b9760e74c0545a9bcd90bdc41e5, with 75.16 million tokens in supply. Lista's CDP documentation is published for BNB Chain.
0x0782b6d8…0bdc41e5Explorer ↗Supply on this page is read from these contracts. Addresses are verified by DIA against the issuer’s own published documentation.
0x0782b6d8…0bdc41e5mint(address,uint256)eip1967-transparentRead 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.