Stargate is a Cross-Chain Bridge Built on Unified Liquidity

Last updated 10 Aug 2026

Stargate is a bridge, meaning a service that moves tokens between blockchains, using shared reserves called unified liquidity. Built on LayerZero messaging, it connects same-asset routes through pools, Omnichain Fungible Token (OFT) paths, and Circle Cross-Chain Transfer Protocol (CCTP) routes. A user selects a source chain, asset, destination chain, and recipient; the quote then exposes the expected receipt and network costs before signing. It serves multichain transfers, DeFi integrations, and liquidity deployment.

How Does a Transfer Move Through Stargate?

A Stargate transfer moves a supported asset through one quoted route: pool liquidity, an OFT path, or CCTP, with LayerZero carrying messages for Stargate-native routes.

On an EVM route, the wallet first confirms the source network and token contract. Ethereum uses chain ID 1; Arbitrum One uses chain ID 42161. A first ERC-20 transfer commonly requires 2 source transactions: one approval and one send. An existing sufficient allowance reduces that to 1 send transaction. Native gas assets skip ERC-20 approval. The quote must name the same recipient on the destination, because the source transaction commits the cross-chain instruction before any destination receipt appears on that target network.

The route quote then fixes the transfer parameters. The amount sent uses local token decimals, minAmountLD protects the minimum receipt, and maxAmountLD reflects the credits available for that pathway. Signing authorizes those values, plus the messaging fee quoted in the source chain’s native gas token.

A pool route deposits the asset into a source pool and releases matching liquidity from a destination pool. A Hydra path locks the core asset and mints its configured OFT representation on a connected chain. Circle CCTP follows its own USDC burn-and-mint route. Each mechanism preserves the selected asset’s economic identity, although the destination token contract differs by route.

After source confirmation, the destination action follows the chosen mechanism. The next useful check is the received token contract and amount, not the ticker alone.

The Four Numbers Behind a Stargate Quote

A Stargate quote reduces the decision to four numbers: amount sent, amount received, route maximum, and the native-token fee for execution and messaging.

Amount Sent and Received

The quoteOFT call returns 3 outputs: transfer limits, fee or reward details, and the OFT receipt. The receipt states amountSentLD and amountReceivedLD in local decimals. A positive fee reduces the receipt; a route reward increases it. The user-facing difference between those amounts captures the token-side effect, while the wallet separately displays gas. This separation matters because a stablecoin deduction and an ETH gas payment are different costs.

Route Maximum and Credits

The maximum comes from Stargate’s credit allocation for a particular asset pathway. Credits represent destination capacity, so a large quote on Ethereum-to-Arbitrum does not establish the same capacity on Base-to-Avalanche. A fresh quote owns the decision because balances and planner allocations move with transfer demand.

Native Fee and Timing Trade-Off

The quoteSend call prices the LayerZero message in the source network’s native token, while the wallet estimates source execution gas. Pool routes also show a dynamic treasury fee or reward set per pathway. Hydra OFT routes can charge a treasury fee but do not return a pool-rebalancing reward. Taxi and Bus then change the messaging share and delivery schedule.

Should You Take the Taxi or Ride the Bus?

Choose Taxi when delivery speed or destination execution matters; choose Bus when Stargate offers batching and a lower messaging share is worth an uncertain wait.

Taxi sends one transfer message immediately and encodes oftCmd as an empty, 0-byte value. Bus uses a 1-byte command and waits for its configured batch. A bus departs when it reaches between 2 and 10 passengers, or when someone pays to drive it early. Local settlement occurs when the source transaction succeeds, but destination delivery follows the batch departure. Each passenger receives a ticket whose identifier uses the uint56 type, giving the queue a precise on-chain ordering key.

Driving a bus pays for the remaining seats and releases the batch before it fills naturally. Source and destination finality still shape visible arrival, so the quoted route time must fit the next application deadline.

High-Value Uses for Unified Liquidity

Unified Stargate liquidity is most useful when a user needs the same fungible asset on another chain without arranging a separate market trade. It supports moving USDC before an Aave deposit, repositioning USDT between treasury wallets, and funding an application on a new network. Network identifiers provide a concrete preflight check: Base uses chain ID 8453, Avalanche uses 43114, and BNB Chain uses 56. Route support still follows the selected asset’s configured mesh.

Composability Beyond a Basic Bridge

Stargate composability lets a developer pair asset delivery with destination-chain contract logic, reducing a bridge-then-call workflow to one cross-chain instruction for the user. Only Taxi supports composed execution. The protocol exposes 3 composable entry points: sendToken, send, and redeemSend. A destination receiver implements ILayerZeroComposer, decodes the message, and executes budgeted logic such as an Aave deposit or Uniswap trade. This design removes a separate user signature on the destination, so developers next choose Taxi and size the destination gas budget.

Where Do Stargate Transfers Meet Hard Limits?

Hard limits in Stargate transfers occur at route availability, quoted credits, recipient encoding, and destination execution rules; no interface setting creates an unavailable asset-chain path.

Asset support belongs to a configured mesh rather than a universal token list. Selecting USDC on Ethereum therefore reveals only destinations connected to that USDC instance. The quoteOFT maximum enforces available credits for the route at that moment. An amount above that ceiling needs another live quote, a smaller amount, or a different supported path. Splitting a transfer makes sense only when each part receives its own executable quote (covered in practice ).

Address encoding also matters. An EVM recipient is 20 bytes, while SendParam carries the recipient in a 32-byte field. The destination endpoint uses uint32, local amounts use uint256, and the Bus shared-decimal amount uses uint64. Integrations must convert these fields exactly before they calculate a minimum receipt or message fee.

Pool routes add liquidity and smart-contract exposure; OFT routes rely on the configured mint, burn, or adapter logic; CCTP relies on Circle’s attestation flow. Composed calls introduce the destination application’s execution conditions as well. Audits reduce uncertainty without erasing contract, messaging, liquidity, or asset-representation risk. The route’s mechanism therefore belongs in the decision beside its fee and timing.

Across, CCTP, and Canonical Bridges by Mechanism

Typically, Stargate suits pool-backed and OFT routes, while Across, Circle CCTP, and canonical rollup bridges use different capital, settlement, and trust assumptions for users.

Across and Relayer-Filled Intents

Across accepts an intended outcome and lets relayers front destination liquidity, then settles repayment through its hub-and-spoke system and UMA verification. That model emphasizes fast fills and solver capital. Stargate pool routes commit against protocol credits, while Bus explicitly batches messages. The choice turns on whether the user prefers relayer execution or reserved route capacity.

Circle CCTP for Native USDC

Circle CCTP burns USDC on the source chain and mints native USDC on the destination at a 1:1 amount. It avoids third-party liquidity pools for that asset and limits the use case to supported USDC paths. Stargate can expose CCTP as one route within its broader transfer architecture, so the quoted mechanism matters more than the front-end label, which is discussed in Stargate pricing.

Arbitrum and Optimism Canonical Paths

Arbitrum’s canonical bridge and the OP Mainnet Standard Bridge follow their rollups’ native contracts rather than shared external liquidity. OP Mainnet sets a 7-day Standard Bridge withdrawal window from Layer 2 to Ethereum. Canonical paths fit users who prioritize a direct rollup route, while liquidity bridges target faster destination availability. Direction, asset contract, and withdrawal deadline decide between them.

A Route-Ready Decision Checklist

A Stargate transfer is ready to sign when the route, asset representation, recipient, quote limits, and destination plan all match the intended outcome.

• Use the exact asset-chain path shown in the quote, rather than assuming that a shared ticker means a shared token contract.
• Select Taxi for composed execution or time-sensitive delivery; select Bus only when batching appears and the wait fits the deadline.
• Approve the displayed ERC-20 amount when the existing allowance is insufficient, and reserve the source network’s native token for gas.
• Match native USDC, USDC.e, WETH, or another OFT representation to the destination application that will receive it.
• Keep the transfer at or below maxAmountLD, and reject any quote whose minAmountLD misses the required destination amount.

Passing all five conditions narrows the remaining choice to route cost and timing. The final wallet prompt should reproduce the source chain, contract, amount, recipient, and native fee already shown by the quote.

Advanced Paths, Liquidity Roles, and Token Status

Advanced Stargate use separates three roles: integrators compose transfers, liquidity providers fund pool routes, and token holders follow the protocol’s post-acquisition structure.

Developer Controls

SendParam contains 7 fields covering destination endpoint, recipient, local amount, minimum receipt, options, compose data, and transport command. The sendToken call returns 3 records: a messaging receipt, an OFT receipt, and a Bus ticket. Integrators use quoteOFT before quoteSend, preserve the refund address, and budget extra destination gas only when composeMsg carries application logic.

Liquidity and Yield

Pool depositors receive LP tokens representing a proportional reserve claim. Active reward programs let those LP tokens enter farm contracts, but the yield moves with incentives, utilization, and pool conditions. Single-asset deposits avoid the two-token ratio used by many automated market makers, yet they retain smart-contract, liquidity, and incentive risk. A provider’s next decision is the pool’s exposure and withdrawal terms.

STG After the Acquisition

The 2025 acquisition terms removed STG from Stargate operations, dissolved the Stargate DAO, and established a fixed redemption of 1 STG for 0.08634 ZRO. The bridge protocol continued as LayerZero-aligned transfer infrastructure, so STG ownership is not a prerequisite for moving assets or paying route fees. Users pay with the transferred asset and the source network’s native gas token; developers integrate the transfer contracts and route system.

Things people ask about Stargate