Need verifiable oracle data for your project?
DIA provides transparent, customizable price feeds across 50+ chains with fully auditable methodology.
Market cap
DIA price
Total supply
Holders
34.2M BOLDpartial
DIA holds no verified contract address on Arbitrum, Avalanche, Hyperliquid L1. The figure above is a floor.
1,139holders
What the top-10 is
Shares of the same supply as Top-10, from public address labels covering 73.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.
+$2.0Msince Sat, Aug 29 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 BOLD'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.
DIA price
$0.9996
Peg deviation
-4 bps
Peg currency
USD
Launched
Primary use
—
Last snapshot
Sat, Sep 5 UTC
BOLD is the US dollar stablecoin minted by Liquity V2. Borrowers lock ETH or a liquid staking token in a Trove and mint BOLD against it. Liquity describes BOLD as "over-collateralized and backed only by WETH, wstETH, and rETH", with "no real-world assets or custody by centralized players". Each borrower sets their own interest rate on the loan, and that rate decides the order in which loans get redeemed. It is a crypto-backed stablecoin with no fiat leg.
Not the same token as LUSD
LUSD is Liquity V1's stablecoin. Liquity wrote that V1's "fixed one-time origination fee / no interest rates" design "has shown to work reliably in low interest environments", and that in high-rate periods LUSD saw "excessive selling pressure and thus redemptions". V2 replaced the fixed fee with borrower-set rates. The V2 launch post is dated May 19, 2025, and says the release followed "a five-week audit contest with 800+ researchers, multiple re-audits, and weeks of testing".
Sources: Liquity official site, BOLD and Liquity V2 overview, Liquity blog, Liquity V2 is LIVE, Liquity blog, why user-set interest rates (V1 vs V2 and LUSD)
What stands behind each BOLD
Three collateral branches back the supply: WETH, wstETH and rETH. Liquity's docs put maximum LTV at 90.91% on ETH and 83.33% on wstETH and rETH. Opening a Trove needs a minimum debt of 2,000 BOLD. Liquidations carry a 5% penalty.
No reserve attestation exists
Liquity publishes no reserve report and no auditor opinion on backing. There are no off-chain reserves to attest. The collateral is the ETH and the staking tokens held in the branch contracts, and those balances are readable on chain.
The audits cover code
Liquity's technical docs index security reviews from ChainSecurity, Dedaub, Certora, Coinspect and Recon, plus a Cantina competition. Those engagements reviewed smart contracts.
Sources: Liquity Docs, Borrowing and Liquidations (LTV, minimum debt, penalties), Liquity Docs, Technical Docs and Audits (audit index), Liquity Docs, BOLD and Earn (backing and Stability Pools)
The redemption floor
Anyone holding BOLD can redeem it with the protocol for WETH, wstETH and rETH at face value, minus the fee. Liquity's docs say this "creates a price floor around $1". Redemption only pays when BOLD trades under a dollar after fees, so it stops once the price recovers.
The fee
The redemption fee is min(0.5% + baseRate, 100%). baseRate rises with each redemption in proportion to the amount redeemed against total BOLD supply, then decays exponentially with a six-hour half life.
The queue
Inside a branch, Troves are redeemed in ascending order of interest rate. Ties are settled last-in-first-redeemed.
Sources: Liquity Docs, Redemptions and Delegation (fee formula, ordering, price floor)
Oracle failure shuts a branch
Liquity's risk disclosure states that if "Chainlink oracles fail, collateral markets might get priced inaccurately, leading to unfavorable redemptions or excessive or delayed liquidations". An answer that goes stale past its threshold shuts the affected branch. A shut branch keeps using the last recorded price, which the disclosure says can cause "improper liquidations or redemptions".
A shutdown can leave supply unbacked
Liquity discloses that shutting a borrow market can leave part of BOLD unbacked and set off mass redemptions on the branches still running. Its wording: "If this unbacked portion is small, the system can still function with BOLD retaining its peg, assuming no major loss of confidence. However, if confidence erodes, BOLD may depeg." The monorepo README describes urgent redemptions during shutdown, where "1 BOLD redeems for $1.01 worth of collateral". All three collateral types are ETH or ETH staking tokens, and the same assets sit behind many positions in the DeFi vault and lending map.
No manual controls
The disclosure says the protocol can shut markets down algorithmically but has no manual controls. It also lists Stability Pool losses "when the oracle lags behind or an LST flash-crashes within a few blocks".
Sources: Liquity Docs, Risk Disclosure, Liquity V2 monorepo README (shutdown and urgent redemptions)
What is read on chain
The Global Stablecoin Map reads BOLD on Ethereum at 0x6440f144b7e50d6a8439336510312d2f54beb01d, the address held in the map's own registry. The registry supply snapshot is 30,039,742 BOLD, all of it on Ethereum, about $30.05 million at a first-party price of $1.0009. About 1,100 addresses hold the token. Supply, price and holder count here are the map's own readings and carry no external citation. BOLD sits alongside other crypto-backed coins in the stablecoin explorer.
What is not in that figure
The registry chain list for BOLD holds six networks: Ethereum, Optimism, Base, Arbitrum, Avalanche and Hyperliquid. Balances on the non-Ethereum deployments are not inside the supply figure above. Liquity's technical docs carry a per-chain BOLD token address table. The collateral sitting in the Trove and branch contracts is not read here.
Sources: Liquity Docs, Technical Docs and Audits (BOLD token addresses by chain)
Liquity describes BOLD as over-collateralized and backed only by WETH, wstETH and rETH, with no real-world assets and no custody by centralized players. Collateral sits in the protocol's branch contracts and is readable on chain.
No. Liquity publishes no reserve report and no auditor opinion on backing, because there are no off-chain reserves to attest. Its technical docs index smart contract audits from ChainSecurity, Dedaub, Certora, Coinspect and Recon, plus a Cantina competition.
Holders can redeem BOLD with the protocol for WETH, wstETH and rETH at face value, minus a fee of min(0.5% + baseRate, 100%). Liquity's docs say this creates a price floor around $1, since redemption only pays when BOLD trades below a dollar after fees.
No. LUSD is Liquity V1's stablecoin and uses a fixed one-time origination fee with no interest rate. BOLD is Liquity V2 and lets each borrower set their own interest rate, which determines redemption order.
Liquity's risk disclosure states that a branch shutdown can leave part of the BOLD supply unbacked and trigger mass redemptions on the remaining branches, and that BOLD may depeg if confidence erodes. The monorepo README describes urgent redemptions during shutdown at $1.01 of LST collateral per BOLD.
0x03569cc0…4781b01dExplorer ↗0x6440f144…54beb01dExplorer ↗0x03569cc0…4781b01dExplorer ↗Supply on this page is read from these contracts. Addresses are verified by DIA against the issuer’s own published documentation.
0x03569cc0…4781b01dmint(address,uint256)0x6440f144…54beb01dmint(address,uint256)0x03569cc0…4781b01dmint(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.