The contract holds 1,111,739.96 USDC, read from the chain by its token. At the price we publish that is $1.11M, against the $1.11M shown above.
Over 112 daily readings it has ranged from 3.02% to 8.74%, averaging 3.47%. The tile above shows today’s quote alone.
The published ratio divides the realised rate by the rate this vault quotes TODAY.
Over 112 of the 263 days the return covers we hold its own quotes, it advertised between 3.02% and 8.74%, averaging 3.47%, and today's quote is an ordinary one for this vault. Against the average it quoted, the realised rate is 105.30% of it. We hold no quote for the rest of the window, so this says what the venue was advertising while we watched and not across the whole return. 45 of those days we recorded ourselves and 67 come from the venue's own published history, which is the same fact read later rather than a different one.
We derive 0.0% of this vault as withdrawable and its own accounting says 100.0%. The venue claims more could leave than we can account for, which is the direction that needs their word rather than ours.
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 ring marks the largest single withdrawal in the last 30 days, $48.2k.
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,111,356 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. The two figures were read 19 minutes apart, not together, which is enough on its own to move a figure this size.
Observed configuration: an ordinary withdrawal pays from the idle balance and what the liquidity adapter can pull back. At block 26327481 the vault's idle balance was 0.00% of its assets, a ratio of the two in the token's own units. Applied to the capital figure in this report that would be about $0; that is an illustration, not an idle balance observed at that size. Money in its one adapter is subject to a penalty of 0% on a forced deallocation. Alternative routes, in general: a forced deallocation (anyone may call it) moves assets from an adapter back to the idle balance, and needs free liquidity in the market behind that adapter; where there is none, a potential route is an in-kind exit, in which the depositor first supplies to that market themselves (with their own funds or a flash loan) in the same transaction, then forces the deallocation and withdraws, and ends up holding a supply position in that market, in the vault's asset, which can be withdrawn only when that market has free liquidity, rather than the asset itself. Executed on this vault: neither. Both are potential routes; that they work for this vault's adapters, and what each adapter's own code allows, is not verified.
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, 45 recorded by us since 2026-09-19 and 67 from the venue’s own published history.
$10.0k would be $10.1k , a gain of $87.10, 0.9% over 89 days.
And you could not take it out today. Effectively none of this vault was withdrawable at the last reading, so the figure above is what your shares are worth on paper rather than what you could realise.
Computed from the price of one share, so another depositor arriving is never counted as this strategy’s performance. Fees the venue charges inside the share price are included; anything charged outside it is not. It says what this vault did between two dates and nothing whatever about what it will do next.
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. 1 of 6 is not measured for this vault.
| Source mark | Question | What we hold | Source |
|---|---|---|---|
| What does it hold or lend into? | 0 collaterals read, $0.00 suppliedRead from the vault’s own holdings. Concentration and the assets themselves are below. | Measured | |
| How much could leave now? | $0.00What the contract will pay out now, read from it. Not the same as what is idle. | Measured | |
| Who runs it, and what else have they run? | —No operator identified and no evidence of automation either way. | Not measured | |
the owner is a single externally-owned account, not a multisig
The owner is a single key rather than a contract, so there is no multisig or timelock behind it.
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.
Severe liquidity risk on this vault, against an overall band of moderate, and 1 further dimension also worse than it.
One of those is not part of the band at all, so no amount of reading the band would have surfaced it.
Evidence · Not scored · 4 of 5 components read (76% of the weight)
Point at a risk to read what it rests on.
| 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 | Low | Yes | drawdown |
| Liquidity | Severeworse than the band | Yes | exit |
| Depositor concentration | Low | Yes | concentration |
| Operatinglimited scope: continuity of the observed record; not a review of operations | Low | Yes | consistency |
| Controller | Highworse than the band | No | who may move the money |
| Evidence | Not scored | No | 4 of 5 components read (76% 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.
Low observed risk is not zero risk. Market here is two observed readings: the worst fall in the vault's past share price and how much of its lending shares a market with other vaults we track. It does not assess the collateral, the borrowers' ability to repay, a concentration in one market (read under where the capital rests), or whether withdrawals hold under stress. 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.
Input: at least effectively none of it could be withdrawn at the last reading: uninvested cash $0 over capital $1,111,356, a floor on what could leave, and the venue publishes no exit figure to read instead. 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 21%, 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.00 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.
Of the curator's powers, read one by one: Each of the curator's 15 timelocked functions was read from the contract at block 26,327,481: its delay, and whether it has been abdicated. A gate that can lock depositors out can be set at once: setSendSharesGate, setReceiveAssetsGate, setReceiveSharesGate. Funds can be pointed somewhere new at once: addAdapter, increaseAbsoluteCap, increaseRelativeCap. Fees can change at once, within the contract's ceilings: setPerformanceFee, setManagementFee, setForceDeallocatePenalty. Allocators move funds between destinations already added, within the caps, at once, as the contract intends; who they are was not checked. The owner names the curator and the sentinels, at once; this contract gives it no function that moves funds or sets a gate, a cap or a fee itself, and a new curator's changes wait the same delays. This is not part of the overall band: a vault reading low can read high here.
By weight, 62.5 of the 82.5 points that apply were read, which is 76% 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.
Figures computed from the share price read from the vault contract as we went: 2026-03-30 to 2026-11-02, 243 observations. 30-day window from 2026-10-03, 90-day window from 2026-08-04. Readings from Morpho’s own daily record of the vault, reconstructed afterwards (1,020) and the share price read from the contract at past blocks, reconstructed afterwards (52) 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.
| What does it depend on? |
| Morpho Vaults V2 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? | eoathe owner is a single externally-owned account, not a multisig | Measured |
| How much of the above was measured? | 2 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.
We have watched who controls this vault since 2026-09-19 and nothing we record has moved in that window.
That is not the same as a vault that has never changed hands: anything before 2026-09-19 predates this platform holding control state at all, and we do not reconstruct it from history.