There is no overall band for these dimensions to disagree with.
Evidence · Not scored · 1 of 4 components read (21% of the weight)
Point at a risk to read what it rests on.
We checked 162 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 vault accounts for 2,670,795.13 CT in total assets, read from the chain by its token. At the price we publish that is $278.2k, against the $278.2k shown above.
This vault deploys into one contract on ethereum, 0x42cf9791e804df5c216b8d9ead3eaf8196f544ee. Every unit it reports is sitting in the vault as the asset, so there is nothing deployed and no underlying return to look through to. That is a reading of where the capital sits rather than a gap in our reading.
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 0x1f470a217c3eeddea118194a66ff8692ce705d50 POSTS the figure, last on 28 September 2026, and a posting stays current for 356 days.
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-10-01.
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.
| Source mark | Question | What we hold | Source |
|---|---|---|---|
| What does it hold or lend into? | SCTThe venue names a deposit asset. What the vault actually holds behind it has not been read. | Declared | |
| How much could leave now? | at least $1.01M 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. |
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.
22 transactions moved assets on the vault’s own account, across 1 token.
Counted as manager activity because the transaction carried neither a deposit nor a withdrawal. 14 further transfers travelled with somebody’s own money and are not counted here. A transfer is not a trade: this says the contract acted, not that it acted well.
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 | Moderate | Yes | concentration |
| Operatinglimited scope: continuity of the observed record; not a review of operations | Not read | Yes | nothing fed it |
| Controller | High | No | who may move the money |
| Evidence | Not scored | No | 1 of 4 risk-band components read (21% 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 50%, 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.33 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.
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, 12 of the 57.5 points that apply were read, which is 21% 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-02 to 2026-11-15, 276 observations. 30-day window from 2026-10-16. Readings from the share price read from the contract at past blocks, reconstructed afterwards (3) 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? | 3 measured · 1 declared · 1 inferredCounted 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-10-01 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-10-01 predates this platform holding control state at all, and we do not reconstruct it from history.