Vesper
Vesper pools issue shares against assets routed among modular DeFi strategies. DefiLlama recorded about $64.7M on 2026-08-14. Keepers can change strategy weights and governance can replace modules, so a depositor delegates venue selection, sizing and maintenance. That is the allocation function this advisory program must retain. The rejection is a business-model and control decision, not a claim that Vesper is defective.
- Publishes allocator mandates, curator accountability, and per-vault disclosure that let the delegation be underwritten
Watched nightly: a warning on its venues or files, or a cited document that changes, reopens the memo. The first confirmation is due 2026-11-15.
The research file
Mechanism
A pool accepts one asset and issues pool shares while strategy modules deploy capital into external protocols. Multiple strategies can run concurrently at assigned weights; yield and losses flow back through the pool share. The product is therefore a managed portfolio of protocol claims, not a single lending receipt.
Control and operating evidence
Keepers rebalance among enabled strategies and can update target weights, while governance can add, replace or remove strategies. Vesper documents pause and emergency-withdraw authorities and publishes more than fifty audit reports. Those controls are relevant operating evidence but leave future underlying allocation outside the adviser’s control.
Exit consequences
Withdrawals first use the pool reserve and then unwind strategies in a configured order. A stressed or illiquid underlying can delay or impair the amount returned, and emergency withdrawal can crystallize losses or leave residual assets. The pool share does not remove the oracle, bridge, market and contract risks of its active modules.
Why the class rule decides
Vesper delegates strategy selection, weights and rebalancing to protocol actors without a duty to this client. That duplicates the allocation layer the adviser is paid to own, so the delegated-allocation rule is decisive. Review could reopen for a static, capped pool whose mandate, approved venues, change controls and exit waterfall are underwritable in advance.
Class rule
The delegated allocation class is outside the approved structures, so every protocol in it is not approved until the rule changes. The rule is about the structure, not an adverse finding about this protocol, and it is not a client instruction. The events that would reopen it are listed with the memo.
Sources
The claims above trace to these. Where a number could not be independently verified, the thesis says so.
- Vesper Docs — modular pool architecture · primary · accessed 2026-08-14
Supports: strategy modules, target weights, keeper control, governor emergency authority - Vesper Docs — reserve and withdrawal flow control · primary · accessed 2026-08-14
Supports: withdrawal reserve, strategy withdrawal order, rebalancing, liquidity path - Vesper Docs — published smart-contract audits · primary · accessed 2026-08-14
Supports: audit record, review coverage - DefiLlama — Vesper survey record · secondary · accessed 2026-08-14
Supports: survey TVL, chain distribution, yield-aggregator category
Inherited controls
The research above describes the protocol layer. Every position also inherits the asset it holds and the chain it settles on. The layer with the most administrative power sets the position’s effective control; that describes control, not quality or suitability.
| Chain | Verdict | Control | Control constraint |
|---|---|---|---|
| Ethereum | Approved | No freeze key | No sequencer, no upgrade key, no operator who can be compelled. Rule changes require social consensus. |
| Base | Approved with limits | Mixed control | Coinbase, one regulated US company, operates the only sequencer, and admin keys can upgrade bridge contracts within ~7 days. |
| OP Mainnet | Rejected | Mixed control | Ethereum forced inclusion limits sequencer censorship, but the Foundation and Security Council can co-sign an immediate upgrade before a client can exit. |