Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
Bridged TVL counts crypto locked in bridge contracts — not assets deployed in DeFi protocols. Here's how the metric works, why platforms disagree, and what it actually tells you about a chain.
Bridged TVL (bridged total value locked) is the dollar value of crypto assets locked inside bridge smart contracts — the escrow mechanism that holds your tokens on one blockchain while a wrapped equivalent is minted on another.
The number shows up prominently on DefiLlama’s /bridged page and inside L2BEAT’s TVS breakdown. It is frequently confused with a chain’s main TVL figure. Both metrics measure value in crypto. Both update in real time. But they count completely different things — and mixing them up leads to badly wrong chain comparisons. This guide explains what bridged TVL actually measures, why the platforms disagree, and what the number really tells you about a chain’s health.
—
When you move ETH from Ethereum to Arbitrum, the ETH does not actually travel. It gets locked in a bridge smart contract on Ethereum L1 — held in escrow. The bridge then mints a wrapped IOU, WETH, in your wallet on Arbitrum. That locked ETH is what bridged TVL counts.
The wrapped WETH sitting in your Arbitrum wallet is not in bridged TVL. And if you leave it in your wallet without deploying it into a protocol, it is also not in DefiLlama’s Arbitrum TVL — because DefiLlama counts assets actively used in dApps, not idle tokens. Only when you put WETH to work in, say, a Uniswap liquidity pool on Arbitrum does the asset start counting toward the chain’s DeFi TVL.
That gap creates a real misconception. A chain can have $8B in bridged TVL and $1.5B in DeFi TVL at the same time — because most of the bridged capital is sitting idle in wallets, not deployed. Bridged TVL measures what crossed the bridge, not what is working in the destination chain’s applications.
The table below shows the dividing line clearly.
| What Bridged TVL Counts | What DefiLlama Protocol TVL Counts |
|---|---|
| ETH locked in bridge contract on Ethereum L1 | WETH deployed in Uniswap pool on Arbitrum |
| USDC locked in bridge escrow | USDC supplied in an Aave lending pool |
| Any asset sitting in bridge contract, active or idle | Assets actively used in a dApp on the destination chain |
| Assets waiting to be withdrawn back to L1 | None — withdrawn assets exit TVL immediately |
When you see a large bridged TVL number, the more useful question is: how much of this capital is actually deployed? The raw number tells you how much crossed the bridge — nothing more.
—
L2BEAT, the primary analytics platform for Ethereum Layer 2s, breaks bridged TVL into three categories when computing TVS (Total Value Secured). Each category carries a different risk profile, and each appears as its own line in the L2BEAT breakdown for a given chain.
Most users see three numbers on L2BEAT and assume they all measure the same thing. They do not.
| Asset Type | What It Means |
|---|---|
| Canonically bridged | Assets locked on Ethereum L1 using the L2’s own official bridge (e.g., ETH in Arbitrum’s canonical bridge). Carries the L2’s native bridge contract risk. |
| Externally bridged | Assets brought from another chain via a third-party bridge, not the canonical L2 bridge. Different risk profile — relies on the security of the external bridge protocol. |
| Natively minted | Tokens created directly on the L2 — for example, ARB on Arbitrum or OP on OP Mainnet. These are not bridged at all. They were never on Ethereum L1. |
L2BEAT’s TVS figure is the sum of all three categories. That is why TVS can look dramatically higher than DefiLlama TVL for the same chain — TVS includes canonical bridge escrow plus external bridge escrow plus natively minted tokens in circulation, while DefiLlama counts only what is deployed in tracked protocols.
Natively minted tokens deserve a brief note. ARB and OP are counted by L2BEAT because they are the L2’s own tokens, and the platform includes their market cap in the total value the L2 is securing. But they carry no bridge risk — they are simply native assets that did not cross a bridge to arrive. Knowing the split between canonical bridged, external bridged, and native helps you understand how much of a chain’s TVS is actually sitting in bridge contracts and how much is just local token supply.
—
Put 1 ETH into the Arbitrum bridge. The moment the transaction confirms on Ethereum, L2BEAT counts it in Arbitrum’s TVS. Your ETH is now in the bridge contract escrow.
DefiLlama does not count it yet. Your WETH sits in your Arbitrum wallet. It is idle. DefiLlama tracks active protocol usage, and an asset in a wallet is not being used in a protocol. The moment you supply that WETH to Uniswap on Arbitrum, DefiLlama adds it to Arbitrum’s TVL. When you withdraw from Uniswap but keep the WETH on Arbitrum, DefiLlama removes it. L2BEAT keeps counting it both times, because the ETH is still in the bridge contract.
Neither platform is wrong. They answer different questions.
The first table below shows what each platform measures. The second shows what each platform excludes.
| Platform | What It Measures |
|---|---|
| L2BEAT TVS | All assets secured by L2 bridge contracts: canonical, external, and natively minted |
| DefiLlama TVL | Assets actively deployed in tracked dApps on the destination chain |
| Platform | What It Excludes |
|---|---|
| L2BEAT TVS | Assets deployed within dApps — it measures the bridge security surface, not protocol usage |
| DefiLlama TVL | Bridged assets sitting idle in wallets and assets in bridge escrow on L1 |
Use L2BEAT when you are evaluating the security or trust surface of an L2. Use DefiLlama when you are comparing DeFi activity between chains. Never put an L2BEAT TVS figure next to a DefiLlama TVL figure as if they are the same number — that is a methodologically invalid comparison.
This platform gap explains nearly every “why does Chain A show $10B on L2BEAT but only $3B on DefiLlama” question you see in DeFi forums.
—
A spike in bridged TVL for a chain is almost always a conversation-starter, not a verdict. The signal depends entirely on what is driving it.
Rising bridged TVL can mean multiple things at once. Capital from other chains is flowing in because the destination chain has compelling yield, applications, or a token incentive program. Arbitrum’s 700M ARB incentive program and Sui’s $500M liquidity initiative both produced large, rapid rises in bridged TVL — followed by partial outflows once the most attractive incentive periods ended. Capital that arrives to capture rewards is mercenary: it rotates out when something better appears elsewhere, which is covered in our guide to crypto capital rotation.
The useful pairing is bridged TVL trend vs. protocol fee revenue. If bridged TVL is rising but fees on the chain are flat or declining, the incoming capital is not generating real activity. It is sitting in pools chasing incentives, not generating the transaction volume that healthy DeFi activity produces.
Here are the main signals to watch:
Post-exploit collapses are the starkest case. Ronin Network’s bridged TVL fell roughly 95% after the $625M hack in March 2022 and has not recovered to anything close to its pre-hack level. Capital flight after a security event is not rotation — it is an exit, and the chart shows a different shape than normal cycle outflows.
For anyone evaluating a destination chain, yield farming activity is the best companion metric. If bridged capital is flowing in and being deployed in farms, that is a stronger health signal than a bridged TVL number sitting in isolation.
—
Here is a scenario that inflates apparent TVL without anyone doing anything fraudulent.
You bridge $100M in ETH from Ethereum to Polygon. The ETH locks in the bridge contract on Ethereum. Bridged TVL registers $100M. Polygon mints $100M in wrapped ETH (WETH). A DeFi user takes that WETH and supplies it to a lending protocol on Polygon. DefiLlama counts the $100M in the Polygon TVL. Now $200M appears to exist in DeFi aggregate statistics, but the underlying capital is still the original $100M.
Academic research on TVL double-counting measured the size of this gap at peak. During the DeFi peak in December 2021, the gap between aggregate TVL and true underlying TVR (total value at risk) reached approximately $139.87B, representing a TVL-to-TVR ratio of roughly 2x. Half the TVL number in that period was effectively the same capital counted twice.
Better-designed dashboards reduce this. DefiLlama, for example, strips borrowed assets from its TVL calculation — if you borrow ETH against your USDC, DefiLlama does not double-count the borrowed ETH. But the risk is structural when bridged assets flow into heavily recursive DeFi activity on destination chains.
Intent-based bridges are a newer architecture that reduces the problem at the source. Protocols like Across and deBridge do not hold assets in large bridge contract escrows. Operators (called “relayers” or “solvers”) front liquidity for users and are later reimbursed. Very little capital ever sits in a bridge contract — bridge TVL for these protocols is minimal compared to their actual transaction volume. This design also means the double-counting risk that comes from large bridge escrow balances is substantially reduced.
Understanding this double-counting dynamic is also relevant to the exit liquidity risk that surfaces when inflated TVL numbers mislead users into believing a chain or protocol has more backing than it actually does.
—
Bridged TVL is, from a security standpoint, a target. The higher the number, the larger the prize for anyone who finds a vulnerability in the bridge smart contracts that hold those assets.
The 2022 bridge hack wave made this concrete. The Ronin Bridge exploit in March 2022 drained $625M — at the time, the second-largest hack in crypto history. The Wormhole exploit in February 2022 took $320M. Both were audited bridge protocols. Both had meaningful TVL tracked in real time before the exploits. That TVL was not a signal of safety — it was the honeypot. By March 2026, total bridge TVL across DeFi had reached $21.94B, making bridges the single highest-value point of failure in the sector.
Two contrasting models:
When you see a chain with high bridged TVL, the useful question is not just “how much is locked?” but “what bridge model is securing it?” A $2B TVL secured by a three-year-old canonical bridge that has been stress-tested through multiple exploit attempts is a different risk profile from a $2B TVL in a newly launched third-party bridge with one audit and six months of mainnet history.
Bridged TVL measures total value at rest in bridge contracts. It does not measure how safe those contracts are, how long they have been running, or whether they have been independently audited more than once. Always pair bridged TVL with the bridge’s security credentials before drawing any conclusions about chain safety.
—
Three platforms give you meaningfully different views of the same underlying phenomenon. Using all three together gives a much clearer picture than any one alone.
The sources, with their primary use cases:
The single most common mistake when reading chain marketing materials is accepting “X billion TVL” at face value without asking which platform produced the number. A chain citing L2BEAT TVS and a chain citing DefiLlama TVL are not comparable — the L2BEAT number will almost always be significantly higher because it includes bridge escrow that DefiLlama excludes.
The second mistake is comparing L2BEAT TVS for one chain against DefiLlama TVL for a different chain. That comparison makes the L2BEAT chain appear far more active than the DefiLlama chain even if actual activity levels are similar.
The CryptoProcent guides section covers the mechanics, risks, and metrics that matter across DeFi — useful if you want to keep building on what bridged TVL taught you.
—
Bridged TVL (bridged total value locked) is the dollar value of crypto assets sitting inside bridge smart contracts — the escrow that holds your tokens on one blockchain while a wrapped version is minted on another. It measures cross-chain liquidity at rest, not assets actively deployed in DeFi protocols. You can track it on DefiLlama’s bridges page and inside L2BEAT’s TVS breakdown for individual L2s.
Regular TVL on DefiLlama counts assets actively used in DeFi protocols — lending pools, DEX liquidity, yield farms. Bridged TVL counts assets sitting inside bridge contracts, whether or not those assets are being used anywhere. ETH that you bridge to Arbitrum and leave in your wallet raises bridged TVL by the full amount but adds nothing to Arbitrum’s DeFi TVL until you actually deposit it into a protocol.
Yes, in two ways. First, double-counting: the same ETH locked in a bridge contract on Ethereum and the wrapped version deployed on Polygon can both appear in aggregate TVL figures, inflating the apparent total. During the DeFi peak of December 2021, research found the gap between aggregate TVL and true underlying capital reached approximately $139.87B. Second, incentive bootstrapping: foundations have used large liquidity mining programs to attract bridged capital that leaves when incentives end. Neither is fraud, but both make raw bridged TVL an incomplete signal without context on methodology and incentive status.
Different methodologies. DefiLlama counts assets actively deployed in tracked dApps. L2BEAT counts all assets secured by the L2 bridge — including tokens that are sitting idle in wallets after being bridged. A user who bridges ETH to Arbitrum and does nothing shows up in L2BEAT’s TVS but not in DefiLlama’s Arbitrum TVL. Neither number is wrong. They answer different questions. Use L2BEAT for security and trust comparisons, and DefiLlama for DeFi activity comparisons.
Context determines everything. A rising bridged TVL driven by organic app growth and fee revenue is a positive signal — capital is arriving because the chain is useful. A spike driven by token incentives is worth scrutinizing: once incentives end, mercenary capital tends to leave quickly. From a safety standpoint, high bridged TVL also means more assets concentrated in bridge contracts — a reality the Ronin ($625M) and Wormhole ($320M) hacks in 2022 made clear. Use bridged TVL as one data point in a broader chain health assessment, not a standalone verdict.
—
Bridged TVL is useful only if you know what question it is answering. Most chain comparisons go wrong because someone pulls one number from L2BEAT and compares it to a different number from DefiLlama — often without realizing the two platforms measure entirely different things. The steps below give you a repeatable process for reading bridged TVL correctly.
Start with the methodology gap, then layer in the bridge composition and the fee data. That sequence lets you distinguish organic chain growth from incentive-driven inflows before you draw any conclusions.
Here are four concrete steps:
The most telling number is not the raw bridged TVL figure — it is the ratio between bridged TVL and actual protocol fee revenue. A chain running $5B in bridged TVL with $500K in monthly fees is very different from one with the same TVL and $10M in fees. The first is probably sitting on incentive capital. The second is earning it.