Stargate: capped OFT fees, Taxi transfers and October asset-support deadlines

Stargate is a cross-chain liquidity transport protocol with token swap/transfer functionality. It uses pool liquidity and cross-chain messaging to move a supported asset across separate networks or into a supported alternate representation. Its current V2 architecture includes core unified liquidity and a Hydra mechanism in which a native asset may be locked in a core pool while a mapped omnichain representation is minted on a destination chain. This is technically different from buying Bitcoin against a bank deposit or resting an order on a single central exchange order book.[5][4][3][9]

The route UI must specify both the token identity and source/destination networks; onchain swaps depend on exact chain/asset combinations, liquidity, current contract state and messaging security. Stargate’s technical docs discuss a protocol built on LayerZero and pool balancing through credit-allocation mechanisms. For an end user, the practical output is the quantity and type of token deliverable at the destination, not a generic coin balance guaranteed in fiat. The same token ticker across chains may represent a native coin, wrapped token or Hydra-issued asset with very different redemption and smart-contract exposures.[5][4][3][9]

LayerZero’s August 11, 2026 fee announcement states that OFT transfers through the Stargate app carry up to two basis points from September 1, capped at $250 per transfer. Two basis points is 0.02%, so an eligible $10,000 transfer at the maximum 2bps component implies $2 before other costs. However, this figure applies to the named OFT transfer charge and route, not every native-pool or cross-token transaction. The same update separately described a LayerZero Labs Executor fee minimum of $0.25, with chain gas and other protocol costs potentially additional.[6][7][3]

The source-chain transaction requires its own gas, and the bridge route may expose the sender to pool fees, destination gas arrangements, token-conversion ratios and changing quote conditions. Old user documentation describes Stargate Bus batching as a cheap option, but the September operational update ended Bus deliveries from October 1, moving transactions to Taxi only. A 2025 Bus-versus-Taxi cost comparison is therefore not appropriate for this October service profile. Avoid quoting outdated fixed 0.06% averages as the current universal charge.[6][7][3]

Stargate has no universal local bank deposit account for customers. The user holds tokens on the source chain, connects a wallet, requests a quote with an explicit destination chain and signs the required onchain operation. Depending on the route, the source may lock a native asset in a liquidity pool and release assets elsewhere or mint/burn an omnichain representation. Wallet gas is needed for the source transaction; the destination may involve its own verification and relayer/executor steps before the asset becomes spendable.[3][4][8]

A confirmed send on the source chain is not proof that the destination has completed. Track the source hash and the LayerZero/Stargate message until delivered and inspect the target asset contract. The revised support bulletin set 23 October asset-support deadlines for certain chains. Those dates have passed as of this review; an old supported-route screenshot does not establish that a late exit remains available.[3][4][8]

Stargate is wallet-connected, but user funds are not necessarily under individual wallet control for the entire transfer. The protocol may lock a token in a pooled smart contract while a destination asset is created or released. Unified liquidity pools rely on allocation and redemption mechanics; an OFT representation has token contract and cross-chain backing assumptions. A wallet owner must distinguish successful message finality from the economic claim represented by the received token. This is an infrastructure contract risk rather than the private balance sheet of a conventional centralized exchange.[3][4][8]

Cross-chain dependencies include contract security, message verification under LayerZero, destination chain liveness, relay costs, bridge liquidity and token issuer restrictions. A deprecation of a satellite chain can create a real withdrawal deadline for Hydra or liquidity-provider positions even if the token still appears in a wallet. The documented deadline is an operating constraint, not evidence of a full protocol shutdown. Core networks such as Ethereum, Arbitrum, Base and BNB Chain are identified as deeper-liquidity migration destinations in the bulletin, but route and asset availability require a current check.[3][4][8]

Eligibility is chiefly asset, wallet and route-specific rather than based on a universal customer onboarding list. A source wallet must be able to sign on the chosen network and hold gas; the protocol must still support that pool and token. The July 24 support update named Gravity, Camp, GOAT and Metis among networks with Stargate asset-support deprecation effective October 23, 2026, with owners told to move or redeem assets before that date. Other chains in the same bulletin had earlier effective dates. The 23 October deadline had already passed by the 26 October review.[8][7]

The presence of an old quoted token price or an OFT contract is not proof of ongoing cross-chain redemption. Users holding specific Hydra assets or pool LP positions may need a migration transaction, and those who miss a cutoff can lose access to the related funds. Conversely, these scheduled deprecations do not mean all Stargate services end. Users should rely on the latest LayerZero and Stargate support announcements and the live route screen, not a scraped static “30+ chains” claim, to decide whether the desired path works.[8][7]

The troubleshooting starting point is the source-chain hash, exact token contract, sending and receiving networks and wallet addresses, plus the associated LayerZero message identifier when displayed. If the source token was locked but target not credited, distinguish a pending verifier/executor message from a destination token visibility problem or route that has become unsupported. A new source transfer can duplicate exposure rather than cure the original stuck message. Save the route quote and gas breakdown as well as each transaction hash.[8][3][6]

The provider’s support bulletin directs impacted users to bridge or redeem assets on affected networks. An ecosystem forum reply is not a substitute for the official signed transaction state. No worldwide guarantee of compensation for a chain deprecation, abandoned LP position or wrong token route was identified. Be especially cautious of spoofed migration websites: scammers often imitate urgent deadline announcements and request unlimited token approvals. Read the original LayerZero/Stargate destination rather than a direct-message link.[8][3][6]

Stargate is a smart-contract protocol involving liquidity pools, onchain tokens and cross-chain messaging, rather than an identified universal customer bank or central exchange counterparty. LayerZero’s acquisition of Stargate protocol activities in 2025 and its subsequent infrastructure announcements do not establish that the combined ecosystem holds a regulator approval to accept cash deposits or guarantee bridge redemptions everywhere. No matching financial-services permission number was established for the protocol.[3][7][5]

The rights of an asset holder depend on their wallet, token, smart contract and applicable legal jurisdiction. A business integrating cross-chain transfers may have additional compliance or custody responsibilities distinct from protocol code. LayerZero’s price schedule is a protocol-infrastructure fee notice, not a national regulatory filing. Token and chain-support withdrawals should be taken seriously regardless of whether a user believes the protocol is decentralized.[3][7][5]

LayerZero’s September 2026 ecosystem update says Stargate was acquired in 2025 and describes a finite conversion window for the former STG token into ZRO, ending 15 December 2026. The token transition should not be confused with closure of all Stargate bridging routes. It also reports that the old Bus transaction batch service was discontinued from October 1. These are distinctive continuing operational developments and matter for anyone using old fee guides, historical ticker labels or cached integration settings.[7][5]

Operator

Stargate protocol / LayerZero ecosystem (global contracting entity not established)

Exchange model

Decentralised

Service scope

Cross-chain native/OFT asset movement and supported swap-like transfers using Stargate liquidity pools and LayerZero messaging. Not a conventional fiat-funded central limit-order book.

Client types

Retail clients; Professional clients; Institutional clients

Pricing publication

Public and quoted pricing

Other names

Stargate Protocol; Stargate V2; Stargate

Headquarters

Decentralized multichain infrastructure

Pricing scope

Effective September 2026, certain Stargate app OFT transfers incur up to 2bps capped at $250, separate from LayerZero executor fees and gas; app quote varies by protocol route. Taxi route replaced Bus from Oct 1.

Funding scope

Supported token/network onchain sends and receives; no direct local-fiat bank account service. Requires source gas and a valid target wallet, plus route-specific limits.

Custody and asset handling

Wallet-connected blockchain smart contracts including liquidity pools, Hydra lock/mint representations and cross-chain messaging. Asset value and smart-contract security depend on involved chains/LayerZero verification.

Client eligibility

Compatible wallet, chain, token, source/destination liquidity and applicable route. Stargate V2 support ended for the named chains on 23 October 2026 under the published bulletin; do not infer all displayed networks remain available.

Support

Official project and LayerZero documentation and route status. No general bank-style payment recovery; source/destination hashes essential for incidents.

Authorisation and registration scope

LayerZero/Stargate smart-contract transfer infrastructure; not established as a regulated bank deposit or a universally licensed centralized crypto exchange. No matched financial authorisation number asserted.

Exchange metadata checked 29 Oct 2026Source 1Source 2Source 3Source 4Source 5Source 6Source 7Source 8Source 9

For an OFT transfer of $10,000 eligible for the maximum 2-basis-point platform component, the illustrated Stargate app fee is $2, before LayerZero Executor and blockchain network costs. That is a straightforward rate calculation, not a real executable rate. The fee cap of $250 matters only to sufficiently large transfers and only for routes covered by that charge. A liquidity-pool transfer can have a distinct fee schedule, and a cross-token exchange can include conversion economics as well as transport charges.[6][8][7]

The affected 23 October Stargate asset deadlines are already past. Holders need current asset- and chain-specific support information; this profile does not promise a late recovery. Comparing routes still requires the exact source/target token, contract, protocol fee, messaging dependency and ultimate settlement state.[6][8][7]