There is no overall band for these dimensions to disagree with.
Evidence · Not scored · 2 of 5 components read (24% of the weight)
Point at a risk to read what it rests on.
We checked 16 addresses: roles and direct holders against the digital currency addresses OFAC SDN published on 2026-11-13; none of them is on it.
Exact address matches against one list (OFAC SDN, version 55badef69280). Not a legal opinion, and no exact match is not a finding that no sanctioned party is involved.
Every daily reading we hold.
The contract holds 1,007,000 USDC, read from the chain by its token. At the price we publish that is $1.01M, against the $1.01M 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.
Getting out is a REQUEST, not a withdrawal: the contract takes an ERC-7540 redeem request and pays it when it settles.
It names no period, so how long settlement takes is the operator’s to decide and we cannot read it. The contract will also tell you where you stand: it answers what of yours is still pending and what has settled and is waiting to be claimed. A liquidity figure does not say how long the request takes. A queue does not remove the liquidity question either: a request is filled only when there is money to fill it, so both readings stand side by side.
The exit is read, and not on this contract. Leaving here is request-and-claim, so the selector that reports withdrawable capacity answers a different question: what a SETTLED request has set aside for one holder, not what the vault could pay. The constraint on getting out is the queue and the wait rather than a capacity figure, which is read under `exitPhases`.
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-30.
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? | HUBCAP-USDCThe venue names a deposit asset. What the vault actually holds behind it has not been read. | Declared | |
| How much could leave now? | $125.04 idle, by request onlyOnly the unlent part is known, and here it is not a door at all: leaving this vault means filing a request and waiting for it to be settled, so this is what a request would be settled from rather than an amount anybody can take today. Redemption here is asynchronous: a request, then a settlement at the manager’s epoch. Confirmed on-chain through ERC-7540. The cash is real and it is not available on demand. | Inferred | |
Scope: the protocol’s code; a curator’s configuration of it is not what these audits cover. Source: DefiLlama audit links, read 15 November 2026, 13:30 UTC.
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.
| 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 | Not read | Yes | nothing fed it |
| Depositor concentration | High | Yes | concentration |
| Operatinglimited scope: continuity of the observed record; not a review of operations | Low | Yes | consistency |
| Controller | High | No | who may move the money |
| Evidence | Not scored | No | 2 of 5 risk-band components read (24% 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.
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 59%, 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.45 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.
What that party may change is set by the venue's contract; if it can redirect funds and nothing delays it, one signature is enough to do so. This is not part of the overall band: a vault reading low can read high here.
By weight, 20 of the 82.5 points that apply were read, which is 24% 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-10-01 to 2026-11-15, 282 observations. 30-day window from 2026-10-16. Readings from 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.
| Who runs it, and what else have they run? |
| LagoonA named operator with a record across every vault they run, including the ones that closed. |
| Measured |
| What does it depend on? | Lagoon 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? | 1 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-30 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-30 predates this platform holding control state at all, and we do not reconstruct it from history.