# Wormhole Bridge Tracker: Messages, Token Transfers and NTT > Wormhole activity by route: cross-chain messages, Token Bridge and Native Token Transfers volume, wrapped tokens outstanding, delivery times and rate limits. Markdown copy of https://voltfincrypto.com/apps/wormhole-bridge-tracker **Question:** How many messages and how much token value move over Wormhole, on which routes and through which products? - Kind: Dashboard in Voltfin Vantage - Topic: [Layer 1 chains](https://voltfincrypto.com/topics/chains) - Chains: Multi-chain, Ethereum, Solana, Arbitrum, Base, BNB Chain, Sui, Aptos - Status: Planned. The data is not published yet, so this page states no figure; each figure will open its receipt when it is. Wormhole is a messaging protocol watched by nineteen guardians. A contract on one chain publishes a message through the Wormhole core contract; once at least thirteen guardians have signed it, the signed message, called a VAA, can be submitted on any other chain Wormhole supports, where it is checked against the current guardian set. Token transfers ride on these messages. Two products carry most of the token value. The Token Bridge locks a token on its home chain and mints a wrapped copy elsewhere. Native Token Transfers, or NTT, let a token's issuer move it in its own form, by burning and minting or by locking and minting, with rate limits the issuer sets. This dashboard counts both from the contracts, with every message keyed the way the guardians sign it. The 2022 exploit, in which a flaw in the Solana contracts let an attacker mint wrapped ETH that nothing backed, is why the dashboard also tracks wrapped supply beside what is locked. ## Blueprint ### Messages Messages and token value by route and product. - **Messages published** (count): Messages published through the Wormhole core contracts on covered chains in the selected period. - **Token value moved** (USD): Token value carried by Token Bridge and NTT transfers in the period, valued at the publish block. - **Guardians in the current set** (count): Keys in the guardian set currently stored in the core contracts, shown with the set's index. - **Median delivery time** (minutes): The median time from a transfer's publish block to its redemption block in the period. - **Messages by day and source chain** (count): Messages published each day, split by the emitting chain. - **Busiest routes**: Each route's messages, token value, product mix and median delivery time over the period. ### Tokens Wrapped supply, NTT tokens and their rate limits. - **Wrapped tokens outstanding** (USD): Supply of Token Bridge wrapped assets on covered chains at the latest day's end, valued at oracle prices. - **NTT tokens tracked** (count): Tokens deployed with Native Token Transfers on covered chains. - **Value by product** (USD): Token value moved in the period through the Token Bridge and through NTT. - **NTT tokens and their limits**: Each NTT token's mode, chains, outbound and inbound rate limits per chain and value moved in the period. Filters: Route (Every covered source and destination pair); Product (Token Bridge, NTT or all messages); Period (Last 7, 30 or 90 days). ## How it will be measured - Messages are LogMessagePublished events from the Wormhole core contract on each chain, keyed by emitter chain, emitter address and sequence, the same key the guardians sign, so each message counts once. - Deliveries are the destination transactions that verify a message's VAA, such as a Token Bridge redemption or an NTT receive, and the delivery time is the gap between the two blocks. - Token value comes from decoded Token Bridge and NTT transfer payloads, valued at oracle prices at the publish block; wrapped tokens outstanding are each wrapped asset's totalSupply at the day's last block. - NTT rate limits are read from each NTT Manager's inbound and outbound limits at the latest block, and the guardian set in force is read from the core contract. ## 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. - `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. - `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. - `address_labels` (to build): Labels for known addresses: exchanges, bridges, protocols, funds, treasuries, sanctioned addresses and known attackers. - Source: LogMessagePublished events of the Wormhole core contract on each covered chain - Source: Token Bridge transfer payloads and redemption events, and NTT Manager transfer and receive events - Source: totalSupply of Token Bridge wrapped assets and NTT tokens at each day's last block - Source: The guardian set stored in each core contract and NTT inbound and outbound rate limits ## Questions ### How does Wormhole work? A contract publishes a message through the core contract on its chain. Wormhole's nineteen guardians observe it, and once at least thirteen have signed, the signed message can be delivered to any chain Wormhole supports, where the core contract there verifies the signatures before the receiving app acts. ### Who are the Wormhole guardians? Nineteen validator operators that each run nodes for the chains Wormhole connects and sign the messages they observe. A message needs a supermajority of their signatures, and the set can be changed only through a message the guardians themselves sign. ### What is the difference between the Wormhole Token Bridge and NTT? The Token Bridge locks a token on its home chain and mints a wrapped copy, controlled by the bridge, on other chains. NTT lets the issuer deploy its own token on each chain and move it by burning and minting or by locking and minting, with its own rate limits and settings. ### What is the Wormhole Governor? A safety feature in the guardians' software that limits how much value can leave each chain in a day through the Token Bridge and delays very large transfers. It caps what a single flaw could take before people notice. ### Was Wormhole hacked? Yes. In February 2022 an attacker bypassed signature verification in Wormhole's Solana contracts and minted wrapped ETH with no ETH locked behind it. Jump Crypto replaced the missing ETH and the flaw was fixed. The bridge hacks table ranks this incident among the others. ## Glossary - **VAA**: A verified action approval: a Wormhole message carrying the guardians' signatures, which any chain's core contract can check. - **Guardian set**: The list of guardian keys whose signatures are valid at a given time, stored in the core contract on each chain. - **NTT**: Native Token Transfers, Wormhole's framework for moving an issuer's own token between chains without a wrapped copy. ## Related apps - [Biggest Bridge Hacks, Ranked by Losses and What Failed](https://voltfincrypto.com/apps/biggest-bridge-hacks) - [Bridged Token Backing: Locked vs Minted Supply](https://voltfincrypto.com/apps/bridged-token-backing) - [Chainlink CCIP Tracker: Cross-Chain Messages and Token Transfers](https://voltfincrypto.com/apps/chainlink-ccip-tracker) - [Pyth Price Updates: Feeds Pulled On-Chain by Chain and App](https://voltfincrypto.com/apps/pyth-network-price-updates) - [Hyperlane Tracker: Interchain Messages, Warp Routes and ISMs](https://voltfincrypto.com/apps/hyperlane-messages-warp-routes) - [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