Volume
USDValue transferred through Stargate in the selected period, valued at the send block.
Dashboard · VantagePlanned
Stargate Bridge Tracker: Volume, Pools and Bus vs Taxi
How much moves through the Stargate bridge on each route, by bus or by taxi, and how much liquidity backs it?
Transfers through Stargate by route and mode, the liquidity in its pools on each chain, the credits between them and the fees users pay.
ShareEmail it
Blueprint
What the dashboard will show.
The dashboard as it will open in Vantage. Each figure is named here and arrives with its receipt; until its data is published, its place stays empty.
Transfers
Volume by route and mode, with what each mode costs.
Transfers
countTransfers delivered in the selected period.
Sent by bus
%Share of transfers in the period that rode a bus rather than a taxi.
Median fee
USDThe median of protocol fees plus messaging cost per transfer in the period.
Volume by source chain
USDValue transferred each day, split by source chain.
Busiest routes
Each route's volume, transfers, bus and taxi split, median fee by mode and median bus wait.
Pools
Liquidity on each chain, the credits between pools and Hydra supply.
Pool liquidity
USDAssets held in Stargate pools across covered chains at the latest day's end.
Hydra assets outstanding
USDSupply of Hydra assets on chains without a native pool, valued at oracle prices.
Liquidity by chain and asset
USDPool liquidity on each covered chain, split by asset.
Pools and credits
Each pool's chain, asset, balance, the credits it holds toward each destination and its fee or reward for rebalancing.
- Route
- Every covered source and destination pair
- Asset
- USDC, USDT, ETH and the other pooled assets
- Period
- Last 7, 30 or 90 days
About
What it answers, and for whom.
Stargate is a bridge for native assets such as USDC, USDT and ETH, built on LayerZero. It keeps a pool of each asset on every chain it serves: a transfer pays into the pool on the source chain and is paid out of the pool on the destination, and a system of credits tracks how much each chain may send to each other chain. Chains without a pool of their own receive Hydra assets, minted copies backed by pool funds elsewhere.
Users choose how their message travels. A taxi sends its own LayerZero message at once; a bus groups several transfers into one message, so each rider pays less and waits for the bus to leave. This dashboard reads every transfer, bus ride and pool balance from the contracts, so the volume by route, the cost of each mode and the liquidity behind it come from the same source.
In 2025 the Stargate DAO approved an acquisition by the LayerZero Foundation, under which STG can be swapped for ZRO. The pools and contracts keep running, and the dashboard reads them the same way.
Method
How it will be measured.
Every figure will be read at a block, kept with its source and its exact read, and open a receipt anyone can re-check.
How receipts work →- Transfers are read from each chain's Stargate pool and OFT sent and received events and matched across chains by the LayerZero message guid, so each transfer counts once.
- A transfer is a taxi when it carries its own LayerZero message and a bus ride when it is recorded as a passenger; a bus wait is the time from the ride to the event that drove that bus.
- Pool liquidity is each pool's balance at the day's last block, valued at oracle prices; Hydra assets are the supply minted on chains without a native pool, backed by funds in pools on other chains.
- Fees are the amount sent minus the amount received in each transfer, plus the LayerZero messaging fee paid in the source chain's native token.
The data it needs
Read from chain state and history
- bridge_flows_dailyTo buildBridge deposits and withdrawalsDeposits into and withdrawals out of canonical and major third-party bridges by chain, token and day, plus escrow balances at day end.
- defi_tvl_dailyTo buildDeFi value lockedAssets deposited in DeFi protocols per protocol, chain and asset at day end, valued with oracle prices, never double counting receipt tokens.
- token_supply_dailyTo buildToken supply by dayTotal supply of each registry token on each chain at day end: wrapped BTC, liquid staking tokens, tokenized assets and other tracked tokens.
- protocol_revenue_dailyTo buildProtocol fees, revenue and buybacksFees users paid to each protocol and the part kept by the protocol or its token holders, per protocol and day, including buybacks.
- native_prices_dailyTo buildOracle prices by dayReference prices of major assets read from on-chain oracle feeds (Chainlink latestRoundData) at each day's last block, with each round's update time.
- Stargate pool and OFT sent and received events on each covered chain, with the LayerZero guid
- Bus ride and bus drive events from Stargate's messaging contract
- Pool balances and credits at each day's last block
- totalSupply of Hydra assets on chains without a native pool
Questions
Questions people ask.
What is Stargate?
A bridge that moves native assets between chains using pools on each side and LayerZero messages. A user pays into the source chain's pool and receives the same asset from the destination chain's pool, not a wrapped copy, wherever a native pool exists.
What is the difference between bus and taxi on Stargate?
A taxi sends a transfer in its own LayerZero message straight away. A bus collects several transfers to the same chain and sends them in one message, so each passenger pays a smaller share of the messaging cost but waits for the bus to be driven.
What are Stargate Hydra assets?
Tokens Stargate mints on chains that have no native pool, such as bridged USDC or ETH, backed by funds locked in Stargate pools on other chains. The dashboard shows Hydra supply on each chain beside the pools that back it.
What happened to the STG token?
In August 2025 Stargate DAO voters approved an acquisition by the LayerZero Foundation. Under its terms the Stargate DAO is dissolved and STG holders can swap their tokens for ZRO. The bridge's contracts and pools continue to operate.
How is Stargate's security tied to LayerZero?
Every Stargate transfer is a LayerZero message, so it is accepted on the destination only after the verifiers configured for that route sign off. The LayerZero DVN checker shows those settings route by route.
- Credits
- Stargate's accounting of how much liquidity one chain's pool may draw from another, updated as transfers move between them.
- Bus
- A Stargate transfer mode that batches several transfers into one LayerZero message so they share its cost.
- Hydra asset
- A token Stargate mints on a chain without a native pool, backed by assets locked in its pools elsewhere.
Related
More apps like this.
LayerZero DVN Checker: Bridge Verifier Settings
Each major LayerZero-bridged token, route by route: which verifiers check its messages, how many must agree and whether one alone suffices.
Multi-chainEthereumArbitrum+5Bridged Token Backing: Locked vs Minted Supply
Whether each bridged token's supply on other chains is matched by tokens locked on its home chain, with every gap shown.
Multi-chainEthereumBase+4Across Protocol Bridge: Volume, Relayer Fees and Fill Times
Transfers bridged through Across by route, the fees users paid, how fast relayers filled them and the bundles that repaid the relayers.
EthereumArbitrumBase+5Wormhole Bridge Tracker: Messages, Token Transfers and NTT
Messages and token value moving over Wormhole by route and product, with the guardian set behind them and the rate limits on NTT tokens.
Multi-chainEthereumSolana+5Cross-Chain Intents: Volume, Solvers and Fill Times
How much volume intent-based bridges and swaps fill, which solvers and relayers fill it and how long a fill takes from deposit to delivery.
Multi-chainEthereumBase+2Blockchain Revenue Rankings: Monthly League Table
Major chains ranked by the fees users paid last month, split into fees burned and fees paid to validators, beside new issuance.
Multi-chainEthereumSolana+3Build Stargate Bridge Tracker: Volume, Pools and Bus vs Taxi on verified data.
Start free in Voltfin Studio: boards, tables and reports where every number opens its receipt. Tell us which data you need first and we will build it next.