DEX, swaps & DeFi

Stargate

by LayerZero

A cross-chain asset transfer protocol and bridge interface powered by LayerZero infrastructure. It supports transfers of selected tokens across Ethereum and other supported networks, with liquidity pools and a transfer interface.

Type
Cross-chain bridge and liquidity protocol
Chains
EVM protocol networks; broader EVM and non-EVM interface support
Markets
Native assets and supported omnichain tokens
Custody
Smart-contract liquidity pools and backed token representations
Platforms
Web bridge, smart contracts, developer integrations

What Stargate does

Stargate is a cross-chain asset transfer interface and liquidity protocol built on LayerZero messaging. Its protocol contracts coordinate liquidity pools holding native assets on EVM networks. Stargate also uses Hydra deployments, where backed omnichain token representations extend access to assets on other supported chains. The interface supports transfers involving Stargate assets, LayerZero omnichain tokens, and other supported interoperability standards. Users select a source network, destination network, and asset to access an available transfer route.

Traders use Stargate to move assets between blockchain markets and inspect the destination asset before submitting a transfer. Pool-to-pool transfers differ from routes that create or redeem backed token representations. Builders can integrate Stargate contracts and transfer infrastructure into cross-chain applications. Available routes depend on supported tokens, liquidity pools, credit allocation, and messaging configurations. Stargate's interface also covers supported non-EVM transfers, although its underlying native liquidity protocol contracts operate on EVM networks. This distinction matters when evaluating route coverage and asset representations.

Best for: Traders who transfer supported assets between chains and need to distinguish native pool transfers from omnichain token routes.

Strengths

  • LayerZero messaging coordinates transfers between Stargate liquidity pools and supported Hydra deployments.
  • The interface supports Stargate assets, LayerZero omnichain tokens, and other supported cross-chain transfer standards.
  • Developers can integrate Stargate liquidity contracts and use its documented cross-chain transfer infrastructure.

Limitations

  • Stargate's native liquidity protocol contracts operate on EVM networks, even though its interface supports non-EVM transfers.
  • Pool capacity and allocated route credits determine which transfers can be fulfilled.
  • Hydra routes can deliver backed omnichain token representations instead of the destination chain's native asset.

Where we compare Stargate

  • Top 8 Cross-Chain Bridges: Routes, Fees and Risks

    Stargate uses pooled liquidity and LayerZero messaging, with route capacity and destination token representation affecting transfer selection.

  • Top 8 Ethereum Bridges

    Stargate supports Ethereum and other networks through pooled transfers, while asset availability and destination liquidity remain route-specific.

Alternatives to Stargate

Stargate questions

Does Stargate always transfer the native version of a token?

No. Native pool-to-pool routes can deliver native assets, while Hydra routes can deliver backed omnichain token representations. The destination asset depends on the selected route.

Does Stargate support non-EVM blockchains?

The Stargate frontend supports selected non-EVM routes through LayerZero omnichain tokens and other integrations. Stargate's underlying native liquidity protocol contracts are deployed on EVM networks.

Details checked November 16, 2026. Features, chains and availability change, so confirm on the official site before you sign up or trade. Browse all tools.