EVK Vault eUSDC-91

What it holds

How you get out

The contract imposes NO notice period: a redeem settles in the transaction that asks for it. That is not a promise of an instant exit — it is still subject to the vault having the money, which is the liquidity reading and a separate question — but there is no queue, no request step and no lock-up in the contract. This was read by ASKING the contract rather than by reading its code: the vault is a small proxy that dispatches into modules, so there is no interface in its bytecode to lift.

Six risks, read separately

There is no overall figure and there will not be one. The band covers four of these and contains no reading of the controller at all, so a band of `low` beside a controller of `high` is not a contradiction: it is the thing this table exists to show.

What it advertised and what it returned

Who controls it, and whether that has changed

Not read for this vault.

We have watched who controls this vault since 2026-10-12 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-12 predates this platform holding control state at all, and we do not reconstruct it from history.

What we cannot see

• · The realised return is not comparable with the advertised one (venue-silent), so the ratio is not a verdict on the venue's figure.
• · The risk band rests on 61% of its components; the rest could not be measured for this vault.
• · Whether it still takes deposits is not something we could establish.
• · Who can move the money: we have not read this vault’s owner, curator or controller on chain, so nothing here says whether one key could empty it.