# Stargate Bridge Tracker: Volume, Pools and Bus vs Taxi

> Stargate bridge activity on LayerZero: volume by route, bus and taxi transfers, pool liquidity on each chain, Hydra assets and the fees users pay per transfer.

Markdown copy of https://voltfincrypto.com/apps/stargate-bridge-tracker

**Question:** How much moves through the Stargate bridge on each route, by bus or by taxi, and how much liquidity backs it?

- Kind: Dashboard in Voltfin Vantage
- Topic: [Layer 1 chains](https://voltfincrypto.com/topics/chains)
- Chains: Ethereum, Arbitrum, Base, OP Mainnet, BNB Chain, Avalanche, Polygon, Mantle
- Status: Planned. The data is not published yet, so this page states no figure; each figure will open its receipt when it is.

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.

## Blueprint

### Transfers

Volume by route and mode, with what each mode costs.

- **Volume** (USD): Value transferred through Stargate in the selected period, valued at the send block.
- **Transfers** (count): Transfers delivered in the selected period.
- **Sent by bus** (%): Share of transfers in the period that rode a bus rather than a taxi.
- **Median fee** (USD): The median of protocol fees plus messaging cost per transfer in the period.
- **Volume by source chain** (USD): Value 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** (USD): Assets held in Stargate pools across covered chains at the latest day's end.
- **Hydra assets outstanding** (USD): Supply of Hydra assets on chains without a native pool, valued at oracle prices.
- **Liquidity by chain and asset** (USD): Pool 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.

Filters: Route (Every covered source and destination pair); Asset (USDC, USDT, ETH and the other pooled assets); Period (Last 7, 30 or 90 days).

## How it will be measured

- 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.

## Data it needs

- `bridge_flows_daily` (to build): Deposits into and withdrawals out of canonical and major third-party bridges by chain, token and day, plus escrow balances at day end.
- `defi_tvl_daily` (to build): Assets deposited in DeFi protocols per protocol, chain and asset at day end, valued with oracle prices, never double counting receipt tokens.
- `token_supply_daily` (to build): Total supply of each registry token on each chain at day end: wrapped BTC, liquid staking tokens, tokenized assets and other tracked tokens.
- `protocol_revenue_daily` (to build): Fees users paid to each protocol and the part kept by the protocol or its token holders, per protocol and day, including buybacks.
- `native_prices_daily` (to build): Reference prices of major assets read from on-chain oracle feeds (Chainlink latestRoundData) at each day's last block, with each round's update time.
- Source: Stargate pool and OFT sent and received events on each covered chain, with the LayerZero guid
- Source: Bus ride and bus drive events from Stargate's messaging contract
- Source: Pool balances and credits at each day's last block
- Source: totalSupply of Hydra assets on chains without a native pool

## Questions

### 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.

## Glossary

- **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 apps

- [LayerZero DVN Checker: Bridge Verifier Settings](https://voltfincrypto.com/apps/layerzero-dvn-checker)
- [Bridged Token Backing: Locked vs Minted Supply](https://voltfincrypto.com/apps/bridged-token-backing)
- [Across Protocol Bridge: Volume, Relayer Fees and Fill Times](https://voltfincrypto.com/apps/across-bridge-volume)
- [Wormhole Bridge Tracker: Messages, Token Transfers and NTT](https://voltfincrypto.com/apps/wormhole-bridge-tracker)
- [Cross-Chain Intents: Volume, Solvers and Fill Times](https://voltfincrypto.com/apps/cross-chain-intents-solvers)
- [Blockchain Revenue Rankings: Monthly League Table](https://voltfincrypto.com/apps/blockchain-revenue-rankings)

Build it in Voltfin Studio: https://app.voltfincrypto.com/signup?next=%2F