The short answerStargate delivers the real asset on the destination chain rather than a bridge wrapper, with unified pools deep enough for institutional-size transfers. It is a large concentrated pool of value secured by a configurable messaging layer, which is precisely the profile bridge attackers look for.
Best forUnified liquidity transfers of native assets
Trust assumptionsweight 30%
6.5avg 7.2
Exploit historyweight 25%
9.0avg 8.8
Settlement speedweight 15%
8.5avg 8.3
Chain coverageweight 15%
8.5avg 8.1
Costweight 15%
7.5avg 8.2
this service category average across 15Score = Σ mark × weight. Works well for a specific use case, weaker outside it. Methodology.
| Criterion | Mark | What we found | Source | Checked |
|---|
| Trust assumptions | 6.5 | not sourced yet | not sourced yet | — |
| Exploit history | 9.0 | not sourced yet | not sourced yet | — |
| Settlement speed | 8.5 | not sourced yet | not sourced yet | — |
| Chain coverage | 8.5 | not sourced yet | not sourced yet | — |
| Cost | 7.5 | not sourced yet | not sourced yet | — |
What we liked, and what fell short
Liked- Receives native USDC or USDT rather than a bridge wrapper
- Deep pooled liquidity supports large transfers
- No exploit of its own contracts to date
Fell short- Security ultimately depends on LayerZero's verification configuration
- Pooled liquidity is a large concentrated target
Why the marks landed where they did
Wrapped assets are a persistent annoyance and a persistent risk: you receive a representation whose value depends on the bridge remaining solvent, and unwinding it later costs another transaction. Stargate's unified liquidity pools let you receive native USDC or USDT directly.
How unified liquidity works
Each supported asset has a single shared pool spanning all chains, rather than separate pools per route. That concentrates depth, which means large transfers execute without the slippage that fragmented liquidity would cause, and it concentrates risk in the same place.
The security position
Stargate's own contracts have not been exploited. Its messaging security is LayerZero's, which depends on how the application configures its verifier networks. A large pooled balance behind a configurable verification layer is the classic bridge risk profile, and it is the reason this scores 6.5 on trust assumptions despite a clean record.
Cost and coverage
Around 0.06% plus gas, with support across the major EVM chains and a growing set beyond. Transfers are fast, typically completing within a minute or two.
Who should use it
Users moving size in stablecoins who need native assets on the destination chain. For USDC specifically, CCTP achieves the same outcome without any pooled collateral, and is the safer route where both are available.
FAQ
Does Stargate give me wrapped tokens?+
No. Its unified pools deliver the native asset on the destination chain, so there is nothing to unwrap later.
What secures Stargate?+
LayerZero messaging, with security depending on the verifier configuration, plus Stargate's own contracts, which have not been exploited.
Is Stargate good for large transfers?+
Yes — unified liquidity pools provide the depth for size without significant slippage, which fragmented per-route pools cannot.
Stargate or CCTP for USDC?+
CCTP, where available: it achieves native USDC delivery with no pooled collateral to attack.
