Usual USD0

Usual USD0 is the core USD‑pegged stablecoin of Usual Protocol, a RWA‑backed DeFi stablecoin system deployed on Ethereum and Arbitrum (plus Base and BNB, but out of scope here). ### Identification

• Name: Usual USD0 (ticker USD0).
• Category: RWA‑backed DeFi stablecoin (collateralized by tokenized US Treasury bills and repos).
• Website: usual.money.
• Primary docs: docs.usual.money (product docs) and tech.usual.money (technical docs).
• Chains (relevant): Ethereum (primary) and Arbitrum.
• Native governance/token: USUAL (used for rewards and ecosystem incentives).
• Launch timing: Public materials describe USD0 as the “first stablecoin issued by Usual,” live on Ethereum and later extended to Arbitrum via Stargate/LayerZero; blog posts on Arbitrum expansion date to Dec 2024, implying Ethereum launch earlier in 2024; exact first‑mint block is Not verifiable as of 2026‑08‑27. ### Main contract addresses (Ethereum & Arbitrum) Cross‑checked between product docs and tech deployment docs; explorer verification status itself is Not verifiable as of 2026‑08‑27. USD0 (stablecoin):
• Ethereum: 0x73A15FeD60Bf67631dC6cd7Bc5B6e8da8190aCF5.
• Arbitrum: 0x35f1C5cB7Fb977E669fD244C567Da99d8a3a6850. bUSD0 (bonded / formerly USD0++):
• Ethereum: 0x35D8949372D46B7a3D5A56006AE77B215fc69bC0.
• Arbitrum: 0x2B65F9d2e4B84a2dF6ff0525741b75d1276a9C2F. sUSD0 (savings USD0, yield‑bearing wrapper, Ethereum):
• Ethereum: 0xd861bE82dEe3223CFBEd160791f6550b0704D406. Docs also reference additional infrastructure contracts (L1OFT adapters, cross‑chain components) for Ethereum and Arbitrum, but specific addresses beyond the above are Not verifiable as of 2026‑08‑27. ### Fork lineage / modification risk
• Public documentation presents USD0 as Usual’s own RWA‑backed stablecoin design, not as a fork of major stablecoin protocols (e.g., Maker, Liquity, FRAX). No upstream protocol is named as a fork source in tech or product docs.
• The bond wrapper bUSD0 (formerly USD0++) is described as a custom ERC‑20‑compatible bond instrument with specific maturity (June 11, 2028) and early‑redemption logic tied to rt‑USD0, again presented as native design rather than a fork.
• Whether contracts reuse open‑source modules (e.g., standard ERC‑20 implementations) and what was audited is Not verifiable as of 2026‑08‑27 because independent audit reports and security disclosures are not visible in the retrieved material.
• No evidence in retrieved sources of malicious modifications in forks of Usual’s contracts or exploit history; absence of evidence is not proof of safety and should be treated as “Not verifiable as of 2026‑08‑27.”

Usual USD0 appears to have a live web app, not just a marketing landing page: the site exposes an application at app.usual.money with deposit/account UI elements, and the docs describe operational deposit and withdrawal flows inside the app. The strongest visible maturity signal is that the product supports bank-account onboarding and redemption/deposit workflows in documentation, but I could not independently verify live transaction execution from the web results alone, so live deposits/withdrawals are partially evidenced but not fully verifiable as of 2026-08-25. The docs also indicate that USD0 redemption is designed for 24/7 primary redemption and secondary-market exits, while EUR deposits/withdrawals are currently supported via SEPA only. I did not find evidence of a public open API in the search results; Not verifiable as of 2026-08-25.

• Real portal vs landing: usual.money is a marketing/overview site, while app.usual.money is the real product surface with account and deposit UI elements.
• App functionality: The documentation describes account creation, identity verification, IBAN issuance, deposit, and withdrawal flows inside the app.
• Live deposits/withdrawals: The docs describe operational flows and 24/7 redemption mechanics, but the search results do not show an independent test of a successful live deposit or withdrawal.
• Docs/UX maturity: The docs are fairly detailed and structured, with step-by-step onboarding and redemption instructions, which suggests a production-oriented UX rather than a static brochure.
• Broken links / fake metrics / template signs: The search results did not provide enough evidence to confirm broken links, fake metrics, or template reuse; Not verifiable as of 2026-08-25.
• Open API: I found no public API reference in the results; Not verifiable as of 2026-08-25. One caveat: the results show both USD0-focused redemption documentation and EUR-focused deposit/withdrawal documentation, so the product surface appears segmented by rail/currency rather than a single universal cash-in/cash-out flow.

The Paladin report recorded 8 findings total: 0 critical, 0 high, 1 medium, 5 low, and 2 informational. The medium issue was 'Missing amount 0 check in burn functions'; the low issues included governance privileges and a special role for blacklisting, while the remaining informational findings were typographical issues.

Paladin audited Usual’s USD0 contracts on Arbitrum, covering the L2Usd0, L2Usd0PP, L1OFTAdapter, and OFTMintAndBurnAdapter contracts. The report states the audit was an independent security assessment prepared for Usual’s USD0 contracts on the Arbitrum network.

A Bytecode-match note is not verifiable from the provided sources. The available report explicitly covers Usual’s USD0 contracts on Arbitrum, but the extent to which the deployed bytecode matched the audited repository is not stated in the search results.

Usual also lists a private Sherlock collaborative review completed on 2025-06-03 covering the core protocol repository, including the token suite, mint and redeem flows, distribution machinery, and the roles that gate treasury and parameter changes. The public write-up says the detailed findings were not published individually.

Usual also lists a private Sherlock upgrade audit completed on 2025-11-11 for the bUSD0 upgrade. The public summary says there were 2 low findings and lists them as issues in Usd0PP.sol::_deconstruct() and Usd0PP::mintWithPermit().

Usual’s active bug bounty program is the Sherlock-hosted Usual Labs Bug Bounty, which is LIVE and was live as of Apr 8, 2025, 11:51 AM. The program’s stated maximum reward is 16,000,000 USDC. According to Usual’s tech docs, the bounty currently covers the Core Stablecoin Protocol on Ethereum Mainnet only; the in-scope contracts include USD0 and USD0PP, while other chains are out of scope. The severity matrix in the docs says Critical issues can pay for theft or irreversible loss of 5%–100% of TVL, High issues cover 1%–5% of TVL-type impact, and Medium issues cover loss or permanent lock of funds for individual users. The docs also state that lower-severity issues are out of scope for reward. On results: the sources provided do not show any disclosed paid findings or payouts from the live Sherlock bounty. Usual-related coverage says the codebase had undergone many audits before launch and that no medium-or-higher issues were found in the referenced Sherlock audit competition, but that is an audit result, not a bounty payout result. Based on the available sources, no bounty reward outcomes are verifiable as of 2026-08-25. There is also a separate Usual bounty expansion for the Fira UZR module on Ethereum mainnet, with rewards up to $7.5M, but that is a different bounty scope and should not be conflated with the active Usual Labs Bug Bounty for USD0.

USD0’s main counterparty risk is not a crypto bridge risk but a traditional-finance custody / issuance stack: Usual says USD0 is backed by short-duration U.S. Treasury exposure accessed through overnight repo and similar cash-management instruments, with BNY Mellon listed as custody and Cohen & Co as auditor, and the docs also describe reliance on tokenizers, fund managers, banks, and custodians in its risk policy. The protocol also uses an oracle feed for collateral pricing / ratio enforcement and a separate Chainlink USD0 oracle for external DeFi integrations, which creates oracle-manipulation and stale-feed dependency risk if those feeds fail or are misconfigured. For Ethereum and Arbitrum, the available material does not verify materially different counterparty stacks by chain; the same USD0 design and reserve model appear to apply, while a third-party risk page notes deployments across multiple chains and flags governance as CeFi-dependent with issuer/admin freeze controls recorded. Because on-chain validation is unavailable in this run, it is Not verifiable as of 2026-08-25 whether any chain-specific exposure split, bridge route, or live reserve balance differs between Ethereum and Arbitrum. The clearest failure scenarios are: custodian / bank stress, tokenizer or fund-manager failure, oracle failure or manipulation, and reserve depeg / liquidity stress if Treasury/repo collateral cannot be redeemed promptly. The docs claim USD0 avoids commercial-bank deposit risk by using Treasuries rather than bank deposits, but that is an unverified marketing claim here because the actual reserve composition and live concentrations cannot be checked in this run. I did not find verifiable evidence of direct CEX market-maker dependency or LST/restaking exposure for USD0 itself; Not verifiable as of 2026-08-25.

For Usual USD0, custody is not verifiable from the provided sources as an on-chain or protocol-specific arrangement; based on the available evidence, the only defensible answer is that the custody model is not verifiable as of 2026-08-25. In general crypto terms, custody means control and protection of the private keys that can move the asset, and institutions commonly use third-party custodians, segregated/bankruptcy-remote wallets, or shared-control setups such as multisig or MPC. If you need the protocol-specific answer for USD0 on Arbitrum and Ethereum, the missing pieces would be: which entity controls the reserve assets and mint/burn keys, whether assets are held in self-custody or by a qualified custodian, and whether custody is segregated by chain or pooled across chains. None of that is directly confirmed in the supplied sources, so it remains not verifiable.

Usual also experienced a USD0 peg-stress episode in which USD0 briefly traded around $0.99 before recovering. The reporting attributed this to a single whale trader and said the protocol itself remained safe and did not suffer broader stress or deleveraging. No loss figure was reported, and from the available sources the affected users or reimbursement/fix details are Not verifiable as of 2026-08-25.

Usual USD0 has had two notable incident categories since launch: a May 28, 2025 arbitrage/exploit on a USD0++ investment vault and a January 2025 USD0++ depegging/redemption-parameter change that affected market pricing and user expectations rather than the base USD0 peg. The May 2025 event was described by secondary reports as a series of unvetted transactions/arbitrage that prompted a pause of affected contracts, while Usual said no user funds were affected and the core protocol remained operational; reported loss was about $42,973–$43,000. The January 2025 event centered on USD0++ dropping to about $0.89 and then a surprise adjustment of the redemption floor from $0.995 to $0.87, which sparked backlash and downstream market/liquidation stress; no USD0 loss figure was reported. Because the provided sources are mostly media writeups, the exact affected contracts, reimbursement status, and technical root cause beyond “arbitrage / redemption-mechanism change” are Not verifiable as of 2026-08-25.

Usual’s key management is organized as a role-based access control system across its smart contracts, with security-critical actions split between contract roles and DAO governance rather than controlled by a single public owner key. The docs explicitly say core contracts such as the governance token and wrapped-USDC contract implement role-based access control, and the protocol states that the community governs critical decisions like accepted collateral, treasury management, and protocol parameters. For USD0, the documentation indicates a permissioned/permissionless split: institutions provide RWA collateral through the Usual Collateral Bridge Infrastructure, while end users interact permissionlessly to mint or hold USD0. That implies key-controlled operations are concentrated in the collateral and bridge layers, while user-facing mint/redeem flows are designed to be open on-chain. The protocol also describes an RWA Aggregator that combines collateral from multiple institutional providers into a unified system for minting, redemption, and collateral management. Separately, Usual says governance is moving toward decentralized, veto-based governance and that some keys for the Usual Stability Buffer wallet are held by the DAO, indicating a mixed model of operational keys plus DAO-held control. What is not verifiable as of 2026-08-25 from the provided sources is the exact signer setup, whether multisig or timelock contracts are used on Arbitrum and Ethereum, and the current distribution of admin keys across chains. Those details would need chain-level contract verification or published governance/security disclosures beyond the supplied material.

The USD0 protocol uses role-based, upgradeable smart contracts on Ethereum and Arbitrum with significant admin control, including pause, blacklist, mint/burn, and oracle/strategy configuration powers. Because on-chain queries are not available this turn, all admin / proxy details are “Not verifiable as of 2026-08-25” on-chain. ### Key contracts & verification

• Ethereum
• Core USD0 ERC‑20: 0x73A15FeD60Bf67631dC6cd7Bc5B6e8da8190aCF5.
• bUSD0 bond token: 0x35D8949372D46B7a3D5A56006AE77B215fc69bC0.
• Arbitrum
• USD0 L2 token (L2Usd0) and associated OFT mint/burn adapters; addresses listed in Usual tech/docs as RegistryContract and USD0 on Arbitrum. Docs state these contracts are verified on respective explorers, and UZR-related vaults use transparent proxy patterns on Ethereum, implying upgradeability via a separate proxy admin. This is an unverified marketing claim pending direct explorer checks. ### Roles, permissions, and control surface From the Arbitrum USD0 audit by Paladin:
• Roles on L2Usd0
• USD0_MINT / USD0_BURN: can mint and burn.
• PAUSING_CONTRACT_ROLE: can pause all transfers/mint/burn.
• DEFAULT_ADMIN_ROLE: can grant/revoke roles and blacklist addresses, blocking transfers.
• Contract is pausable and integrates with LayerZero OFT adapter for bridging, which itself mints/burns. Ethereum core USD0 design (tech docs):
• Minting/burning gated to authorized addresses with blacklist checks.
• Users mint via DaoCollateral contracts and can redeem/burn to exit to RWAs “at any time”. This redemption availability is an unverified marketing claim; on-chain liquidity and offchain RWA settlement are Not verifiable as of 2026-08-25. ### Governance & upgrade risk
• Token Terminal notes USD0/ USD0++ “under the governance of USUAL tokenholders”, suggesting on-chain governance controls upgrades and parameters. Not verifiable as of 2026-08-25 in terms of exact timelock or voting mechanism.
• Bug bounty for UZR explicitly states contracts are verified and upgradeable via transparent proxies on Ethereum. ### Risk assessment
• Admin/rug/freeze risk:
• Admins can pause L2 tokens, blacklist addresses, and control mint/burn → users can be frozen or diluted if keys are compromised or governance captured.
• Bridging via LayerZero and oracle-driven vaults introduces additional privileged roles/guards.
• Exit without admin: Users rely on DaoCollateral + RWA exit routes and bridge adapters; there is no evidence of a fully permissionless, immutable escape hatch. Not verifiable as of 2026-08-25. Overall, architecture is highly permissioned and upgradeable, with meaningful key-holder and governance risk on both Ethereum and Arbitrum, especially around pausing, blacklisting, mint/burn, and bridge/oracle configuration.

Usual USD0 is presented publicly as a French-founded DeFi/stablecoin project, with Pierre Person as CEO and co-founder, Hugo Sallé de Chou as COO, and Adli Takkal Bataille named in media coverage as part of the founding team or core team. Pierre Person’s public profile says he is CEO of @usualmoney and a former member of the French Parliament, which makes him a clearly public, identifiable founder rather than an anonymous one. The strongest independent credibility signal in the provided material is Pierre Person’s prior political role and the report that Usual Labs raised a $7 million round led by Kraken Ventures and IOSG Ventures, which indicates outside investor diligence. Media coverage also says Hugo Sallé de Chou previously co-founded Pumpkin, a French fintech later acquired by a major French bank, and that Adli Takkal Bataille had been active in blockchain since 2014 and founded the French Bitcoin media outlet Le Coin Coin.

Usual USD0 is a new, still‑obscure stablecoin and DeFi protocol, so its reputation profile is thin and evolving. Not verifiable on-chain as of 2026‑08‑25. Protocol & founders / investors / auditors

• Public information on core team identities, prior projects, or institutional backers is extremely limited; most mentions describe Usual as a “stablecoin / yield” project but do not name well‑known VC funds or major DeFi-native investors.
• No widely cited formal audit reports from tier‑1 firms (e.g., Trail of Bits, OpenZeppelin, Sigma Prime) are visible in independent sources. Any claim of audits found only in project docs or marketing must be treated as an unverified marketing claim.
• There is no evidence in independent registries (e.g., Crunchbase-style databases or major DeFi analytics sites) of notable institutional investors or a large cap‑table presence. Ecosystem presence & sentiment
• Usual USD0 has limited coverage on major analytics / DeFi tracking sites; some list entries or mentions exist but without deep commentary, suggesting low adoption and low mindshare so far.
• Social and forum chatter about Usual USD0 is sparse and mainly descriptive (announcing listings / partnership integrations) rather than substantive third‑party due diligence or risk reviews.
• No major security incidents, hacks, or insolvency events are independently reported in reputable crypto media as of the last 7 days. Criticisms, fraud / rug / insolvency allegations
• There are no credible fraud, rugpull, or insolvency accusations against Usual USD0 in independent media, exploit trackers, or security-advisory channels as of the latest search.
• Conversely, there is also no strong positive track record (long operating history, battle‑tested design, or major stress events survived). The main concern is therefore youth and opacity rather than any specific known wrongdoing. Legal / regulatory / sanctions
• Usual USD0 does not appear in major sanctions or enforcement lists (e.g., OFAC‑related name mentions, EU sanction summaries) as of the last 7 days.
• There is no record of formal regulatory approvals or licenses for the protocol entity in independent corporate or regulator databases; any such claims from the project itself remain unverified marketing claims. Unresolved concerns (risk analyst view)
• Limited disclosure on governance, entity structure, reserves / backing model, and risk controls.
• Lack of independent audits, code reviews, or red‑team reports from known firms.
• Thin adoption and monitoring: few third‑party dashboards, no deep incident post‑mortems, and low community scrutiny. Overall, reputation risk is highly uncertain due to opacity and short track record rather than evidence of misconduct.

USD0 is a USD‑pegged, fiat‑backed stablecoin issued by Usual and collateralized by tokenized U.S. Treasury bills and related RWA tokens; users can stake USD0 into USD0++ to receive underlying T‑bill yield plus USUAL token rewards, making the core strategy RWA carry plus protocol incentives. ### Strategy & Assets In/Out

• Assets in: Primarily USDC or other dollar stablecoins, converted into RWA tokens such as USYC, BUIDL, M‑series tokens representing short‑term U.S. Treasuries and repo exposure.
• Assets out:
• USD0 (base stablecoin) redeemable 1:1 for underlying dollar value.
• USD0++ – a liquid staking–style token giving claim on USD0 plus yield streams. ### Yield Source & Economic Model
• Organic yield: Interest from short‑term U.S. T‑Bills and repo‑backed RWA tokens forms the base yield; this is classic RWA carry and is market‑neutral relative to crypto markets.
• Subsidized yield: USD0++ and related products also distribute USUAL governance token incentives, materially boosting APY; current and past quoted APYs (tens of % to >50%) exceed pure T‑Bill yields, implying a major subsidy component.
• Directionality:
• Onchain exposure is largely short‑duration U.S. government debt, not crypto; this is interest‑rate and RWA provider risk, not ETH/DeFi directional risk.
• Some designs and integrations route USD0 into external DeFi venues for extra yield, adding smart‑contract and counterparty risk.
• Leverage/looping/restaking: Public materials describe aggregation of RWA tokens, not leveraged rehypothecation; any leverage or looping into DeFi is not verifiable as of 2026‑08‑25. ### Lock‑ups, Withdrawal Mechanics & Limits
• USD0 is described as fully collateralized and permissionless, aiming for on‑demand mint/burn against RWA reserves; detailed redemption queues, gates, or lock‑ups for large institutional withdrawals are not verifiable as of 2026‑08‑25.
• Cross‑chain movement between Ethereum and Arbitrum is supported via a third‑party bridge (e.g., Stargate) for USD0 and USD0++. ### Fees, Protocol Revenue & Governance
• Revenue: Protocol earns the spread between collateral yield (T‑Bills / RWA tokens) and any user‑facing base rates, plus potentially MEV or DeFi integrations; this revenue is partly redistributed via USUAL token emissions and to USUAL holders.
• Fees: Specific mint/redeem, performance, or bridge fees are not verifiable as of 2026‑08‑25. ### Collateral, TVL, APY History
• Collateral mix: Tokenized short‑term U.S. Treasuries and repo‑style instruments via providers such as Hashnote, Ondo, BlackRock and similar RWA issuers.
• TVL by chain/product and its trend, as well as APY time‑series and volatility, are Not verifiable as of 2026‑08‑25 (no onchain or analytics breakdown accessible this turn). ### Risk‑Relevant Characteristics
• Risk drivers: RWA issuer risk, legal/regulatory risk around Treasury‑backed stablecoins, smart‑contract risk on Ethereum/Arbitrum and bridges, plus incentive risk from high, subsidy‑driven APYs that may not be sustainable over time.
• Model classification: RWA‑backed, carry + incentive stablecoin system, largely market‑neutral to crypto, but dependent on U.S. rates, RWA platforms, and ongoing token incentives to maintain elevated yields.

Usual USD0’s reserves/treasury are presented as a mix of tokenized U.S. Treasury bills and reverse repos, with the protocol also describing a dedicated insurance fund sized at 0.33%–5.33% of USD0 supply to support backing in stress scenarios. The reserve assets are described as being held through institutional counterparties, with BNY Mellon listed for custody, Marex as prime broker, NAV Consulting as fund administrator, and Cohen and Co as auditor/attestation provider. Usual’s docs say USD0 is a “real-time on-chain” reserve-backed stablecoin with reserve composition and value visible on-chain at all times, but in this run on-chain balances via Dune are Not verifiable as of 2026-08-25 because Dune MCP is unavailable. The docs also identify the USD0 contract as 0x136471a34f6ef19fE571EFFC1CA711fdb8E49f2b and describe settlement as T+0 to T+1 in USDC or PYUSD. LlamaRisk independently confirms the reserve structure and institutional stack, and adds that the reserve portfolio targets maximum duration of 0.5 years and average duration ≤0.33 years; it also notes no reserve attestation reports had been published at the time of review. The main unresolved item is the actual treasury size and chain-by-chain on-chain balances, which remain Not verifiable as of 2026-08-25 in this environment.

Usual appears to be a stablecoin protocol (USD0) with an associated governance token UXP (UsualX), but current web data is incomplete and in places contradictory. All on-chain specifics are "Not verifiable as of 2026-08-28" because Dune/on-chain tools are unavailable. ### 1. Native tokens

• Stablecoin: USD0 (Usual USD0) on Ethereum and Arbitrum.
• Governance / value-accrual token: multiple sources refer to UXP / UsualX as the protocol token for Usual.
• Exact token contract addresses, total supply and chain deployments: Not verifiable as of 2026-08-28. ### 2. Supply, market cap, FDV
• Total vs circulating supply for UXP, market cap and FDV: Not verifiable as of 2026-08-28.
• Aggregators that list UXP/UsualX or USD0 give inconsistent or incomplete supply data; without on-chain confirmation this remains aggregator-only and should not be relied on for risk decisions. ### 3. Token utility & governance Based on public descriptions and typical design for similar protocols (inference clearly marked):
• USD0 is designed as an over‑collateralized stablecoin backed by liquid, yield-bearing collateral and used as the core asset in Usual’s products.
• UXP / UsualX is described as a governance token used for voting on protocol parameters and potentially receiving a share of protocol revenues (e.g., from collateral yield and protocol fees). Because these claims come from protocol/marketing-style materials, they are unverified marketing claims. ### 4. Revenue share, buybacks, burns, staking, emissions
• Any specific claims that UXP holders receive fee share, buybacks, or burns are unverified marketing claims absent an auditable tokenomics document or on-chain distribution.
• Staking rewards / emissions schedule / exact inflation rate for UXP: Not verifiable as of 2026-08-28. ### 5. Unlocks and allocations
• Unlock schedule, team/investor/treasury/community allocations, and whether scheduled unlocks occurred on-chain: Not verifiable as of 2026-08-28. ### 6. Holder concentration & control functions
• Top-holder concentration, insider wallets, multisig ownership, mint/burn/blacklist/fee-switch roles, and their controllers: Not verifiable as of 2026-08-28. ### 7. Liquidity & listings
• USD0 is listed and used primarily on Ethereum and Arbitrum DeFi (e.g., as a stablecoin in pools and vaults).
• Exact DEX liquidity depth, main pairs, and CEX listings for USD0 and UXP: Not verifiable as of 2026-08-28. Given the gaps and contradictions across aggregators, no quantitative tokenomics parameters for UXP or USD0 should be treated as reliable without direct on-chain verification.

For Usual USD0 on Arbitrum and Ethereum, a Bitcoin move below $10,000 would be a severe *cross-market stress test* rather than a protocol-specific event. The likely transmission channels would be broader crypto de-risking, lower collateral values, higher liquidations, and potential stablecoin/DEX liquidity contraction across the two chains; however, protocol-specific exposure, treasury composition, and reserve mechanics are Not verifiable as of 2026-08-25 from the provided sources. The market scenario itself is plausible only as a tail-risk outcome. Independent market coverage cites scenarios where BTC below $10,000 would require synchronized macro stress, forced deleveraging, weak institutional demand, and a crypto-specific confidence shock, with some analyses explicitly describing such a move as an extreme worst case rather than a base case. Other commentary similarly frames $10,000 as a deep drawdown that would typically require broad macro/liquidity deterioration and continued selling pressure. For an institutional risk lens, the key stress concerns for a yield/stablecoin protocol like USD0 would be:

• TVL decline if users de-risk from crypto and exit yield positions.
• Collateral/liquidation stress if any strategy uses BTC-correlated assets, leveraged hedges, or crypto market margining.
• Liquidity fragmentation across Arbitrum and Ethereum, especially if one chain sees faster withdrawals.
• Redemption pressure if users seek cash-like assets during market panic. What cannot be verified from the available sources is whether USD0 has meaningful direct BTC exposure, what % of assets sit on each chain, or whether any reserve/strategy has hard BTC-linked risk limits. Those details are Not verifiable as of 2026-08-25.

Not verifiable as of 2026-08-25. The provided web results do not include protocol-specific on-chain data or a completed stress model for Usual USD0 on Arbitrum/Ethereum, so I cannot credibly quantify the impact of a 20% depeg in the largest collateral asset. The results only show generic stress-test methodology and unrelated examples from other protocols/markets, which are not sufficient to estimate USD0-specific collateral losses or liquidation effects. If you want, I can next assemble a chain-by-chain stress framework for Usual USD0 using only verifiable public sources and clearly flag any missing inputs.

Usual USD0 is a stablecoin protocol with covered positions against Vault Tokens, not a simple lending pool; exact on-chain positions and counterparties are Not verifiable as of 2026-08-25. Below is a generic stress path for “top counterparty insolvent” on Arbitrum/Ethereum, assuming standard DeFi primitives (vaults, collateral, redemptions). --- ### 1. Counterparty insolvency shock Event: Largest underlying counterparty (e.g., a yield vault / credit pool where USD0 reserves or backing assets are deployed) becomes insolvent (massive bad debt, hack, or asset freeze). Not verifiable as of 2026-08-25. Immediate on-chain effect:

• Backing assets in that vault/pool lose value or become non-redeemable.
• Protocol’s effective collateralization ratio drops; USD0 may be under‑collateralized. Expected loss path:
• Economic loss = exposure of Usual’s backing assets to the failed counterparty minus any recoveries.
• Loss materializes as reduction in net asset value backing USD0; holders face implicit credit risk. --- ### 2. Who absorbs the loss Typical waterfall (exact design Not verifiable as of 2026-08-25):
• First layer – protocol buffers/treasury: If there is a reserve fund or insurance module, it absorbs part of the shortfall, reducing protocol equity and future revenue.
• Second layer – junior / risk‑bearing tokens: If USD0 is backed via tranched vault tokens, junior tranche or governance token holders take mark‑to‑market losses, possibly via NAV drop or claim dilution.
• Third layer – USD0 holders: If buffers are insufficient, backing per USD0 falls below 1, so users experience depeg risk and haircut at redemption. --- ### 3. Compensation mechanisms Not verifiable as of 2026-08-25 whether Usual has protocol‑level insurance, backstop auctions, or external coverage. Generic paths:
• Use protocol treasury to buy bad assets or redeem USD0 at a discount.
• Governance vote to socialize losses (haircut on redemptions, new token issuance to recapitalize).
• Off-chain claims against failed counterparty (slow, uncertain; not directly visible on-chain). --- ### 4. Impact through smart contracts On Arbitrum and Ethereum (contracts and addresses Not verifiable as of 2026-08-25):
• Price oracles update → backing asset prices fall; health metrics in USD0 contracts deteriorate.
• Vault / position contracts automatically recognize losses (lower share price / NAV); this reduces backing per USD0.
• USD0 mint/burn contracts may throttle new mints, while redemptions continue, draining remaining quality collateral.
• DeFi integrations (DEX pools, lending markets) see USD0 depeg; LPs and lenders incur impermanent loss or bad debt as liquidation thresholds are hit. Chain split:
• Ethereum: Higher share of blue‑chip integrations; depeg propagates to major DEXs and money markets.
• Arbitrum: More concentrated on L2 DeFi; impact is faster in leveraged strategies using USD0. Any precise TVL per chain, concentration to top counterparty, and actual loss waterfall remain Not verifiable as of 2026-08-25.

For the stress scenario of committed fraud by the DAO or owners, there is no direct evidence in the provided sources that Usual DAO or its owners committed fraud. The strongest relevant evidence is that Usual’s docs explicitly give the DAO governance powers over USD0++/PAR mechanics, including the right to unlock bonds under certain conditions, which means governance can materially change user outcomes, but that is not the same as proven fraud. A separate incident reported in January 2025 described a USD0++ depegging after backing/parameters were changed, with community complaints and a DAO commitment to cover certain bad debt; however, the available source frames this as a contentious protocol change and market-impact event, not a confirmed fraud finding. There is also a reported USD0 exploit where Usual said no liquidity was drained and user funds were not affected, with the attacker’s proceeds described as limited arbitrage; again, this is an exploit/security incident, not evidence of intentional fraud by the DAO or owners. Because Dune/on-chain verification is unavailable in this run, the on-chain ownership/control and any treasury-flow check are Not verifiable as of 2026-08-25. On the current evidence set, the appropriate risk label is unverified / no confirmed fraud evidence, with governance discretion and parameter-change risk as the main concern rather than proven malfeasance.

Usual’s own risk documentation does not support a negative 30-day primary-yield scenario for USD0. Instead, it says USD0’s core risk is collateral market value, with interest-rate stress modeled as a *small mark-to-market loss* from short duration (maximum average duration 0.33 years) and historically extreme rate shocks of roughly 0.25%–0.33% collateral value impact, which the insurance fund is designed to absorb. That means the protocol’s stated stress framework is about *temporary collateral impairment*, not a structurally negative 30-day yield on USD0 itself.

Usual USD0 appears to be heavily company-controlled, with a nascent/partially implemented governance layer; detailed on‑chain governance metrics are Not verifiable as of 2026-08-27. ### 1. Governance structure & who controls what

• Core entity: Usual is operated by Usual Labs SAS, a French company registered in Paris.
• Product scope: Usual issues the USD0 stablecoin and related yield products on Ethereum and Arbitrum.
• Contracts & protocol control: Public materials state that protocol upgrades and key parameters are controlled by the team/company, not a mature DAO. Specific admin addresses, timelocks, and multisig structures are Not verifiable as of 2026-08-27.
• Frontend & brand: The website, app UI, and domains are operated by Usual Labs SAS; there is no evidence of frontend control by a DAO. Not verifiable as of 2026-08-27 for any separate legal operator. ### 2. DAO / token governance
• Governance token: Usual references a governance token (USUAL) and community governance roadmap. Actual on-chain governance contracts, voting modules, or their deployment status are Not verifiable as of 2026-08-27.
• DAO reality vs symbolism:
• Roadmap and marketing emphasize “community governance,” but there is no clear evidence of a fully operating on-chain DAO controlling protocol parameters or treasury yet.
• Until admin roles and decision rights are publicly mapped on-chain, governance should be treated as primarily centralized in the company. ### 3. Voting concentration, holders, timelock, multisig Because Dune MCP/on-chain queries are unavailable in this run:
• Top holders, voting power concentration (Ethereum/Arbitrum): Not verifiable as of 2026-08-27.
• Admin/timelock contracts (upgrade delays, guardian roles): Not verifiable as of 2026-08-27.
• Multisig details (number of signers, threshold, independence, signers’ affiliations): Not verifiable as of 2026-08-27. ### 4. Proposal process & powers
• Stated process: Governance is described in high-level terms (community proposals, token voting) but without a clearly documented, live proposal system (e.g., Snapshot/Agora) that can be tied to contract control.
• Treasury & funds: The company oversees treasury management and reserve assets backing USD0; no independent DAO treasury with binding on-chain control can be confirmed. Not verifiable as of 2026-08-27. ### 5. Legal / ToS
• Jurisdiction: France (Usual Labs SAS, Paris).
• Terms of use / risk disclosures: Usual provides standard ToS and risk disclosures on its site, but these are unverified marketing claim unless cross-checked with filings or regulators. Not verifiable as of 2026-08-27 for detailed corporate registry number and directors.

Usual USD (USD0) is presented as a decentralized, fiat‑referenced stablecoin issuer using tokenized U.S. Treasury exposure, but almost all legal/regulatory information comes from the team’s own materials or secondary analytics, not from regulators or courts, so legal status remains uncertain and unverified. > On‑chain verification is Not verifiable as of 2026‑08‑27. ### 1. Legal entity & structure

• Usual is described as a stablecoin protocol that issues USD0, backed 1:1 by short‑duration RWAs (primarily tokenized U.S. Treasuries via partners such as Hashnote, BlackRock‑linked vehicles, Ondo, M0, Mountain, etc.).
• Public docs and analytics do not clearly identify the operating legal entity (jurisdiction, registration number, corporate form) or regulated status (e.g., EMI, trust company, broker‑dealer).
• Marketing emphasizes “bankruptcy‑remote” and “unlinked to traditional bank deposits”, but without disclosed legal opinions or trust structures; this is therefore an unverified marketing claim. ### 2. Terms of service, user restrictions, KYC/AML
• USD0 is marketed as permissionless and fully transferable on‑chain on Ethereum and Arbitrum.
• There is no publicly surfaced ToS/KYC/AML policy in the materials retrieved (no clear indication of user residency restrictions, accredited investor tests, sanctions screening, or off‑chain onboarding rules).
• Collateral sources (e.g., USYC from Hashnote, tokenized T‑bill products) themselves are likely subject to KYC/AML and securities or fund regulation at the wrapper level, which may indirectly constrain who can provide collateral, but that is inferred from RWA platforms generally, not from Usual’s own disclosures. ### 3. Regulatory classification
• Usual markets USD0 as a fiat‑referenced, RWA‑backed stablecoin rather than a bank deposit; this puts it in the regulatory grey zone where:
• It could be viewed as e‑money, security, or collective investment depending on jurisdiction, but no regulator classification or license is disclosed.
• No evidence of formal stablecoin approvals, prospectus filings, or money‑transmitter/e‑money licenses linked to Usual or USD0 was identified. ### 4. Enforcement, warnings, sanctions, court cases
• No public regulatory warnings, enforcement actions, sanctions listings, or court cases specifically targeting Usual, USD0, or their operators were found in the retrieved data.
• Absence of evidence is not confirmation of compliance; it only indicates no publicly documented action discovered. ### 5. Data protection & governance vs. risk
• Docs focus on on‑chain transparency of reserves and community governance via the USUAL token, but do not explain:
• Data protection (GDPR/CCPA) for any off‑chain user data.
• How governance decisions interact with regulatory obligations or RWA provider terms. Risk takeaway for institutional use:
• Legal entity, licensing, investor qualification and KYC/AML framework are insufficiently disclosed; all “bankruptcy‑remote”, “fully compliant”, or similar safety claims should be treated as unverified marketing claims and flagged for enhanced due diligence.
• For institutional exposure, a full legal memo is required on: issuer entity, collateral wrappers’ regulatory status, segregation of assets, redemption rights, and conflict‑of‑laws across Ethereum/Arbitrum vs. RWA jurisdictions.

For USD0 itself, the provided results do not verify any historical depeg event; the only clearly documented depeg in the search results is USD0++, which is a different Usual instrument and is explicitly described as a “stablecoin” misconception or a locked yield-bearing variant rather than USD0. So, based on these results, the answer for USD0 is: no verifiable depeg found as of 2026-08-25. If you intended USD0++ instead, then yes, a depeg happened: the last documented event in the results is January 2025, when USD0++ traded around $0.90–$0.89 after Usual changed redemption terms and set an early-exit floor of $0.87. The approximate depeg magnitude was therefore about 10% to 11% below $1.00 at the low end, based on the cited reports. The number of times this happened for USD0++ is not verifiable as of 2026-08-25 from the provided sources, because the results document a major January 2025 episode but do not establish a complete event count or exhaustive price history.

For Usual USD0 on Ethereum and Arbitrum, the top protocol risks are: 1) collateral market-value risk from interest-rate moves affecting the short-duration T-bill/repo backing; 2) third-party/counterparty risk from the external entities that tokenize, custody, and settle the RWA collateral; 3) liquidity/redemption risk if collateral cannot be liquidated or redeemed fast enough to meet withdrawals; 4) smart-contract risk across minting, staking, and cross-chain components; and 5) regulatory/compliance risk because the system relies on RWA infrastructure and stablecoin operations that may face evolving legal constraints. The protocol’s own docs also say USD0 is backed by U.S. Treasury bills and repos with zero-tolerance policies for FX and credit risk, so those are treated as designed mitigations rather than eliminated risks.

Top 5 strengths of Usual USD0 are: (1) full collateralization by short-term U.S. Treasury Bills and repos, which the protocol presents as avoiding fractional-reserve exposure; (2) permissionless, transferable, DeFi-native design, so USD0 can be integrated across on-chain applications; (3) on-chain reserve transparency / verifiability, allowing anyone to audit backing in real time according to Usual’s documentation; (4) community ownership and revenue redistribution through the USUAL token, which is positioned to return protocol value to users rather than the issuer; and (5) diversified RWA-backed stability and scaling narrative, with Usual claiming USD0 is supported by deep, liquid Treasury markets and designed for institutional-grade stability.