There is no overall band for these dimensions to disagree with.
Evidence · Not scored · 3 of 5 components read (45% of the weight)
Point at a risk to read what it rests on.
The contract holds 182,942,767.53 WLFICX, read from the chain by its token. At the price we publish that is $9.26M, against the $9.27M shown above.
This vault issues one share per unit of the asset and its contract reports exactly as many assets as shares, so the unit price CANNOT move. A flat price here is a fact about the design and not a measurement of performance: any return has to be paid some other way than through the price, and we do not read one. 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. AND ITS OWN HOLDINGS HAVE NOT MOVED AT ALL in 90 days: the same assets and the same shares then as now. That is capital sitting still, which no venue publishes about itself.
This vault deploys into one contract on ethereum, 0x0dbf562b20b633c14ca9db7130b77a9c68f79589. This contract does not derive what it is worth from what it holds: a multisig at 0xc1338e55a765fd98a17d5fd1aed6cf0068c66522 POSTS the figure, with the last posting on 2026-07-30. one posting may move it by at most 200 of the contract’s own units, and a posting is treated as current for 180 days, which is long enough that it is not a freshness control in any practical sense. 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.
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. Every unit of this vault’s capital is deployed away from it, and the contract it is deployed into does not derive what it is worth from what it holds: a party at 0xc1338e55a765fd98a17d5fd1aed6cf0068c66522 POSTS the figure, last on 30 July 2026, and a posting stays current for 180 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.
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? | CTWLFICX-COREThe 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 5 components read (45% 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 $9,288,221, 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.
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 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 82.5 points that apply were read, which is 45% 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-07-31 to 2026-11-02, 298 observations. 30-day window from 2026-10-03, 90-day window from 2026-08-04. Readings from the share price read from the contract at past blocks, reconstructed afterwards (33) 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-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.