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 241 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 result and whether it holds for a current decision, cash against unplaced capital, the largest holder against what could leave, what would change the conclusion, the sanctions screening and the key unknowns: the same readings the API and the PDF carry.
See what unlocksAlready a customer? Sign in0 changes across the 5 daily reports we stored: the assessment, each risk, the withdrawable share, control roles and the tested withdrawal.
See what unlocksAlready a customer? Sign inThe vault accounts for 13,441,206.33 USDE in total assets, read from the chain by its token. At the price we publish that is $13.43M, against the $13.43M shown above.
The unit price does not move, and the contract does not explain it: assets and shares are NOT equal, so this is not the one-share-per-unit design the others have. That is a question about this vault we have not answered, and it is published as one rather than left to look like a vault that earns nothing. AND NONE OF IT IS HELD HERE: every unit has been deployed somewhere else, so whatever is earned happens downstream of this contract and could never show in its share price.
This vault deploys into one contract on berachain, 0x4cf8427e0e640ea0afff1aa0098d28200b0f4fd4. That contract reports exactly as many assets as shares, so ITS unit price is fixed and whatever it earns is paid some way that contract’s share price cannot show.
35.6% of the capital we can attribute here, or $4.78M, belongs to 105 addresses that also hold an open vault elsewhere, the deepest of them in 24. They can leave all of them on the same morning.
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 says redemptions are PAUSED right now, so nothing can leave whatever the liquidity is.
That is the vault’s own switch and it can be turned back.
We have not established what could be taken out. WE PUT THE QUESTION AND ESTABLISHED NOTHING, which is our silence and not the vault refusing. Either the contract did not answer what a holder could withdraw, or we could not read what their shares are worth to compare it against. Unlike a contract that has no such figure, this is work that remains ours to do.
Simulated at block 28937791 (17 November 2026, 04:38 UTC), by eth_call, which runs the vault's own withdraw and sends nothing, on behalf of its largest depositor, whose position was worth $8,341,770: none of the sizes tried would have gone through; $1,000,000 ($1M), $1,343,449 (a tenth of the vault), $8,333,428 (the holder's position, less 0.1% for rounding), $10,000 ($10,000), $100,000 ($100,000), $134,345 (1% of the vault), $671,724 (5% of the vault), $100 (a small amount, $100), $1 (a small amount, $1) would have reverted (custom error 0xd93c0665). The revert names the category of the failure; the deeper cause behind it (which market, why its liquidity was not free) was not verified by this simulation. Downward search at the same block: 4 halving steps from $10,000 ended at $625; every step failed. Smaller amounts tried directly at the same block: $100 and $1; all failed. Amounts below $1 were not tested. One holder at one block, before anybody else takes the same liquidity, and only up to what that holder owns; it says nothing about a later block, and it is the largest depositor’s withdrawal, not yours: your access rights, share and moment can differ.
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 is fixed by construction — the contract mints one share per unit — so the return is not in the price and cannot be read from it.
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 these 6 questions is not measured for this vault. These are evidence questions, not the risk band’s components, which are counted under the six risks.
| Source mark | Question | What we hold | Source |
|---|---|---|---|
| What does it hold or lend into? | CTUSDEThe venue names a deposit asset. What the vault actually holds behind it has not been read. | Declared | |
| How much could leave now? | —No exit reading. This is the figure that decides whether a position can be left, and we do not have it. | Not measured | |
| Who runs it, and what else have they run? |
Scope: the protocol’s code; a curator’s configuration of it is not what these audits cover. Source: DefiLlama audit links, read 16 November 2026, 13:30 UTC.
One party holds more than one of the roles, or nobody can veto a change once its timelock expires.
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 | Not established | 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 62%, 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.49 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.
Observed: the owner is a contract, and not of a shape we recognise (it is neither a Safe-style multisig nor a timelock). We have not traced it to the keys that can make it act, so we have not established whether a single party can act alone. That is no reading, and it is not low. This is not part of the overall band.
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-02-28 to 2026-11-16, 670 observations. 30-day window from 2026-10-17, 90-day window from 2026-08-18. Readings from the share price read from the contract at past blocks, reconstructed afterwards (50) 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? | Concrete on BerachainAllocations read from the vault, so the protocols it stands on are known. | Measured |
| Who can change it, and how fast? | contractno guardian, so no party can veto a timelocked change | Measured |
| How much of the above was measured? | 3 measured · 1 declared · 1 unknownCounted 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-08-24 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-08-24 predates this platform holding control state at all, and we do not reconstruct it from history.