No dimension we could read is worse than the overall band of severe; 2 were not read (market, evidence), and this comparison says nothing about them.
Evidence · Not scored · 3 of 4 components read (65% of the weight)
Point at a risk to read what it rests on.
We checked 2 addresses: roles and direct holders against the digital currency addresses OFAC SDN published on 2026-11-09; none of them is on it.
Exact address matches against one list (OFAC SDN, version 329a9b9c6e55). 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 contract holds 10,199,726.03 USD1, read from the chain by its token. At the price we publish that is $10.18M, against the $10.18M shown above.
Over 53 daily readings it has ranged from 0.00% to 86.71%, averaging 8.67%. The tile above shows the base rate as the venue last quoted it, alone.
The published ratio divides the realised rate by the base rate this vault quoted when the comparison was last computed (11 November 2026, 09:40 UTC).
Over 53 of the 91 days the return covers we hold its own quotes, it advertised between 0.00% and 86.71%, averaging 8.67%, and that quote is near the BOTTOM of that range, so the published ratio flatters the delivery. Against the average it quoted, the realised rate is 103.04% 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.
This vault deploys into one contract on ethereum, 0x08970a00822a6572e601db4ea77f4eb78a088af4. This contract does not derive what it is worth from what it holds: a multisig at 0x7302b3c92cba579df1f748c50c87cbeb9f136155 POSTS the figure, with the last posting on 2026-11-10. one posting may move it by at most 50 of the contract’s own units, and a posting goes stale after 7 days. Those are limits on the POSTING and not checks on the number: nothing in this contract sets it against anything the chain can confirm. So a flat unit price upstream is not evidence that nothing was earned, and a moving one would not be evidence that anything was. It is the reported book value of a strategy whose holdings we cannot see, and whoever holds that key decides it. The last posting is still inside that period.
100.0% of the capital we can attribute here, or $10.18M, belongs to 1 addresses that also hold an open vault elsewhere, the deepest of them in 4. 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 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.
There is no exit capacity to read here, and that is the contract rather than a gap in our reading. THE CONTRACT HAS NO EXIT CAPACITY TO READ, and that is a fact about the contract rather than a gap in our reading. Asked what a holder who demonstrably holds shares could withdraw, it returned their whole holding converted, with no liquidity cap inside the answer. Asking again returns the same thing and so would any other reader: there is no figure here that measures what the vault could actually pay. The contract it is deployed into does not derive what it is worth from what it holds: a party at 0x7302b3c92cba579df1f748c50c87cbeb9f136155 POSTS the figure, last on 10 November 2026, and a posting stays current for 7 days. Asked what a real holder could withdraw, this vault returned THAT POSTED FIGURE to the unit. What a reader would take for exit capacity here is the number that party entered, converted into shares and back, so publishing it as capacity would be publishing one party’s entry as a measurement of liquidity.
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.
$10.0k would be $10.2k , a gain of $199.73, 2.0% over 89 days.
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.
| Source mark | Question | What we hold | Source |
|---|---|---|---|
| What does it hold or lend into? | CTZIGUSD1The venue names a deposit asset. What the vault actually holds behind it has not been read. | Declared | |
| How much could leave now? | at least under $0.01 idleOnly the unlent part is known, so this is a floor: at least this much can leave. Idle is not withdrawable, and a queue, a cooldown or a cap can stand between them. | Inferred | |
| Who runs it, and what else have they run? | ConcreteA named operator with a record across every vault they run, including the ones that closed. |
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 | Severe | Yes | exit |
| Depositor concentration | Severe | 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 | 3 of 4 risk-band components read (65% 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 $10,179,357, a floor on what could leave — A recorded cash figure of $0, with no measurement time, against $10,179,357 of capital. It does not exceed what the vault holds, which is all this compares; it is not a reading of what is uninvested now. The cash figure carries no reading time, so it is not a measured figure, and it says nothing about what can leave the vault., 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.
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: one wallet holds the whole vault (100%), 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 1.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.
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, 37.5 of the 57.5 points that apply were read, which is 65% 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-08-12 to 2026-11-10, 581 observations. 30-day window from 2026-10-11, 90-day window from 2026-08-12. Readings from the share price read from the contract at past blocks, reconstructed afterwards (11) 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 EthereumAllocations read from the vault, so the protocols it stands on are known. | Measured |
| Who can change it, and how fast? | multisigno guardian, so no party can veto a timelocked change | 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-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.