# Hyperlane Tracker: Interchain Messages, Warp Routes and ISMs

> Hyperlane activity by chain: messages dispatched and delivered, Warp Route token transfers, interchain gas paid and the security modules recipients use.

Markdown copy of https://voltfincrypto.com/apps/hyperlane-messages-warp-routes

**Question:** How many messages move over Hyperlane, which Warp Routes carry tokens and what security do they rely on?

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

Hyperlane is a permissionless interoperability protocol: anyone can deploy its Mailbox contract to a new chain and connect it without asking anyone. A sender dispatches a message through the Mailbox on the origin chain, a relayer delivers it to the destination Mailbox and the recipient's Interchain Security Module decides whether the message is valid, for example by checking signatures from a set of validators.

Because each recipient chooses its own security, two routes on Hyperlane can trust very different things. This dashboard counts messages and their delivery from both Mailboxes and follows Warp Routes, the token bridges built on Hyperlane. It also reads the security module each recipient used at delivery, so the share of traffic on each kind of module is measured.

## Blueprint

### Messages

Dispatch and delivery by route.

- **Messages dispatched** (count): Messages dispatched through Hyperlane Mailboxes on covered chains in the selected period.
- **Messages delivered** (count): Messages processed by destination Mailboxes in the selected period.
- **Chains connected** (count): Chains whose Mailbox sent or received at least one message in the period.
- **Median delivery time** (minutes): The median time from dispatch block to process block across delivered messages.
- **Messages by day and origin chain** (count): Messages dispatched each day, split by origin chain.
- **Busiest routes**: Each route's messages dispatched and delivered, median delivery time and gas prepaid over the period.

### Routes and security

Warp Routes and the modules their recipients trust.

- **Warp Routes active** (count): Warp Routes with at least one transfer in the selected period.
- **Messages on the default module** (%): Share of delivered messages whose recipient relied on the Mailbox's default security module.
- **Messages by module type** (count): Delivered messages grouped by the recipient's module type: multisig, aggregation, routing or other.
- **Warp Routes and their security**: Each route's token, route type, chains, module type, value moved in the period and its validators and threshold.

Filters: Route (Every covered origin and destination pair); Period (Last 7, 30 or 90 days).

## How it will be measured

- Messages are Dispatch events from each chain's Mailbox, matched by message id to the Process event on the destination Mailbox, so delivery is measured from both ends and undelivered messages stay visible.
- Each recipient's security module is read from the destination Mailbox with recipientIsm() at the delivery block, and multisig modules are read for their validator set and threshold.
- Warp Route transfers are the amounts in each route's transfer messages, valued at oracle prices at dispatch, with collateral, synthetic and native routes kept apart so a locked token and its minted copy are never added together.
- Gas payments are the Interchain Gas Paymaster's GasPayment events for each message, which show what senders prepaid for delivery.

## 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: Mailbox Dispatch and DispatchId events on each covered chain, and Process and ProcessId events on destinations
- Source: recipientIsm() and multisig module validators and thresholds at each delivery block
- Source: Warp Route transfer and receive events and totalSupply of synthetic route tokens
- Source: Interchain Gas Paymaster GasPayment events

## Questions

### What is Hyperlane?

An interoperability protocol that lets contracts on different chains send each other messages. Its contracts can be deployed to any chain by anyone, and each app chooses how incoming messages are verified.

### What is an Interchain Security Module?

The contract a Hyperlane recipient uses to decide whether a delivered message is valid. Common kinds check signatures from a set of validators, combine several modules or route to different modules by origin. A recipient that sets none uses the Mailbox's default module.

### What is a Hyperlane Warp Route?

A token bridge built on Hyperlane messages. A collateral route locks a token on one chain, a synthetic route mints a representation on another and native routes move a chain's gas token. Each route uses its own security module.

### Why does the default security module matter?

A recipient that does not choose a module inherits the Mailbox's default, which the Mailbox owner can change. Messages on the default therefore trust whoever controls that setting, and the dashboard shows how much traffic relies on it.

### What is the HYPER token?

Hyperlane's token, launched in 2025. Holders can stake it to provide economic security for Hyperlane validators. The dashboard measures messages and transfers, not the token's market.

## Glossary

- **Mailbox**: The Hyperlane contract on each chain that dispatches outgoing messages and processes incoming ones.
- **ISM**: Interchain Security Module: the contract a recipient uses to verify that a delivered message really was sent.
- **Warp Route**: A Hyperlane token bridge that locks, mints or moves a token between chains using Hyperlane messages.

## 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)
- [Wormhole Bridge Tracker: Messages, Token Transfers and NTT](https://voltfincrypto.com/apps/wormhole-bridge-tracker)
- [Axelar Network: GMP Calls, Interchain Tokens and Validators](https://voltfincrypto.com/apps/axelar-gmp-interchain-tokens)
- [Chainlink CCIP Tracker: Cross-Chain Messages and Token Transfers](https://voltfincrypto.com/apps/chainlink-ccip-tracker)
- [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