Transfer assets between networks
Stargate
Stargate offers crosschain asset transfers and OFT routes. Its quote shows the receiving asset, route and fees before submission. Taxi is the current delivery mode following the October end of Bus.
Your ecosystem guide / LayerZero
LayerZero carries messages between applications on different blockchains. Those messages can move a token balance, trigger a contract action or return data from another chain. Stargate gives users a transfer interface; LayerZero Scan follows delivery.
OFT · OApp · lzRead
The application chooses its verification requirements. DVNs check the message, then an Executor submits the destination transaction. A token transfer, a contract call and a data query use this process differently.
An OFT keeps a unified token supply across its deployments. The source contract debits the sender; the destination contract credits the recipient. An adapter can lock an existing token instead of burning it.
Read the documentation ↗An OApp can send arbitrary instructions. For a composed transfer, receiving the token and executing the next application action have separate statuses in Scan.
Read the documentation ↗lzRead lets a contract obtain remote onchain data. The response comes back to the requesting contract, which can use it in its own logic.
Read the documentation ↗The same messaging protocol supports different products. Choose a transfer interface to move an asset, an explorer to follow delivery or documentation to build an integration.
Transfer assets between networks
Stargate offers crosschain asset transfers and OFT routes. Its quote shows the receiving asset, route and fees before submission. Taxi is the current delivery mode following the October end of Bus.
Follow both sides of a message
Find a message by source transaction hash or address. Scan separates source confirmations, verification and destination execution, including any composed action.
Move USDT-backed liquidity
USDT0 uses OFT messaging. An Ethereum adapter locks or unlocks the underlying token; corresponding deployments mint or burn the crosschain token as supply moves.
Build crosschain applications
OApp carries application messages; OFT supplies token-transfer logic; lzRead retrieves remote state. Developers configure peers, DVNs and execution for each supported pathway.
A successful source transaction starts the message journey. Source confirmations, verification and destination execution can finish at different times.
The application sets the required block confirmations. DVNs begin checking once that threshold is reached.
Required DVNs and any optional threshold must attest before verification can be committed. The chosen providers belong to that application and pathway.
Inflight means a stage is still pending. Delivered records successful receipt by the destination contract. When a composed action follows, Scan shows its result separately; inspect execution errors in Scan. Once the cause is resolved, execution can be retried through its interface.
The contracts coordinate supply across networks. The asset issuer chooses whether a deployment burns tokens or holds an existing token in an adapter.
One side burns the sent amount; the other creates the corresponding amount. The recipient receives the destination deployment of that asset.
An adapter holds the original token while the crosschain representation circulates. A return transfer can unlock the original.
The application’s supported pathway and the recipient service determine which token and network to use. The Stargate quote identifies what will arrive before you send.
The sender pays for source-chain gas and the work needed to verify and execute the message. Product fees can be added by the transfer interface.
Keep the source network’s gas asset available to submit the transaction. Destination execution is priced through the selected execution service.
Since 1 September 2026, the LayerZero Labs Executor minimum is $0.25 per transaction; selected pathways may cost more. Other service providers set their own terms.
Stargate’s OFT product fee is up to 0.02%, capped at $250 per transfer, separate from the Executor fee. The app displays the fee before submission. This product fee applies to transfers made through Stargate.
The latest fee-switch vote ended Off in June 2026. Stargate revenue already supports a separate ZRO purchase programme.
ZRO holders vote on an additional protocol fee. If enabled, that fee is converted into ZRO and burned. Infrastructure and application charges continue under their own pricing.
The Foundation’s tracker records the active Stargate-revenue ZRO buybacks and the inactive protocol-fee channel.
Following the Stargate acquisition, STG holders can use the official conversion route until 15 December 2026. Stargate v1 has reopened for redemptions; the official update links the conversion instructions.
LayerZero’s 20 October announcement sets the planned mainnet launch date. The current messaging protocol continues to connect applications on existing networks.
Zero separates transaction execution from proof verification. Its announced model gives ZRO roles in gas, delegated staking and governance when the network launches.
ATLAS brings matching, clearing, settlement and risk into a backend on Zero. Users are intended to trade through connected venues, each with its own interface.
The announced ATLAS model first pays the venue rebate. Of the remainder, 25% goes to the market creator and 75% to buying and burning ZRO.
Start at the official transfer interface with the asset on a supported source network. Keep the source transaction hash to check progress in Scan.
Choose the source and destination networks, asset and recipient. Use the token and network supported by the receiving wallet, exchange or application.
Compare the quoted receiving token, amount and charges. Keep enough of the source chain’s gas asset to submit the transfer.
Look up the source transaction hash. Follow verification and destination execution; for a composed action, also read its separate result.
Verification and execution services earn fees for processing messages. Stargate’s product revenue also feeds its documented ZRO buyback programme.
Checked on 23.10.2026
Checked on 23.10.2026
Information checked: 23 October 2026
The working LayerZero protocol carries messages between applications on different blockchains. Stargate is a transfer interface using that infrastructure. Zero is a separate blockchain scheduled to launch on 30 November 2026.
The source contract burns or locks the sent balance. After verification, the destination contract mints or unlocks the corresponding amount. The mechanism keeps supply coordinated across the asset’s deployments.
Search the source transaction hash in LayerZero Scan. Check source confirmations, verification and destination execution. A composed application action has its own result after receipt.
Each application configures its verification requirements for its pathways. Required DVNs and an optional threshold determine when a message can be verified.
The quote includes the relevant messaging and product charges. Stargate’s OFT product fee is up to 0.02%, capped at $250; the LayerZero Labs Executor minimum is $0.25. Network gas is paid separately and route pricing can vary.
The June 2026 vote ended Off. Stargate-funded ZRO purchases are an active, separate programme recorded by the Foundation.
The official deadline to convert STG to ZRO is 15 December 2026. The October ecosystem update links the conversion instructions and confirms Stargate v1 redemptions are open.