Toros

Rejected venues wait the longest for re-review; a rejection has to earn another look before the scheduled date.

Toros issues ERC-20 wrappers over automated strategies spanning leveraged tokens, options, indices and yield vaults that route capital through lending protocols and liquidity pools. The holder therefore delegates downstream venue selection, position maintenance and rebalancing rather than owning a fixed underlying exposure. That substitution and control risk makes the version-1 delegated-allocation dossier dispositive regardless of the roughly $6.94M observed across six chains on 2026-08-15.

Kill criteria: the events that revoke this verdict
• A named wrapper publishes an immutable adviser-approved venue and asset allowlist, per-position caps, no-substitution rule, deployed authority map, live positions and proposed-size exit evidence
• Any named wrapper passes its additional leverage, derivatives, lending or AMM product-level dossier before allocation

The research file

Mechanism applicability

Toros describes every product as an ERC-20 tokenized strategy with automated on-chain management. Its current catalogue spans long and short leveraged tokens, options strategies, one-times tokens, indices and yield vaults; the yield products can deploy across third-party lending protocols and liquidity pools. A holder owns the wrapper while strategy contracts and operations determine the changing downstream positions, directly meeting the shared v1 delegated-allocation dossier.

Current observation and perimeter

The DefiLlama protocol API read on 2026-08-15 reported approximately $6.94M across Base, Ethereum, Polygon, Hyperliquid L1, Optimism and Arbitrum. That six-chain perimeter replaces the stale three-chain survey statement. Toros’ current documentation continues to present live product families and operating mechanics, supporting an active aggregate strategy record rather than a single retired vault.

Control, loss and exit applicability

Toros documents automated rebalancing for leveraged products and oracle-dependent valuation and trade triggers. Yield vaults add lending-protocol and liquidity-pool dependencies, while options and leveraged products add derivative, debt and liquidation paths. An ERC-20 wrapper may trade in a secondary market, but that does not establish executable redemption of a proposed client allocation or eliminate losses and delays inside the changing strategy.

Why the class rule decides

This aggregate record does not identify one immutable adviser-approved allowlist, position cap or no-substitution rule for every Toros wrapper. The client would therefore delegate both venue selection and ongoing position management. The shared v1 delegated-allocation dossier controls; product-specific leveraged-looping, amm-lp or derivatives tests remain additional constraints rather than reasons to classify the aggregate solely by its current TVL.

Sources

The claims above trace to these. Where a number could not be independently verified, the thesis says so.

• Toros — current strategy catalogue · primary · accessed 2026-08-15
  Supports: ERC-20 strategies, automated management, leveraged tokens, options, yield vaults, lending protocols, liquidity pools
• Toros — protocol operations and rebalancing · primary · accessed 2026-08-15
  Supports: automated rebalancing, leverage maintenance, oracle dependency, operating risks
• Toros — official documentation · primary · accessed 2026-08-15
  Supports: current lifecycle, tokenized strategies, product documentation
• Toros — current protocol site · primary · accessed 2026-08-15
  Supports: current lifecycle, strategy interface, product access
• DefiLlama — Toros survey record · secondary · accessed 2026-08-15
  Supports: current TVL, six-chain perimeter, Yield category, survey observation

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.