The Resolv USDC Vault curated by Gauntlet is designed to optimize risk-adjusted returns by lending USDC to Resolv collateral markets, ensuring robust risk management and sustainable yield strategies.
There is no overall band for these dimensions to disagree with.
Evidence · Not scored · 3 of 5 components read (45% of the weight)
Point at a risk to read what it rests on.
Which collateral backs what this vault has lent out, and what each one is.
Withdrawals drain these markets in this order on ethereum. Redeemable here is the smaller of this vault's supply and the market's free money, now.
| # | Market | Allocated | Util | Redeemable here | Share of TVL | Others here |
|---|---|---|---|---|---|---|
| 1 | idle / USDC0x54ef…dbc8 | $0.00 | 0.0% | $0.00 | 0.0% | — |
Every daily reading we hold.
How much could leave now, how hard the money is working, and how much of the borrowing behind it sits close to liquidation.
Collateral of every borrower in the 1 markets this vault lends into, by health factor, 2026-11-07. At or below 1.00 can be liquidated now; up to 1.10 is marked.
No market allocation is held for this vault, so there is no tree to draw.
The contract holds 1,030,971.07 USDC, read from the chain by its token. At the price we publish that is $1.03M, against the $1.03M shown above.
Pick or type an amount to weigh it against both: what the venue says could leave now, and the largest single withdrawal anybody has made here.
The contract imposes no notice period and no request step: a redeem that succeeds settles in the transaction that asks for it, and it succeeds only if the vault holds enough to pay at that moment, which is the liquidity reading and a separate question.
There is no queue and no lock-up in the contract.
$0 of this vault's $1,030,738 is not observed as lent, which does not exceed what the vault holds; that is a check that one figure does not contradict the other, not a reconciliation of the two.
Not lent counts money supplied to markets and not borrowed and money in no market we read alike; the capital account above splits the two for the latest reading. Not lent is not what could be withdrawn, which is read separately.
A quoted rate is one input, not a verdict.
It moves only when the strategy earns or loses; deposits do not move it.
Dashed: what the venue advertised, all recorded by us, which we began on 2026-09-19.
Not computed: the share price is not read as a return here, because its share price never moved in our record, so a return of zero here would be a statement about the accounting, not about what a holder earned.
Everything above is reconstructed from public data. A declaration is free, signed from this vault’s own key, and cannot be edited afterwards.Note 28
Six questions, and what we hold for each.
| Source mark | Question | What we hold | Source |
|---|---|---|---|
| What does it hold or lend into? | 0 collaterals read, $0.00 supplied, across 1 marketRead from the vault’s own holdings. Concentration and the assets themselves are below. Its largest single market holds 0% of what anybody has supplied there. | Measured | |
| How much could leave now? | $0.02The venue's reported withdrawable liquidity, not verified as executable: no withdrawal of it was tried, and an ordinary withdrawal by a given holder may get less. Not the same as what is idle. | Measured | |
| Who runs it, and what else have they run? | GauntletA named operator with a record across every vault they run, including the ones that closed. |
Owner, curator and guardian are different parties, so no single one of them can act alone.
Where the vault's allocated capital sat each day from 2026-08-09 to 2026-11-07, as the venue reports it, across 0 destinations. A day's total is what was allocated, not the vault's total assets: cash held idle is not in it.
| Day | Allocated |
|---|---|
| 2026-11-07 | $0.00 |
| 2026-11-06 | $0.00 |
| 2026-11-05 | $0.00 |
| 2026-11-04 | $0.00 |
| 2026-11-03 | $0.00 |
| 2026-11-02 | $0.00 |
| 2026-11-01 | $0.00 |
| 2026-10-31 | $0.00 |
| 2026-10-30 | $0.00 |
| 2026-10-29 | $0.00 |
| 2026-10-28 | $0.00 |
| 2026-10-27 | $0.00 |
| 2026-10-26 | $0.00 |
| 2026-10-25 | $0.00 |
| 2026-10-24 | $0.00 |
| 2026-10-23 | $0.00 |
| 2026-10-22 | $0.00 |
| 2026-10-21 | $0.00 |
| 2026-10-20 | $0.00 |
| 2026-10-19 | $0.00 |
| 2026-10-18 | $0.00 |
| 2026-10-17 | $0.00 |
| 2026-10-16 | $0.00 |
| 2026-10-15 | $0.00 |
| 2026-10-14 | $0.00 |
| 2026-10-13 | $0.00 |
| 2026-10-12 | $0.00 |
| 2026-10-11 | $0.00 |
| 2026-10-10 | $0.00 |
| 2026-10-09 | $0.00 |
| 2026-10-08 | $0.00 |
| 2026-10-07 | $0.00 |
| 2026-10-06 | $0.00 |
| 2026-10-05 | $0.00 |
| 2026-10-04 | $0.00 |
| 2026-10-03 | $0.00 |
| 2026-10-02 | $0.00 |
| 2026-10-01 | $0.00 |
| 2026-09-30 | $0.00 |
| 2026-09-29 | $0.00 |
| 2026-09-28 | $0.00 |
| 2026-09-27 | $0.00 |
| 2026-09-26 | $0.00 |
| 2026-09-25 | $0.00 |
| 2026-09-24 | $0.00 |
| 2026-09-23 | $0.00 |
| 2026-09-22 | $0.00 |
| 2026-09-21 | $0.00 |
| 2026-09-20 | $0.00 |
| 2026-09-19 | $0.00 |
| 2026-09-18 | $0.00 |
| 2026-09-17 | $0.00 |
| 2026-09-16 | $0.00 |
| 2026-09-15 | $0.00 |
| 2026-09-14 | $0.00 |
| 2026-09-13 | $0.00 |
| 2026-09-12 | $0.00 |
| 2026-09-11 | $0.00 |
| 2026-09-10 | $0.00 |
| 2026-09-09 | $0.00 |
| 2026-09-08 | $0.00 |
| 2026-09-07 | $0.00 |
| 2026-09-06 | $0.00 |
| 2026-09-05 | $0.00 |
| 2026-09-04 | $0.00 |
| 2026-09-03 | $0.00 |
| 2026-09-02 | $0.00 |
| 2026-09-01 | $0.00 |
| 2026-08-31 | $0.00 |
| 2026-08-30 | $0.00 |
| 2026-08-29 | $0.00 |
| 2026-08-28 | $0.00 |
| 2026-08-27 | $0.00 |
| 2026-08-26 | $0.00 |
| 2026-08-25 | $0.00 |
| 2026-08-24 | $0.00 |
| 2026-08-23 | $0.00 |
| 2026-08-22 | $0.00 |
| 2026-08-21 | $0.00 |
| 2026-08-20 | $0.00 |
| 2026-08-19 | $0.00 |
| 2026-08-18 | $0.00 |
| 2026-08-17 | $0.00 |
| 2026-08-16 | $0.00 |
| 2026-08-15 | $0.00 |
| 2026-08-14 | $0.00 |
| 2026-08-13 | $0.00 |
| 2026-08-12 | $0.00 |
| 2026-08-11 | $0.00 |
| 2026-08-10 | $0.00 |
| 2026-08-09 | $0.00 |
Read over 30 days and no asset movement could be attributed to the manager. That is a reading, not an absence of one, every transfer in the window travelled with a deposit or a withdrawal.
Locked here: every depositor we read with their share of the vault, the largest single wallet, and the ledger of each deposit and withdrawal. A vault that is eighty per cent one depositor is a vault whose price can be reset by a single withdrawal, and whose headline TVL says almost nothing about whether anyone else believes in it.
See what unlocksAlready a customer? Sign inWhat this page cannot show yet, and why.
| Risk | Reads | In the band | From |
|---|---|---|---|
| Marketlimited scope: past share-price falls, markets shared with other vaults and, where the vault borrows, distance to liquidation; excludes collateral and borrower credit risk | Not read | Yes | nothing fed it |
| Liquidity | Severe | Yes | exit |
| Depositor concentration | Low | Yes | concentration |
| Operatinglimited scope: continuity of the observed record; not a review of operations | Low | Yes | consistency |
| Controller | Low | No | who may move the money |
| Evidence | Not scored | No | 3 of 5 risk-band components read (45% of the weight) |
The levels come from this vault’s own risk components and controller reading. The bars draw them; they are not a second calculation, and there is deliberately no overall figure.
That is our coverage, not a finding.
Input: at least effectively none of it could be withdrawn at the last reading: uninvested cash $0 over capital $1,030,743, a floor on what could leave; the venue's own withdrawable figure is the same $0, so the two readings agree. The reading 1.00 is one less that share over 25%: a quarter or more free reads 0, nothing free reads 1. The overall band weighs every component together instead, so it can read better than this and is not in conflict with it: a dimension says how bad its worst reading is, the band says what the whole weighs.
Low observed risk is not zero risk. It measures how much of the vault its largest depositor holds, not how much the vault lends into one market; that is the allocation table. Input: largest wallet holds 43%, by the address's position; addresses are not merged by who owns them, and whether the largest is a person, another vault or a custodian is not established. The reading 0.23 is that share less 25%, over 75%: a quarter or less reads 0, the whole vault 1. The overall band weighs every component together instead, so it can read better than this and is not in conflict with it: a dimension says how bad its worst reading is, the band says what the whole weighs.
Low observed risk is not zero risk. The overall band weighs every component together instead, so it can read better than this and is not in conflict with it: a dimension says how bad its worst reading is, the band says what the whole weighs.
Not established: whether its signers are controlled by different people, and whether another role (curator, allocator, guardian) can act alone within its own permissions. ASPERN rule: an owner needing several signatures reads low. This is not part of the overall band, so it neither raised nor lowered it.
By weight, 37.5 of the 82.5 points that apply were read, which is 45% of the component weight the band could draw on (a different denominator: components are not equally weighted); the rest of the 100 is the weight of what does not apply. This is a statement about our coverage and carries no level of its own, because how much we could read is not a risk the vault runs.
Every deposit and withdrawal drawn over the vault's value, the buckets of money in and out, the wallets that moved it and how big a whale is here.
See what unlocksAlready a customer? Sign inFigures computed from the share price read from the vault contract as we went: 2026-07-19 to 2026-11-06, 572 observations. 30-day window from 2026-10-07, 90-day window from 2026-08-08. Readings from the share price read from the contract at past blocks, reconstructed afterwards (29) exist and are not mixed in: one series, one source.
These are the same seven fields in the same order for every vault, so a high rate and a high rate nobody can withdraw from do not look alike.
| Measured |
| What does it depend on? | Morpho on EthereumThe venue and the chain are known; what the strategy routes into underneath them has not been read. | Declared |
| Who can change it, and how fast? | multisig · 72h vault timelock · a guardianowner, curator and guardian are at different addresses | Measured |
| How much of the above was measured? | 0 of 5 not measuredCounted from the rows above rather than asserted. Every figure on this page carries when it was read and what it was read from; the gaps are listed on /reconciliation with their size. | Measured |
This is not a score and there is no letter at the end of it: the answers are different kinds of thing and compressing them into one number would hide exactly the part a reader needs. Where we have nothing, the row says so.
The mark says where an answer came from, never whether it is good: a filled circle is a reading we made, a half circle an inference from readings we hold, quotation marks what the venue or operator states, and a dashed ring means we did not read it rather than that there is nothing to read.
Nothing here is a rating, a recommendation, or a statement that this vault is safe.
These fields are empty because nobody has attested them, not because we failed to find them.
An operator who registers gets a record that provably cannot be edited after the fact, and a grade no unregistered strategy can reach.
2 changes since 2026-08-24.
The most recent was 2026-09-01: the curator was set to 0x9e33…0585. Each is one public transaction that no venue announced. Anything before 2026-08-24 predates this platform holding control state and is not reconstructed.