Troves
Troves is a yield aggregator on Starknet that moves deposits across other protocols within a chosen strategy. It held about $4.3M in TVL at the 2026-08-14 survey, below the size floor, so we do not open an individual review until it clears that floor. Even at scale, it would face our standing objection to delegated allocation, since routing money across venues is the service we charge for. At this size, an advised book of $1M to $8M from one practice becomes the exit crush.
- TVL sustained above the retired TVL threshold for 30 days
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
Applicability to the surveyed record
Troves documents pooled Starknet vaults that automate yield strategies for depositors. Contributors design and maintain the strategies, which may move assets among lending markets, DEX positions, staking pools, borrowing, farming, and hedges. Depositors hand allocation and rebalancing to those contributors instead of choosing each underlying venue.
Current observation and perimeter
The DefiLlama protocol API read on 2026-08-15 continued to classify Troves as Yield, reported only Starknet, and showed approximately $4.35M TVL. Current Troves documentation and its published master, access-control, timelock, and strategy-contract references confirm that the vault system remains live and far below the shared v1 size floor.
Control and exit applicability
Strategy contributors control allocation rules, and newer vaults use role-based access control with a timelocked super-admin. The underlying protocol, leverage, LP, and liquidation risks vary by strategy. Troves offers on-chain strategy withdrawals, but the actual exit depends on unwinding the underlying positions and may include DEX spread, borrow cost, or pool liquidity instead of a guaranteed par redemption.
Why the class rule decides
The shared v1 below-materiality dossier is the immediate basis because Troves remains below the size floor, so we do not open an individual review until it clears that floor. Delegated allocation would remain a separate basic objection if it scaled. Reopen after DefiLlama TVL stays above the size floor for 30 consecutive days, then review each vault and allocation mandate, contributor and admin powers, timelock, underlying protocols, leverage and LP exposure, audits and incidents, executable withdrawals, stressed unwind, and named direct alternatives.
Research status
This is a capacity-unproven record for Troves, not a quality rejection or approval. Reported TVL says how big the venue is, not what the client owns, who can change the rules, or how a position exits at a proposed size. The individual review opens when the protocol clears the size floor.
Sources
The claims above trace to these. Where a number could not be independently verified, the thesis says so.
- Troves — strategies and vaults · primary · accessed 2026-08-15
Supports: pooled vault, delegated strategy, reallocation, underlying protocols, risk management - Troves — withdrawal workflow · primary · accessed 2026-08-15
Supports: strategy withdrawal, Starknet wallet, on-chain settlement - Troves — current contracts and control · primary · accessed 2026-08-15
Supports: mainnet contracts, access control, timelock, strategy contracts - Troves — strategy security and audit status · primary · accessed 2026-08-15
Supports: strategy-specific audits, unaudited warning, vault implementations - DefiLlama — Troves survey record · secondary · accessed 2026-08-15
Supports: current TVL, Starknet perimeter, Yield category, survey observation
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 |
|---|---|---|---|
| Starknet | Approved with limits | Mixed control | validity proofs and a regular exit window constrain control, but permissioned proposers and an instant emergency Security Council remain live dependencies. |