Harvest Finance
Harvest Finance issues vault shares whose strategies deploy deposits into third-party lending, staking and liquidity venues, while Autopilots dynamically reallocate among Harvest vaults. The DefiLlama protocol API read on 2026-08-15 reported about $15.0M across Base, Ethereum, Arbitrum, Polygon and zkSync Era. The shared v1 delegated-allocation dossier controls because the client inherits the selected venues and strategy changes without retaining the advisor’s direct allocation control; this is not a judgment about Harvest’s implementation quality.
- Offers a product with an immutable advisor-selected venue allowlist, enforceable allocation limits, continuously verifiable per-venue positions, and no manager substitution
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 applicability
Harvest documents vaults that issue transferable fToken shares and deploy the underlying into one or more third-party protocols through predefined strategy contracts. Strategies collect reward tokens, sell them into the farming asset and redeploy them. Autopilots add a further layer that actively reallocates deposits across Harvest vaults under predefined optimization rules, directly establishing delegated venue and strategy selection.
Current observation and look-through
The DefiLlama protocol API read on 2026-08-15 reported approximately $15.0M of Harvest TVL: about $10.7M on Base, $3.7M on Ethereum, $0.5M on Arbitrum, $0.08M on Polygon and a small zkSync Era balance, plus separately categorized FARM staking. Harvest’s current overview still advertises more than 100 strategies spanning lending, staking and liquidity provision. Adapter totals do not reveal a client’s live underlying venue mix.
Control and exit applicability
A vault owner can move underlying funds only into and out of the predefined strategy, and strategy replacement uses a 12-hour timelock. Users burn fTokens to receive proportional underlying, sometimes through a swap that Harvest warns can lose value from market moves; Autopilots state no lockup but may need to exit or reallocate underlying vaults. Timelocks and withdrawal access mitigate control risk without returning venue selection to the advisor.
Why the class rule decides
The shared v1 delegated-allocation dossier controls because Harvest selects or changes the third-party strategy stack that generates the client’s return, and Autopilots explicitly optimize allocation across vaults. Reopen only after a product exposes an immutable advisor-selected allowlist, enforceable allocation limits and continuously verifiable per-venue positions without manager substitution; then review each admitted underlying venue, contracts, incidents, fees, liquidity and stressed exit execution.
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.
- Harvest Docs — current product overview · primary · accessed 2026-08-15
Supports: yield aggregator, third-party venues, automated strategies, supported chains, current product perimeter - Harvest Docs — vault mechanism · primary · accessed 2026-08-15
Supports: fToken shares, third-party strategy, compounding, strategy controls, withdrawal swap risk - Harvest Docs — Autopilots · primary · accessed 2026-08-15
Supports: dynamic allocation, vault selection, optimization rules, no lockup, liquidity screening - Harvest Docs — strategy timelocks · primary · accessed 2026-08-15
Supports: strategy replacement, 12-hour timelock, user opt-out, deployer control - DefiLlama — Harvest Finance survey record · secondary · accessed 2026-08-15
Supports: current TVL, chain distribution, staking breakout, 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 |
|---|---|---|---|
| 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. |
| Ethereum | Approved | No freeze key | No sequencer, no upgrade key, no operator who can be compelled. Rule changes require social consensus. |
| Arbitrum One | Approved with limits | Mixed control | a single sequencer orders >99% of transactions and admin keys can upgrade bridge contracts on a ~7-day timelock. |
| Polygon PoS | Rejected | Mixed control | a public validator set orders transactions, but a 5-of-9 multisig can instantly upgrade staking and canonical bridge contracts, while a 5-of-8 controls custom child tokens. |