Ether.fi Cash Liquid
Rejected venues wait the longest for re-review; a rejection has to earn another look before the scheduled date.
Ether.fi Cash Liquid is rejected under the version-1 delegated-allocation dossier. The Phase 2 survey attributed approximately $134.2M to the Cash Liquid product. Liquid accepts a single deposit, deploys it across a basket of DeFi strategies, automatically rebalances the basket, and compounds the results into the vault share. This is a protocol-specific application of a published class rule, not an unsupported claim that every contract or operator behind Ether.fi Cash Liquid is defective.
- Liquid enforces a client-specific immutable allowlist and per-venue limits matching the Ketju mandate
- Every underlying position and executable withdrawal becomes continuously verifiable and no allocator can add an unapproved venue
The research file
Mechanism and applicability
Liquid accepts a single deposit, deploys it across a basket of DeFi strategies, automatically rebalances the basket, and compounds the results into the vault share. The reviewed deployment therefore satisfies the dossier’s mechanism requirements on its own facts. The Phase 2 survey attributed approximately $134.2M to the Cash Liquid product. A class application records enough protocol evidence to prove applicability while leaving the shared economic argument in the pinned dossier rather than pretending this is a separate flagship review.
Control and incident boundary
Strategy selection, weights, integrations, and rebalancing remain continuing allocator decisions even when the vault contracts and displayed allocations are transparent. Those controls and the available incident record may change operational risk, but they do not remove the property that triggers this disposition. No clean-record claim is used as proof of safety: a young deployment can have little adversarial history, and an established deployment can execute its intended economics without an exploit while still remaining unsuitable for the advised sleeve.
Exit and current measurement
Redemption depends on the vault buffer and the ability of the active underlying strategies to return assets; leverage or liquidation risk can exist inside strategies the client did not select directly. Aggregate TVL is an accounting measure rather than a promise that the exact client position can be unwound at the displayed value. The disposition remains a zero allocation until a stated reopen condition is observed and a new review measures the proposed-size exit instead of inferring it from a dashboard total.
Comparison and decision
Direct positions in approved venues preserve the advisor allowlist and per-venue cap instead of outsourcing the same allocation decision to a changing basket. The comparison is made at the exposure level, not by brand or headline rate. The published dossier is preferable to repeating the same class judgment with slightly different wording for every venue; the protocol-specific sources retained here make the classification reproducible and the reopen criteria observable.
Sources
The claims above trace to these. Where a number could not be independently verified, the thesis says so.
- Ether.fi Help Center — How Liquid works · primary · accessed 2026-08-19
Supports: strategy basket, automatic rebalancing, auto-compounding, strategy risks - DefiLlama — Ether.fi Cash Liquid protocol data · secondary · accessed 2026-08-19
Supports: protocol category, chain perimeter, current TVL
Inherited controls
The verdict above grades the protocol layer. Every position also inherits the asset it holds and the chain it settles on. The least safe layer sets the position’s grade, and the position table names which one that is.
| Chain | Verdict | Grade | Control constraint |
|---|---|---|---|
| OP Mainnet | Rejected | hybrid | Ethereum forced inclusion limits sequencer censorship, but the Foundation and Security Council can co-sign an immediate upgrade before a client can exit. |