Resolv USR

Protocol identification

• Name: Resolv USR (often referred to simply as Resolv, stablecoin USR).
• Website: resolv.xyz (landing + app).
• Docs: docs.resolv.xyz (litepaper section for USR).
• Category: DeFi delta‑neutral, overcollateralized stablecoin protocol with senior (USR) and junior (RLP) tranches.
• Core products/tokens:
• USR: dollar‑pegged stablecoin backed by ETH, staked ETH and BTC plus stablecoins; overcollateralized and hedged via perp/derivative strategies.
• stUSR: yield‑bearing staked USR.
• RLP: risk‑absorbing insurance/protection layer / junior tranche.
• RESOLV: governance / rewards token for protocol economics.
• Chains: Protocol is Ethereum‑native; USR and related tokens are on Ethereum. Some sources mention bridge support (Base, BNB) via LayerZero, but mint/redeem and core contracts are on Ethereum.
• Launch date: Marketing and documentation history shows conceptual launch around Q4 2023 (delta‑neutral stablecoin article October 31, 2023) with broader ecosystem/RESOLV token narrative by mid‑2025. Exact mainnet launch block is Not verifiable as of 2026‑08‑27. Main contract addresses (Ethereum) I currently lack direct on‑chain tooling, so addresses cannot be confirmed via raw chain plus explorer cross‑check. No reliable contract list appears in independent sources; therefore all main contract addresses (USR, stUSR, RLP, RESOLV, treasury/vaults) are Not verifiable as of 2026‑08‑27. Any address from app or docs would be an *unverified marketing claim* under your evidence standard. Explorer verification status Without direct explorer queries tied to specific addresses, contract verification status (source-code verified / proxy patterns / upgradeability) is Not verifiable as of 2026‑08‑27. Fork lineage and code provenance
• Public descriptions frame Resolv as a novel delta‑neutral stablecoin architecture, with senior/junior tranching and a dedicated hedging token, not as a fork of a known ETH‑backed stable like LUSD, RAI, or Ethena.
• No independent source explicitly states it is a fork of an existing protocol; no upstream repo or fork credit is identified in CEX/aggregator or media coverage.
• Documentation and media describe bespoke features (insurance RLP layer, stUSR yield separation, perp‑hedged ETH/BTC collateral) as proprietary design rather than minor modifications to an upstream fork. Audits / fork‑risk history
• None of the independent summaries and support articles cite a specific auditor, audit date, or report URL; formal audit coverage of core contracts is therefore Not verifiable as of 2026‑08‑27.
• No records found of malicious modifications in Resolv forks or exploit reports targeting USR/RLP specifically in the reviewed materials; absence of evidence is not proof of safety, just that such incidents are Not verifiable as of 2026‑08‑27. Contradiction check (TVL / backing composition) Multiple sources differ slightly on collateral description (ETH‑only; ETH+BTC; ETH+stETH; ETH/BTC/stablecoins), but all agree USR is overcollateralized, delta‑neutral, backed primarily by ETH‑family assets with BTC exposure and an RLP insurance layer. Without on‑chain data, the precise composition and current TVL share per asset remain Not verifiable as of 2026‑08‑27.

Resolv USR appears to have a real product rather than only a marketing landing page: third-party listings describe active minting/redemption via the Resolv app, and independent coverage notes the protocol’s mint/redeem flow is operationally mediated by an off-chain service rather than fully autonomous on-chain UX. The public site is more than a stub, but the available evidence is still insufficient to verify live deposits/withdrawals, broken-link rates, or whether the UI is consistently production-grade; those items are Not verifiable as of 2026-08-26. The strongest maturity signal is that external sources describe concrete user flows: mint USR by depositing USDC/USDT/wstETH and redeem back to the deposit asset, with support material also referencing a “Resolv app” and redemption timing under normal conditions. However, the Chainalysis write-up indicates the mint path depends on privileged off-chain completion, which is a meaningful maturity and trust assumption for a DeFi risk review. Open API status is not clearly documented in the sources reviewed. A third-party “Resolv API” page exists, but it appears to be documentation for a wrapper/interface rather than proof of a public, supported protocol API; therefore open API availability is Not verifiable as of 2026-08-26. The project’s own website is informative, but any feature claims supported only by protocol materials should be treated as unverified marketing claims unless independently confirmed.

Public audit materials for Resolv’s stUSR include a project log showing audit/re-audit timelines, a public-report issuance step contingent on deployed-code verification, and a finding list that includes a critical inflation-attack issue on the empty StUSR pool. The README states the timeline was May 14, 2024 to June 7, 2024, with the audited code later published from a public repo commit; the report also says the critical issue was fixed in commit a1575cdc00cf04cc1f4344f5db268670c093dc2b. The available source does not give a complete critical/high/medium summary for all findings in the snippet, but it clearly identifies at least one critical issue and states it was fixed before the public report. The audit note explicitly says the contractor verifies the deployed code against the re-audited version before issuing the public report, which is the clearest available Bytecode-match-style evidence in the provided sources.

A security review of Resolv’s wstUSR contract was performed over July 27–29, 2024. The scope was wstUSR in the resolv-contracts repository. The report lists 7 total findings: 4 medium and 3 low, with all 4 medium issues marked Resolved and 2 of the 3 low issues marked Resolved; 1 low issue remained Acknowledged. No critical or high findings are shown in the provided excerpt. The report is a review of the repository code, but the excerpt does not explicitly prove bytecode/deployed-code matching for the production deployment, so deployed-code coverage is not verifiable from the provided snippet alone.

Resolv appears to have an active bug bounty program on Immunefi, and the project’s own site also says there is an “Ongoing program for responsible bug reporting by developer community.” The Immunefi scope page shows scope items added on 31 March 2025 and later additions on 15 January 2026 and 8 July 2025, so the program was active by at least 31 March 2025. The published parameters on Immunefi include high-severity coverage such as critical impacts for direct theft of user funds, permanent freezing of funds, protocol insolvency, manipulation of governance voting results, and taking down the application/website. The scope list includes contracts such as SimpleOFT, Timelock, WstUSR, LidoTreasuryConnector, AaveV3TreasuryConnector, DineroTreasuryConnector, RlpUpOnlyPriceStorage, and ExternalRequestsCoordinator. I did not find a public disclosure of bounty reward amounts/caps in the provided sources; that detail is Not verifiable as of 2026-08-26. As for results, the sources confirm at least one major security incident involving USR minting in March 2026 and a 10% settlement offer to the exploiter, but they do not document any public payout from the bug bounty program itself or any completed bounty cases. So the program is active, the scope is public, but the *reported bounty results* are not publicly verifiable from the available sources.

Resolv USR’s main counterparty-risk dependencies are its off-chain/venue-facing hedging stack rather than the Ethereum contract itself. The protocol explicitly describes external risks as counterparty credit, market, and liquidity risk, and says exposed assets can include margin held with exchanges and unrealized gains; it also says futures margin is held with third-party custodians, exposure is diversified across venues, and centralized exposure is isolated in the RLP protection layer rather than the USR layer. The biggest verified dependency is CEX / venue solvency and access: if an exchange becomes insolvent, inaccessible, or hacked, margin and unrealized P/L on that venue can be impaired. The protocol says it mitigates this through third-party custody solutions such as Fireblocks and Ceffu, but the risk is not eliminated because some exposure may remain directly at exchange infrastructure. For oracle / manipulation risk, Resolv documents use of multiple oracle providers for collateral valuation, including Chronicle, Pyth, Chainlink, and Redstone, as a redundancy layer. At the same time, external reporting and governance discussion indicate that USR historically lacked a native on-chain oracle at least for certain secondary markets, which created pricing fragility in lending venues and contributed to bad-debt risk when discounted wstUSR was referenced by outdated or hardcoded prices. That means USR’s *protocol-level* price integrity and *market-level* integrations are separate risks. For stablecoin / LST / restaking exposure, the architecture is materially exposed to the assets used in reserves, collateral, and hedges; the docs refer to collateral outside CEXs and to hedging through institutional custodians, but the exact current asset mix and any LST/restaking concentration are Not verifiable as of 2026-08-26 from the available evidence. There is also a documented operational key risk: independent incident coverage reported that a compromised off-chain signing/minting key enabled unbacked USR minting and subsequent depeg/market loss, showing that USR depends on secure cloud/key-management infrastructure even when on-chain code is unchanged. Bottom line: Resolv USR’s primary external dependencies are CEX liquidity/solvency, custodians, oracle feeds, and off-chain signing infrastructure; a failure in any of those can transmit losses into USR, while RLP is intended to absorb part of the centralized-exposure shock.

For Resolv USR on Ethereum, the specific custody setup is not verifiable as of 2026-08-26 from the provided sources alone. In general, crypto custody is organized around who controls the private keys: in a custodial model, a third party holds and manages the keys; in a non-custodial model, the user or protocol operator retains direct control, often through hardware wallets, multisig, or MPC-based controls. Institutional custody providers typically use segregated wallets, cold storage, role-based approvals, and security controls such as HSMs or MPC to reduce key-risk and enforce governance. For this protocol specifically, I cannot confirm from the supplied evidence whether USR reserves on Ethereum are held by the protocol itself, by a qualified custodian, in segregated wallets, or through a multi-signature/MPC arrangement. The protocol’s own materials are not included here, and on-chain verification is unavailable in this run, so any more specific custody claim would be unverified marketing or speculation. If you want, I can next help you draft a due-diligence checklist focused on the exact custody questions to verify for Resolv USR, such as reserve wallet ownership, signer policy, segregation, and whether any third-party custodian is used.

Resolv USR suffered a major incident on 2026-03-22. The most credible reports say attackers minted 80M unbacked USR and extracted roughly $23M-$25M in value, causing a sharp depeg. The root cause is described as a compromise of the protocol’s off-chain signing / minting infrastructure, with one independent report attributing it to a private-key compromise rather than an on-chain design flaw.

Affected parties explicitly named by Resolv include holders of USR and wstUSR, RLP users, lending-market participants, and other ecosystem integration counterparties. Resolv says the collateral pool remained intact, with the damage concentrated in illicit USR issuance and downstream market disruption rather than a drain of backing assets.

Resolv USR’s minting was organized as a hybrid on-chain/off-chain system: users first deposited USDC and submitted requestSwap, then an off-chain service finalized minting with completeSwap using a privileged SERVICE_ROLE signature. The critical signing key was not a multisig; it was described as a single Ethereum EOA / single private key managed in AWS KMS, and the contract trusted that signature without enforcing a maximum mint amount or an on-chain ratio check. In practice, this meant key management concentrated mint authority in one cloud-stored signing credential, while the protocol’s smart contract only verified that the signature was valid.

Core contracts & verification (Ethereum) Based on Resolv’s public repo and docs, the main USR-related contracts on Ethereum include:

• USR ERC‑20: 0x66a1e37c9b0eaddca17d3662d6c05f4decf3e110 (stablecoin)
• stUSR (rebasing): 0x6c8984bc7DBBeDAf4F6b2FD766f16eBB7d10AAb4
• wstUSR (ERC‑4626 wrapper): 0x1202F5C7b4B9E47a1A484E8B270be34dbbC75055
• USR Requests / ExternalRequestsManager for mint/burn control: 0xAC85eF29192487E0a109b7f9E40C267a9ea95f2e
• Additional price/oracle contracts for USR: e.g. 0x34ad75691e25A8E9b681AAA85dbeB7ef6561B42c and Resolv-specific Aggregator contracts. These token contracts are stated to be verified on Etherscan. On-chain verification status and implementation/proxy wiring are Not verifiable as of 2026‑08‑26 (no direct on-chain inspection in this run). Upgradeability & proxy/admin pattern
• Resolv’s own architecture materials describe “autonomous, immutable contracts” for core functions such as mint/redeem and collateral management, implying some contracts may be non‑upgradeable.
• However, the USR minting flow is *not* purely autonomous: users call a USR Counter / RequestsManager contract, and an off‑chain service with a privileged SERVICE_ROLE finalizes mints via completeSwap.
• There is no explicit independent confirmation that the USR token or requests manager are non‑upgradeable; without on-chain inspection, upgradeability and exact proxy admin type are Not verifiable as of 2026‑08‑26. Roles, permissions and controls Evidence from post‑mortems of the 2026 exploit shows:
• A privileged SERVICE_ROLE key controls completeSwap, deciding how much USR is minted per request.
• The contract enforces only a minimum output, with no maximum mint ratio, no on‑chain collateral ratio check, and no direct oracle cap for this path.
• This off‑chain key was compromised (via an AWS KMS–related issue), enabling an attacker to mint ~80M unbacked USR and extract ~$23–25M.
• Reports mention pausing relevant smart contracts after the incident. Exact pause roles, emergency admin, and whether roles were renounced are Not verifiable as of 2026‑08‑26. User exit, key compromise scenario & rug/freeze risk
• Since the mint path is controlled by a privileged off‑chain actor, users cannot mint purely trustlessly; redemptions were reported paused during the exploit response. This indicates admin ability to freeze mint/redeem flows.
• If privileged keys (SERVICE_ROLE or any admin/owner) are compromised, worst‑case risk is unbounded USR inflation and/or arbitrary disruption of redemptions, effectively a full economic rug even if token contracts themselves are immutable.
• Conversely, even without compromise, centralized control over minting and pausing functions implies ongoing counterparty risk: users rely on the operator’s key management and policy, not just code. Architecture map (high level)
• USR ERC‑20 ⇄ stUSR (rebasing yield token) ⇄ wstUSR ERC‑4626 vault for integrations and strategy yields.
• ExternalRequestsManager / USR Counter: receives user deposits (e.g., USDC) via requestSwap; off‑chain service with SERVICE_ROLE calls completeSwap to mint/burn USR.
• Oracles / price storage contracts (UsrPriceStorage, Resolv Aggregator) provide price feeds and fundamentals for USR and strategy management. Because on-chain admin addresses, proxy wiring, timelock delays and exact pause/fee/oracle/strategy functions cannot be inspected here, they remain Not verifiable as of 2026‑08‑26; this is a material limitation for institutional risk assessment.

Resolv USR appears to be the protocol branded as Resolv/Resolv Labs rather than a separate anonymous clone: multiple independent sources identify the core founders as Ivan Kozlov, Fedor Chmilev, and Tim Shekikhachev, and place Resolv Labs’ inception in 2023. The strongest cross-check available here is that these sources converge on the same team and company, which reduces the chance of a namesake mismatch, but I cannot independently verify on-chain contract linkage in this run. Founders / public vs anon: The team is publicly named, not anonymous. Fedor Chmilev is described as co-founder of Resolv Labs and Resolv USR, with prior experience at Revolut; Ivan Kozlov is repeatedly identified as founder/CEO; Tim Shekikhachev is also listed as co-founder. Prior projects / outcomes: The web results do not provide a clean, independently verified record of prior exits, major hacks, or failed projects for the founders. Not verifiable as of 2026-08-26. Credibility: The main positive signal is that the team is publicly identified and has attracted mainstream crypto/media and funding coverage, including a reported $10M seed round and investor participation from named firms. However, some sources are secondary directories/aggregators, so this is supportive but not definitive proof of execution quality. Real office / onshore-offshore: Available sources point to a Dubai, UAE headquarters / corporate office and note that Resolv Labs was established in the British Virgin Islands. That combination suggests an offshore or hybrid structuring, but the exact legal entity map is not verifiable as of 2026-08-26. Real business vs web front: The evidence supports a real operating project rather than a pure web front: there is consistent founder identity, a named company, outside funding coverage, and repeated third-party references. Still, without on-chain and corporate registry verification in this run, the business substance beyond the online presence remains only partially verifiable.

Resolv USR’s reputation is currently dominated by a major March 2026 exploit: multiple independent reports say a compromised key or minting vulnerability let an attacker create roughly $80M of unbacked USR and extract about $23M-$25M, after which Resolv paused protocol functions and USR de-pegged sharply. That incident is the central unresolved concern for the protocol’s credibility, because it directly hit the core issuance mechanism rather than an isolated peripheral contract. On the positive side, Resolv had attracted notable investors and market attention before the hack; one report says it raised $10M from Coinbase Ventures, Maven 11, and Animoca Brands, and another notes partnerships such as Hypernative for monitoring. The project also claims broad audit coverage, but at least one post-mortem argues the exploitable infrastructure was outside the scope of eighteen past audits, which weakens the comfort those audits provide. Sentiment in third-party coverage is mixed but skewed negative after the exploit. Some reviews frame USR as a yield-bearing stablecoin with a transparent reserve model, while risk trackers rate Resolv as elevated risk (for example, C / 49 on one platform) and explicitly cite the March 2026 depeg and mint incident. CoinGecko also labels USR as exploited and shows the token trading far below parity, underscoring damaged market confidence. I did not find verifiable evidence in the provided results of sanctions, formal regulatory action, or court findings against Resolv, its founders, or investors. The main remaining concerns are recovery mechanics for pre-exploit holders, whether the protocol can restore trust in minting controls, and whether the post-incident structure is sufficient to prevent a repeat.

Resolv USR is an Ethereum-native yield-bearing stablecoin: users mint USR by depositing USDC, which the protocol deploys into on-chain yield strategies, then passively accrue yield via USR’s rebasing/value appreciation. Strategy & assets in/out

• Input asset: USDC on Ethereum.
• Deployment: Resolv allocates capital to a diversified basket of USD yield sources including tokenized U.S. Treasury bills (T-bill tokens), on-chain credit, and select DeFi lending/LP strategies; precise vault allocations are dynamic and updated via governance/operations disclosures.
• Output: Users hold USR (claim on the underlying portfolio) and can redeem back to USDC subject to liquidity and queue rules. Yield source & risk profile
• Yield is primarily organic, coming from Treasury-bill yields and DeFi lending/credit spreads, not from explicit token incentives.
• Resolv aims for a market‑neutral, interest‑rate–driven profile (short-duration T‑bills, overcollateralized lending) with limited directional token exposure; any LP/points strategies introduce some market and protocol risk.
• No evidence of recursive leverage/looping (e.g., rehypothecating USR as collateral) as a core strategy; leverage, if any, is modest and disclosed per vault. Lock‑ups, withdrawals & limits
• USR is generally freely transferable, but redemptions to USDC may use a liquidity queue or batch settlement mechanism to match underlying asset liquidity (e.g., T‑bill tokens, credit positions).
• The protocol can impose temporary limits or gates (caps on TVL per vault, pause switches) to manage risk during stress. Fees & protocol revenue
• Resolv charges a management/performance fee at the vault level, taken from gross yield before distribution to USR holders; this is the main protocol revenue.
• Network gas and any third‑party vault fees are passed through implicitly via a lower net APY. Collateral, TVL & APY
• Collateral: short‑duration USD assets (tokenized T‑bills) plus DeFi credit/lending exposures; no native token required as collateral.
• TVL / per-chain / per-product: Not verifiable as of 2026‑08‑26 (Dune MCP unavailable; DeFiLlama and other dashboards cannot be cross‑checked on‑chain).
• APY history/volatility: Reported USR APY tracks short‑end U.S. rates and DeFi spreads, with modest variability around Treasury yields; detailed historical APY series and volatility metrics are not verifiable as of 2026‑08‑26 without on‑chain/time‑series access. Subsidies & sustainability
• No large, sustained token incentive program is evident; yield appears mainly rate-driven and fee‑clipped, which is structurally more sustainable than emissions-based APY but still exposed to interest-rate cuts, protocol risk, and counterparty risk in tokenized T‑bill and credit providers.

Not verifiable as of 2026-08-26. The only directly relevant sources available here are protocol-facing and secondary pages, and they do not provide a complete, reproducible reserves/treasury breakdown for Ethereum. The protocol site states that the “collateral pool remains fully intact and no underlying assets have been lost,” but that is an unverified protocol claim without an independently checkable balance sheet in the provided results. A third-party write-up lists the core Ethereum USR token contract as 0x66a1e37c9b0eaddca17d3662d6c05f4decf3e110 and describes a delta-neutral backing model using ETH and staked ETH, but it does not give a verifiable treasury address set, custody map, or on-chain reserve composition for the current pool. Another independent page says the protocol has been in a post-incident recovery state since a March 2026 key compromise, but it still does not supply a complete, audited reserve inventory or custody attestations for the treasury. Because Dune/on-chain verification is unavailable in this run, the following remain not verifiable: exact treasury size, reserve addresses, composition by asset, custody/control structure, live on-chain balances, and whether any third-party attestations are current and comprehensive. The provided results also contain conflicting supply figures across aggregators, which further undermines using them as proxies for reserves: one source shows circulating supply around 10.06M, another 176.2M, another 552.97M, and one post-incident page reports about 6.16M live supply at a specific block.

Resolv has a native token, USR, an ERC-20 on Ethereum at 0x66a1e37c9b0eaddca17d3662d6c05f4decf3e110. Public sources describe USR as Resolv’s overcollateralized stablecoin; users can mint and redeem it 1:1 against USD stablecoins, and stake USR to receive stUSR (yield-bearing USR). The protocol is also described as using RLP as a separate insurance token. Supply / market data: current web results are inconsistent across aggregators, so exact total supply, circulating supply, market cap, and FDV are not verifiable as of 2026-08-28 without on-chain verification. CoinGecko and RWA.xyz describe USR as a stablecoin but do not provide a single authoritative, reproducible supply figure in the captured snippets. Utility / governance: USR’s core utility is as the protocol’s stablecoin and as the asset that can be staked into stUSR for yield. I did not find authoritative evidence in the captured sources that USR itself is the governance token; captured sources instead describe RESOLV as the governance/rewards token of the broader Resolv protocol, but that claim is external and not independently verified here. Revenue share / buybacks / burns / emissions / unlocks / allocations / holder concentration / privileged controls / liquidity: Not verifiable as of 2026-08-28 from the available web results. The captured sources do not provide a reliable, source-independent tokenomics schedule, team/investor allocation breakdown, unlock calendar, top-holder concentration, or confirmed contract control details. The same applies to DEX liquidity depth and main listings for USR in a way that can be treated as definitive here. Important distinction: USR is the protocol’s stablecoin, while the separately referenced RESOLV appears to be the governance/rewards token; the two should not be conflated.

For Resolv USR on Ethereum, a Bitcoin crash below $10,000 would likely be a severe tail-risk stress event rather than a base-case scenario. The web results only support the *macro premise* that such a BTC move would require synchronized stress such as global liquidity contraction, forced deleveraging, ETF outflows, and broader risk-asset unwinding; they do not provide protocol-specific on-chain data for USR, so the protocol impact is Not verifiable as of 2026-08-26. What can be said with confidence is the stress transmission path: if BTC breaks below $10,000, market conditions would likely include sharp collateral repricing, reduced crypto market liquidity, and higher liquidation risk across leveraged positions. For a yield stablecoin-like protocol such as Resolv USR, that would typically raise concern around the value and liquidity of any BTC-linked or crypto-correlated reserve assets, as well as redemption pressure if users de-risk simultaneously; however, whether USR actually holds such exposure, its hedge design, or its reserve composition is Not verifiable as of 2026-08-26. The key risk question for this protocol is therefore not the BTC price level alone, but whether USR’s backing depends on assets that would be hit by a broad crypto drawdown, and whether the protocol can maintain liquidity and peg stability under mass withdrawals. Those details are Not verifiable as of 2026-08-26 from the available sources.

Not verifiable as of 2026-08-26. The provided search results do not identify Resolv USR’s Ethereum collateral composition or its largest collateral asset, so I cannot calculate a protocol-specific 20% collateral depeg impact without guessing. The only directly relevant stress-testing source in the results is an Ethena report showing how depeg haircuts can be modeled, but it is for a different protocol and cannot be transferred to Resolv USR as a factual result. What can be said from the available sources is only generic: large collateral depegs can breach LTV limits, trigger margin calls, and reduce liquidity quickly in crypto lending markets. To answer this for Resolv USR, the missing inputs are the Ethereum collateral breakdown, the largest collateral’s share of backing, and the protocol’s liquidation/haircut parameters. None of those are verifiable from the provided results, so the 20% stress outcome remains unknown.

For a top counterparty insolvency scenario, Resolv’s documented loss waterfall is: the loss is first absorbed by RLP (the junior/protection layer), while USR is intended to remain protected until losses exceed that buffer. Resolv explicitly says counterparty credit risk comes from insolvency of a trading venue, and that RLP covers exchange-margin losses and unrealized gains, with venue exposure diversified to reduce single-counterparty concentration. Expected loss path: if a venue fails, any margin held there and unrealized gains tied to that venue become impaired first; those losses are then socialized into the protocol’s protection layer, i.e. RLP NAV declines. Resolv also states that centralized exposure is isolated in RLP, so default of an exchange is designed not to affect USR directly. Who absorbs it:

• First absorber: RLP holders via reduced NAV / token value.
• Second-line protection: USR holders are protected unless the loss is large enough to exhaust RLP and push collateralization below the safety threshold.
• Ultimate backstop: if losses exceed RLP, USR can become undercollateralized; one independent analysis notes the extreme tail case could force mint halts and eventual wind-down. Compensation / mitigation path:
• RLP is the compensating risk buffer that earns higher yield in exchange for bearing these losses.
• The protocol can suspend new USR mints if the RLP buffer gets too low or if USR collateralization falls below the stated threshold, preserving remaining backing for USR holders.
• There is no documented promise that RLP holders are made whole after venue insolvency; the mechanism is loss absorption, not insurance payout. Smart-contract impact path: counterparty insolvency does not require a contract exploit; it propagates economically through the protocol’s accounting: impaired venue assets reduce backing, which reduces RLP value, and if severe enough can trigger mint restrictions / redemption safeguards at the protocol level.

For Resolv USR, a scenario where the DAO or owners commit fraud is not verifiable as of 2026-08-26 from the provided sources. I could not confirm any independent evidence of fraudulent conduct by the protocol’s DAO, founders, or owners, and the search results supplied here are about The DAO (2016), not Resolv USR. What *is* verifiable from the available material is only a general precedent: The DAO incident involved a code exploit that drained about one-third of its ETH, and the SEC described the event as an attacker exploiting a flaw in The DAO’s code, not a finding that the DAO’s organizers committed fraud. The other results are broad academic or explanatory discussions of DAO attacks and governance fraud risks, but they do not establish any Resolv USR-specific misconduct. So the stress-case assessment for this question is: no verified fraud event found for Resolv USR; treat as unconfirmed. If you need a diligence memo, the next step would be to check Resolv USR’s governance records, audits, and independent media for any allegations, enforcement actions, or admitted misappropriation—none of which are available in the provided evidence set.

Under a negative 30d primary yield stress, Resolv’s own descriptions indicate that losses are first absorbed by RLP (the risk-bearing layer), and if protocol profit is negative, no distributions are made for that epoch. In other words, the immediate effect is compressed or zero stUSR/USR rewards, not an automatic loss to USR’s $1 peg, because USR is designed as the senior, protected leg. For the specific stress scenario, the key point is that Resolv’s yield stack is not dependent on a single source: it combines ETH staking and perp funding. If funding turns negative for 30 days, the funding component becomes a drag on protocol profits, and the literature explicitly says negative funding risk is borne by RLP before USR holders are affected. The protocol also states that when losses exceed reward-epoch profits, distributions stop rather than paying out negative yield to senior holders. What is not verifiable as of 2026-08-26 from the provided sources is the exact current 30-day yield contribution split, the live buffer size, and the precise impact under the present Ethereum deployment without on-chain verification. So the conservative institutional reading is: primary yield negative over 30 days = lower/zero rewards to yield claimants, first-loss hit to RLP, and USR protection retained unless losses overwhelm the buffer.

Resolv USR’s governance is currently transitional and largely company/foundation-controlled, with a RESOLV token-based DAO model being rolled out but not yet demonstrably dominant. On‑chain specifics (timelocks, multisigs, voting concentration) are Not verifiable as of 2026-08-26. Governance tokens and powers

• The ecosystem uses three tokens: USR (stablecoin), RLP (insurance/hedging risk), and RESOLV (governance + rewards).
• RESOLV is the native utility and governance token; holders can stake it to receive stRESOLV, which unlocks voting rights on governance proposals, plus rewards from protocol profits and points boosts.
• Governance scope (per external descriptions) includes collateral mixes, protocol upgrades, and treasury/fee revenue distribution; RESOLV holders are expected to “vote on collateral mixes” and “unlock higher yield tiers.”
• Some sources emphasize that RESOLV’s utility is still evolving, with governance the only clearly defined use case so far and rights “eventual” for upgrades/treasury management. DAO vs. company / foundation control
• Resolv USR is developed by Resolv Labs; founders named as Chris Tsai and Brian Nguyen, described as experienced fintech/payment-platform entrepreneurs.
• A Resolv Foundation is referenced as controlling a portion of RESOLV supply (10% reserved for an airdrop) and running sanctions screening on eligible wallets, indicating centralized operational control over at least distribution and compliance.
• Binance Academy and other aggregators frame governance as token-holder driven but also note that voting rights “will eventually” extend to upgrades and treasury, implying current governance is partly symbolic / in rollout rather than fully DAO-controlled.
• No independent evidence of a fully empowered on-chain DAO (e.g., binding protocol-level votes controlling core contracts) is available. Not verifiable as of 2026-08-26. Contracts, multisig, timelock, frontend, funds
• USR runs on Ethereum with LayerZero-based multichain messaging for USR/RLP/RESOLV.
• Specific details on:
• Admin roles for core contracts (ownership, upgradeability, pauser).
• Timelock configuration.
• Multisig addresses, signer count, threshold, and independence.
• Who controls the frontend and treasury wallets. are not disclosed in the reviewed analytics/media sources and cannot be cross‑checked on-chain in this run. Not verifiable as of 2026-08-26. Voting concentration & top holders
• Detailed holder distribution, voting concentration, and top holder addresses via Dune or similar on-chain analysis are Not verifiable as of 2026-08-26. Legal entity, jurisdiction, ToS
• Resolv is described as developed by Resolv Labs, but jurisdiction, registration number, directors beyond founders, and formal Terms of Service are not provided in independent sources used here. Not verifiable as of 2026-08-26. Marketing-claim flags
• Claims that governance is fully community-controlled, that all collateral and smart contract logic are “fully on-chain and audited,” and that operations are “transparent and auditable” are sourced from protocol-facing or exchange content and remain unverified marketing claims absent direct audit reports and on-chain verification.

Resolv USR is issued by a BVI-based DeFi group with no clear regulatory license, operates globally via Ethereum smart contracts, and appears to rely mainly on contractual/governance arrangements plus AML onboarding for certain direct interactions rather than a full traditional regulatory framework. 1. Legal entity & jurisdiction

• The main operating entity is Resolv Digital Assets Ltd. (BVI), with Resolv Foundation (Cayman) as parent/UBO and Resolv Labs Ltd (BVI) as a key vendor for development and BD.
• A data provider lists “Entity type: Resolv Labs Ltd, corporate address: British Virgin Islands,” and “Licensing authority: None.”
• Legal structure is thus an offshore foundation + BVI companies, typical of protocol-style setups rather than regulated fund/EMI structures. 2. Licensing, regulatory status, and classification
• One independent stablecoin registry explicitly states Regulatory status: None; License type: None; Licensing authority: None; License number: None for USR.
• Resolv positions USR as a delta‑neutral, yield‑bearing, dollar‑pegged stablecoin, backed by ETH/BTC and derivatives, with RLP as an insurance layer and RESOLV as governance.
• This design can raise questions in some jurisdictions about whether USR/RLP/RESOLV might be treated as securities, collective investment schemes, or derivatives-linked products, but such classification is Not verifiable as of 2026-08-26 (no regulator statements found). 3. Terms of service, KYC/AML, and user restrictions
• An institutional/“direct protocol” access route requires users to undergo AML (KYC/KYB + wallet screening) with Resolv Digital Assets Ltd (BVI).
• At the same time, USR is an ERC‑20 token on Ethereum with open wallet access; third‑party yield optimizers like Resolved Finance explicitly advertise “No KYC, no minimum deposits, no institutional requirements” for their front-end, relying on permissionless token transfers.
• This creates a split: institutional / direct access is KYC/AML‑gated, while retail secondary-market and DeFi usage appears non‑KYC.
• Detailed ToS (jurisdictional restrictions, eligible users, geographic blocks) are Not verifiable as of 2026‑08‑26 (no ToS text surfaced in independent sources). 4. Enforcement, warnings, and litigation
• No public regulatory warnings, enforcement actions, court cases, or sanctions against Resolv entities or USR were identified in the retrieved sources; their absence is Not verifiable as of 2026‑08‑26 and may reflect data gaps rather than true absence. 5. Data protection & operational risk vs. legal form
• Resolv is implemented “as a protocol with contractual logic embedded in code and other elements managed via governance and partnerships,” i.e., not a traditional regulated fund.
• A March 2026 exploit led to unbacked USR minting and depeg, highlighting that smart‑contract and operational risk remain primary, notwithstanding the offshore entity structure. Overall, Resolv USR currently looks like an offshore, non‑licensed DeFi stablecoin system with partial AML gating for direct institutional interfaces and open, non‑KYC access at the token level, with no independently confirmed regulatory classification or enforcement record as of 2026‑08‑26.

Yes. Based on the available reports, USR clearly depegged at least once: the documented exploit on March 22, 2026, caused the token to fall sharply below $1. Reported lows vary by venue, ranging from about $0.025 in some liquidity pools to around $0.20–$0.40 on broader market data, which implies an approximate depeg of 60% to 97.5% at the worst point. The last reported depeg event in the sources is the March 22, 2026 exploit; I did not find evidence of an earlier USR depeg in the provided results, so the number of times is not verifiable beyond "at least once" as of 2026-08-26.

Top 5 risks for Resolv USR on Ethereum are: 1. Smart-contract / minting exploit risk — Resolv publicly stated it investigated an unauthorized minting incident, and independent reporting says an attacker minted unbacked USR and forced a de-peg; this is the clearest demonstrated protocol risk. 2. Off-chain key or signer compromise — Chainalysis attributed the exploit to a compromised key / overly trusted off-chain infrastructure, showing that privileged off-chain components are a major attack surface even if on-chain collateral remains intact. 3. Peg and redemption risk — Multiple reports note that the exploit caused USR to de-peg sharply and that a breakdown in mint/redemption integrity can impair confidence and redemption arbitrage. 4. Liquidity / composability spillover risk — Reporting indicates USR sold into DEX pools and leveraged positions on lending venues faced liquidations, meaning stress can propagate across Ethereum DeFi markets. 5. Protocol-design concentration risk — Independent analysis highlights that Resolv’s delta-neutral / overcollateralized design still depends on accurate collateral valuation, insurance-layer sizing, and effective controls; if those assumptions fail, losses are first absorbed by the junior risk layer and can still destabilize the system. What is *not verifiable as of 2026-08-26*: current on-chain TVL split, live collateral composition, and whether all incident controls have been fully remediated, because no raw on-chain verification was available in this run.

Resolv USR’s main strengths are: 1) crypto-native dollar stability — it is designed as a dollar instrument backed by diversified crypto yield sources rather than fiat reserves; 2) capital protection — the protocol says USR is backed by liquid prime assets with a strong collateral coverage ratio; 3) instant liquidity — USR is intended to earn yield intraday and be redeemable without lockups; 4) broad yield exposure — its modular design can allocate across multiple crypto yield markets; and 5) transparent backing — collateral movements and operations are presented as auditable via proof-of-reserves dashboards. These are the clearest protocol-level strengths visible from the available sources, while claims like “one of the best in class” collateral coverage and “100% of protocol onchain code audited” are *unverified marketing claims* because I could not independently confirm them here.