Guru Network Classic
Rejected venues wait the longest for re-review; a rejection has to earn another look before the scheduled date.
Guru Network Classic is a ten-chain aggregate of assets held across ftm.guru utility, yield and bespoke project contracts, not a single BSC investment product. Its adapter reads USD-denominated totals written into one Universal TVL Finder contract per chain, rather than reconstructing each underlying asset and liability. DefiLlama reported $1.70M on 2026-08-16, primarily Binance, Sonic and MultiVAC, with small approved-chain balances on Arbitrum and others. Rejected-chain was therefore false; the version-1 below-materiality dossier rejects this unresolved aggregate before product-level review.
- TVL sustained above $100M for 30 days
- Separates an exact investable product with reconstructable assets, liabilities, authorities, incidents and a proposed-size withdrawal on an approved chain
The research file
Identity, accounting and class applicability
The official adapter describes Guru Classic as a multi-faceted tool and service suite and reads a `tvl()` number from a TvlGuru contract on each chain. That number is represented as USD value rather than derived by the adapter from named tokens and owners. Because the coverage record mixes contracts and utilities without identifying one investable receipt, no single mechanism class can be defended beyond the materiality screen; below-materiality is narrower and more accurate than treating the whole aggregate as BSC-only.
Corrected chain and product perimeter
The current API attributes value across Echelon, Fantom, Avalanche, MultiVAC, Polygon, Sonic, Metis, Arbitrum, Binance and Kucoin. Binance is the largest component, but nonzero balances on Sonic, MultiVAC, Fantom and Arbitrum disprove the former rejected-chain premise. The record does not establish that all ten components are mutually substitutable or that an advised client can acquire one claim spanning the aggregate.
Control, lifecycle and exit applicability
Guru publishes TvlGuru contracts and raw TVL tooling, but the adapter’s stored USD totals do not expose underlying tokens, pool ownership, privileged roles, liabilities or executable withdrawal depth. A client exit would depend on the exact downstream Guru product and chain, not on the aggregate figure. The absence of adapter-derived holdings is a traceability limitation and means the $1.70M headline cannot be treated as cash available to redeem one position.
Comparison and measurable reopening test
Unlike Yearn or a named ERC-4626 vault, Guru Classic does not present one surveyed receipt with reconstructable assets and exits; unlike a direct chain rejection, part of its perimeter sits on otherwise reviewable chains. Reopen only after the same aggregate remains above $100M for 30 days and the exact proposed product is separated with token, contract, chain, asset, liability, authority, incident and proposed-size withdrawal evidence.
Sources
The claims above trace to these. Where a number could not be independently verified, the thesis says so.
- BscScan — Guru Classic TvlGuru contract · primary · accessed 2026-08-16
Supports: Binance deployment, TvlGuru contract, onchain stored total, contract lifecycle - SonicScan — Guru Classic TvlGuru contract · primary · accessed 2026-08-16
Supports: Sonic deployment, TvlGuru contract, multichain perimeter, contract lifecycle - DefiLlama adapter — Guru Classic TvlGuru reads · secondary · accessed 2026-08-16
Supports: TvlGuru contracts, stored USD totals, ten-chain configuration, methodology - DefiLlama — Guru Network Classic survey record · secondary · accessed 2026-08-16
Supports: $1,703,604 TVL, ten-chain perimeter, Yield category, current lifecycle - Guru Network Docs — official links and identity · primary · accessed 2026-08-16
Supports: official identity boundary, current domains, repositories, separate modern Guru network
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 |
|---|---|---|---|
| Avalanche | Approved · limits | crypto-backed | no party can freeze or seize C-Chain funds, but one vendor writes the only production client and Messari measured over a third of stake hosted on AWS. |
| Polygon PoS | Rejected | hybrid | 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. |
| Arbitrum One | Approved · limits | hybrid | a single sequencer orders >99% of transactions and admin keys can upgrade bridge contracts on a ~7-day timelock. |
| BNB Smart Chain | Rejected | freezable | the validator set concentrates around one company, and the chain has been halted by decision. |