Stargate V1
Stargate V1 is a cross-chain bridge. Depositors fund unified liquidity pools that let users move native assets between chains with guaranteed finality. V1 uses single-sided asset pools, so the two-asset AMM-LP dossier is not the main rule. The August 15, 2026 survey reported about $9.73M across thirteen chains, while current Stargate documentation still lists V1 as a live route alongside V2. The v1 below-materiality dossier therefore governs this active legacy-version record.
- 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
Stargate V1 uses LayerZero messages and the Delta algorithm to support native-asset transfers through unified, single-sided pools. Liquidity providers fund one asset pool and collect transfer fees across connected routes. The position is not a two-asset AMM inventory claim, and current evidence does not show discretionary portfolio allocation. The size screen therefore applies instead of amm-lp or delegated-allocation.
Current observation and lifecycle
The DefiLlama API read on 2026-08-15 classified Stargate V1 as a Cross Chain Bridge and reported approximately $9.73M across Ethereum, Arbitrum, Optimism, Polygon, Base, Avalanche, Binance, Fantom, Linea, Mantle, Metis, Kava and a zero-value Goerli record. Stargate’s current architecture documentation still lists V1 and V2 as separate pool routes, so V1 should not be called archived or fully sunset.
Control, loss and exit applicability
V1 divides each local asset pool into credits for remote routes and relies on LayerZero messaging and enough destination liquidity. LP returns come from transfer fees, while capital faces bridge-contract, message-validation, chain, asset and route-balance risks. A local LP exit depends on the asset balance available in the pool and the current credits and traffic pattern. Aggregate TVL does not prove that a proposed-size redemption will work.
Why the class rule decides
The shared v1 below-materiality dossier governs because live V1 TVL remains below the size floor, and no more basic existing class fits its single-sided bridge-liquidity mechanism. We do not open an individual review until it clears that floor. Reopen after reproducible V1-only TVL remains at least the size floor for 30 days, then name a chain, pool and asset and review contracts, LayerZero configuration, DAO and emergency powers, route credits, exploit and incident record, fee economics, and stressed local redemption capacity against direct asset custody.
Research status
This is a capacity-unproven record for Stargate V1, 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.
- Stargate — V1 route and Delta mechanism · primary · accessed 2026-08-15
Supports: V1 route, single-sided pools, Delta algorithm, LayerZero, transfer fees, guaranteed finality - Stargate — current route architecture · primary · accessed 2026-08-15
Supports: V1 lifecycle, V2 coexistence, pool routes, messaging dependency, DAO approval - Stargate — credit allocation mechanics · primary · accessed 2026-08-15
Supports: V1 static credits, pathway liquidity, local redemption, route balancing - DefiLlama — Stargate V1 survey record · secondary · accessed 2026-08-15
Supports: current TVL, thirteen-chain perimeter, Cross Chain Bridge 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 |
|---|---|---|---|
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |