Bridged tokens tracked
countPairs of bridged token and bridge checked at the latest day-end block.
Dashboard · VantagePlanned
Bridged Token Backing: Locked vs Minted Supply
Is each bridged token's supply on other chains matched by tokens locked on its home chain right now?
Whether each bridged token's supply on other chains is matched by tokens locked on its home chain, with every gap shown.
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.
Overview
Backing across every tracked token and where the gaps are.
Tokens with a shortfall
countPairs whose locked supply, after in-flight transfers, is below their minted supply at the latest read.
Largest shortfall
%The largest gap between minted and locked supply as a share of minted supply, and the token it belongs to.
In flight now
USDThe value of bridge transfers started but not yet completed across every tracked pair at the latest read.
Backing by token and bridge
For each token and bridge: home chain, minted supply on each chain, locked supply, the in-flight amount and the backing ratio, with both blocks.
One token
Locked against minted supply for a chosen token over time.
Backing ratio
ratioLocked supply divided by minted supply for the chosen token at the latest read, after in-flight transfers.
Gap in tokens
tokensMinted supply minus locked supply for the chosen token, in token units, after in-flight transfers.
Minted supply by chain
Where the chosen token's bridged supply sits, by chain, at the latest read.
Locked vs minted over time
tokensThe home-chain escrow balance and the total minted supply of the chosen token at each day-end block.
- Token
- Every tracked bridged token
- Period
- Last month, quarter or year
About
What it answers, and for whom.
A lock-and-mint bridge holds tokens on their home chain and issues the same amount on another chain. If the bridge is exploited or misconfigured, it can mint copies that nothing backs. This dashboard compares, token by token, the supply minted on other chains with the balance locked on the home chain at matching blocks, then shows the gap.
A small gap is normal while transfers are in flight: a deposit is locked before it is minted, and a withdrawal is burned before it is released. The dashboard separates those pending amounts from the rest, so a gap that persists or grows stands out.
It covers canonical rollup bridges, LayerZero OFT adapters and other lock-and-mint designs for major tokens. Each comparison names both blocks and both reads, so a reader can check the backing for themselves.
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 →- Minted supply is totalSupply() of each bridged representation on each chain at the last block of the day; locked supply is balanceOf the escrow, lockbox or adapter contract on the home chain at the matching block.
- Backing is locked supply divided by minted supply summed across chains. A ratio below one, after in-flight transfers are accounted for, is a shortfall.
- In-flight amounts are bridge transfers that have started but not finished: withdrawals initiated but not yet finalized, deposits locked but not yet minted and OFTSent messages without a matching OFTReceived.
- Burn-and-mint tokens have no escrow; for them the check matches each mint on one chain to a burn on another, and compares the cross-chain total with the issuer's supply.
- USD values use Chainlink feeds at the same block, and every gap is shown in token units first, so a price never hides a shortfall.
The data it needs
Read from chain state and history
- 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.
- 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.
- 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.
- totalSupply() of bridged representations on each chain at day-end blocks
- balanceOf of the lockbox, OFT adapter or canonical bridge escrow on the home chain at the matching block
- Bridge events: OFTSent and OFTReceived, ERC20DepositInitiated and DepositFinalized, WithdrawalInitiated and ERC20WithdrawalFinalized
- A registry pairing each bridged token with its home token, escrow contract and bridge design
- Chainlink feeds at the same blocks for USD values
Questions
Questions people ask.
What is a bridged token?
A token on one chain that stands for a token whose home is another chain. In a lock-and-mint design the original sits in an escrow contract on the home chain while the copy circulates elsewhere, so the copy is only as good as that escrow.
What makes a bridged token unbacked?
Copies minted without a matching amount locked on the home chain. It happens when a bridge's verification is bypassed, a key is compromised or a bug lets someone mint freely. Holders of the copies then share a claim on less than they hold.
Why is there sometimes a small gap?
Bridging takes time. Deposits are locked first and minted once the message arrives; withdrawals from optimistic rollups are burned first and released only after the challenge period. The dashboard shows those in-flight amounts on their own line.
Does full backing mean a bridge is safe?
No. Backing shows that the escrow holds enough today. It says nothing about who can move the escrow, how messages are verified or whether the contracts can be upgraded; the LayerZero DVN checker and the contract upgrade tracker cover some of those risks.
- Lock and mint
- A bridge design that locks tokens in an escrow on the home chain and mints the same amount on another chain.
- Burn and mint
- A design with no escrow: tokens are burned on one chain and minted on another, so supply moves rather than being copied.
- Lockbox
- The escrow contract that holds home-chain tokens for an omnichain token, such as a LayerZero OFT adapter.
- In-flight transfer
- A bridge transfer that has started on one chain and not yet completed on the other.
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+5Ethereum L2 TVL: Value Locked in Rollup Bridges
Value on each Ethereum layer 2, split into its canonical bridge on Ethereum, other bridges and tokens minted natively on the layer 2.
Multi-chainEthereumBase+6Wrapped Bitcoin Supply by Chain and Issuer
Every wrapped BTC token on EVM chains, its supply by chain and issuer each day, its custody model and the bitcoin reserves behind it.
Multi-chainEthereumBase+4Liquid Restaking Tokens: Backing and Exchange Rates
Whether weETH, rsETH, ezETH and other liquid restaking tokens hold the assets they claim, where that backing sits and how rates moved.
EthereumArbitrumBase+1Proof of Reserves Tracker: Exchange Wallet Balances
What exchanges hold in the reserve wallets they publish, chain by chain, read at each day's last block beside what they report owing.
Multi-chainBitcoinEthereum+1Ethereum TPS: Mainnet and Layer 2 Transactions per Second
Transactions and gas per second on Ethereum and each layer 2, in total and per chain, counted from blocks without system transactions.
Multi-chainEthereumBase+6Build Bridged Token Backing: Locked vs Minted Supply 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.