Symbiosis
Symbiosis is a cross-chain bridge and swap router that pools liquidity so users can move tokens between EVM and non-EVM networks. At the August 14, 2026 survey it held $6.3M across 40 pools spread over 28 chains, far below the size floor. Liquidity this thin and widely spread means an advised position would be a meaningful share of any single venue. We do not open an individual review until the protocol clears the size floor. One practice advising 100 households moves $1M to $8M based on the same research, and at this size that book would constrain exits. The file reopens if the protocol crosses the floor and holds there.
- 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
Symbiosis documents a cross-chain exchange that routes through Portal and Synthesis mint-burn contracts, MPC-signed relayer messages, and protocol-owned multi-asset AMM Octopools on the Symbiosis Host Chain. LPs supply assets to Octopools and receive pool fees when they withdraw, which confirms the bridge and liquidity mechanism covered by this survey.
Current observation and perimeter
The DefiLlama protocol API read on 2026-08-15 classified Symbiosis as a Cross Chain Bridge and showed approximately $8.74M TVL across a 55-chain survey scope spanning EVM chains, TON, and Bitcoin. Many chain balances were zero or very small, and the largest were under $1.7M. Total and route-level liquidity therefore remain below the shared v1 size floor.
Control and exit applicability
Cross-chain execution depends on a relayer MPC group and a sequence of source, Host Chain, and destination transactions. Failed routes can revert automatically, but each revert is also a cross-chain operation and returns the route transit asset after deducting relayer gas. An Octopool LP withdrawal burns the pool claim and may require a second bridge step, so total TVL overstates the exit capacity of any one route.
Why the class rule decides
The shared v1 size rule decides this case because the current bridge and Octopool system remains below the size floor and spreads its liquidity across many routes. We do not open an individual review until DefiLlama TVL clears the size floor for 30 consecutive days. We would then review MPC membership and threshold, contract and upgrade authority, Host Chain security, supported routes and token issuers, Octopool composition, audits and incidents, stuck and reverted operations, route-level liquidity, stressed exits, and named bridge alternatives.
Research status
This is a capacity-unproven record for Symbiosis, 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.
- Symbiosis — protocol overview · primary · accessed 2026-08-15
Supports: cross-chain exchange, supported networks, relayers network, Octopools, cross-chain services - Symbiosis — BridgeV2 contract · primary · accessed 2026-08-15
Supports: Portal and Synthesis, BridgeV2, MPC key, relayer execution, mint-burn messaging - Symbiosis — failed operations and reverts · primary · accessed 2026-08-15
Supports: multi-chain transaction path, stuck operations, automatic revert, transit asset, relayer fees - Symbiosis — Octopool liquidity · primary · accessed 2026-08-15
Supports: AMM multi-token pools, Host Chain, LP fees, withdrawal - DefiLlama — Symbiosis survey record · secondary · accessed 2026-08-15
Supports: current TVL, 55-chain perimeter, chain-level balances, Cross Chain Bridge 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 |
|---|---|---|---|
| Tron | Rejected | Issuer can freeze | governance has been bypassed at nine-figure scale without a vote; treat it as centrally directed. |
| 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. |
| Hyperliquid / HyperEVM | Rejected | Issuer can freeze | a 21-validator permissioned set operates both the chain and its bridge. One compromise reaches both. |
| 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. |
| 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. |
| BNB Smart Chain | Rejected | Issuer can freeze | the validator set concentrates around one company, and the chain has been halted by decision. |
| Mantle | Rejected | Issuer can freeze | the team can push instant upgrades; there is no exit window a client could use. |
| Plasma | Rejected | Issuer can freeze | the production validator committee is permissioned and the public docs still describe decentralization as a phased future rollout with no fixed access timeline. |
| Gnosis Chain | Approved with limits | Governed, no freeze | the chain validator path is permissionless, but its xDAI and canonical bridge exposure adds an 8-of-15 governor multisig outside the base consensus grade. |
| Robinhood Chain | Rejected | Mixed control | one sequencer and two permissioned validators sit beneath an emergency council and transaction filter that can defeat the normal force-inclusion backstop. |
| Cronos | Rejected | Issuer can freeze | the validator set and direction are governed by one exchange company. |
| Monad | Approved with limits | Governed, no freeze | the L1 has a public validator path, but its short production record, single initial client lineage, and Foundation-directed delegation keep stake and operations concentrated. |
| Avalanche | Approved with limits | Governed, no freeze | 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. |
| Bitcoin | Approved | No freeze key | no issuer, sequencer, or upgrade key controls native Bitcoin; the standing control risk is mining-pool concentration, not an administrative backdoor. |