What Is Stargate?

Stargate is an omnichain liquidity-transport protocol that moves native assets between chains by drawing from and depositing into shared liquidity pools, rather than minting a wrapped representation on the destination side. Most bridges solve cross-chain transfer by locking an asset on one chain and issuing a synthetic version on the other, which fragments liquidity into many small, isolated pools, each only as deep as the capital someone chose to park on that one route. Stargate instead treats liquidity as a single shared resource: a pool of USDC on Ethereum and a pool of USDC on Arbitrum both belong to the same logical pool, and a transfer simply rebalances value between the two sides while the user receives the real asset at the destination, with no synthetic token ever entering the picture.

Unified liquidity vs isolated pools

In a conventional bridge design, every route between two chains needs its own liquidity, so capital gets split across dozens of thin pools that are each more exposed to being drained in a volatile market. Stargate's unified-liquidity model pools deposits from every connected chain into one accounting system, which means a single pool backs many routes at once and capital efficiency rises as more chains join the network — a point covered in detail in the Stargate docs. The practical effect is that a large transfer is less likely to exhaust a pool's depth and move the price of the swap against the sender.

Why native assets matter

Receiving native USDC instead of a wrapped version means the asset can be used immediately in any protocol on the destination chain without first being swapped or unwrapped. This removes a step that otherwise costs gas and introduces slippage, and it avoids the risk that a wrapped asset trades below the real one if confidence in its issuer weakens. It also means a destination chain's own DeFi applications treat the arriving balance exactly like locally minted supply, with no special handling required.

Stargate's delta algorithm is the mechanism that keeps unified liquidity solvent while transfers happen asynchronously across chains that never see each other's state in real time. Each pool tracks a delta credit — the amount it can safely send out — and every outgoing transfer checks that credit before it is allowed to settle. If a pool's delta credit runs low because many transfers have flowed out of it recently, the algorithm throttles further withdrawals until rebalancing or new deposits restore the buffer, rather than letting the pool go negative or forcing a withdrawal to fail without warning.

Rebalancing between chains

Because the pools are logically unified but physically sit on separate chains, the protocol periodically rebalances actual token holdings so that no single chain's pool is left too thin to serve its local demand. This rebalancing is what lets Stargate advertise deep liquidity on every connected chain instead of deep liquidity on only the busiest ones.

Why throttling beats failure

A pool that simply let every request through until it hit zero would eventually leave the last users with nothing and no warning. By checking the delta credit before a transfer settles, Stargate turns a potential failure into a predictable limit: large transfers may need to route differently or wait for rebalancing, but no one's funds are ever stranded mid-transfer.

A defining feature of Stargate is guaranteed finality: once a transaction is confirmed on the source chain, the corresponding action on the destination chain is guaranteed to either complete or revert in a predictable way, with no state where funds are stuck in limbo. This is possible because Stargate is built directly on LayerZero's messaging layer, which relays a verified message between chains instead of relying on a third-party custodian to decide when a transfer is valid. The result is that a user's transaction has one clear outcome, confirmed on both ends, rather than a pending state that depends on a centralized operator catching up.

What finality removes from the equation

On many older bridge designs, a user had to trust that an off-chain relayer or multisig would eventually process their deposit, and that trust was itself the main risk. Guaranteed finality replaces that wait with a verifiable message, so the outcome of a transfer is determined by the protocol's logic rather than by whether an operator is online.

STG is Stargate's native governance and utility token. Holding STG on its own grants limited rights; the protocol's real governance power sits with veSTG, a vote-escrowed token obtained by locking STG for a chosen period. The longer the lock, the more veSTG a given amount of STG produces, which ties voting weight to a long-term commitment rather than a short-term holding.

• STG is the liquid, transferable token distributed to the community and liquidity providers.
• Locking STG for a fixed term mints veSTG, which cannot be transferred or traded.
• veSTG holders vote on protocol parameters, including which pools receive emissions.
• Emissions direct STG rewards toward the pools that voters decide need deeper liquidity.
• Locking for longer periods produces more veSTG per STG, rewarding patient governance participants.

Why vote-escrow matters for liquidity

Because veSTG holders choose where emissions flow, the token model gives long-term participants direct influence over which chains and pools stay well capitalized. This is the same vote-escrow pattern used across DeFi to align governance weight with sustained commitment rather than with capital that could exit the next day; STG's own contract and supply figures are visible on Etherscan.

Stargate connects a broad set of EVM networks and several non-EVM environments through LayerZero's endpoint model, letting the same unified pools serve transfers between any two connected chains without a separate bridge contract for each pair. An omnichain swap on Stargate can combine a cross-chain transfer with a token swap in one step, so a user can, for instance, send USDC from one chain and receive USDT on another in a single confirmed transaction, with the swap and the transfer settling together rather than as two separate actions.

Chain type	Example networks	What Stargate moves
EVM layer-1 and layer-2	Ethereum, Arbitrum, Optimism, Polygon	Native stablecoins and ETH
Alternative EVM chains	Avalanche, BNB Chain, Base	Native stablecoins and bridged majors
Non-EVM networks	Networks reachable via LayerZero endpoints	Assets supported by the local pool

Why endpoint coverage keeps growing

Because Stargate inherits its cross-chain messaging from LayerZero rather than building a custom bridge for every new network, adding a chain mainly requires a LayerZero endpoint and a liquidity pool rather than an entirely new codebase. That is part of why the list of supported networks has expanded steadily, a trend trackable through aggregated TVL data on DefiLlama.

How an omnichain swap differs from a plain transfer

A plain transfer sends the same asset across and expects the same asset back. An omnichain swap adds a conversion step on the destination side, so the pool that receives the incoming asset also executes a local swap before crediting the user, letting the two actions share one signature and one confirmation instead of a transfer followed by a separate swap transaction.

Stargate sits in a broader shift described as the omnichain thesis: instead of users and liquidity being locked to one chain and bridges being treated as an afterthought, applications are designed from the start to operate across many chains through a shared messaging layer. LayerZero provides the generic message-passing primitive, and Stargate is the flagship application that proved the model works for real value transfer at scale, which is why it is often the first integration other omnichain protocols point to. A broader overview of the cross-chain interoperability problem it addresses is summarized on Wikipedia.

What other protocols build on top of Stargate

Wallets, aggregators and yield platforms route stablecoin transfers through Stargate when they need a user's balance to land as a native asset rather than a wrapped one, because it removes an extra swap step for the end user and keeps the integration simple for the application builder.

A traditional lock-and-mint bridge locks the deposited asset in a contract on the source chain and mints a brand-new wrapped token on the destination chain, so the receiving chain's supply of that asset is really two separate tokens: the native one and the wrapped one, each with its own market and its own liquidity. Stargate avoids that split entirely by settling transfers against the same unified pool of the native asset on both sides, so there is only ever one USDC, one USDT or one ETH balance to track on a given chain, not a native version and a bridged version competing for the same liquidity. This is also why Stargate transfers do not depend on anyone later redeeming a wrapped token back for the original — the native asset is what the user held and what the user receives.