Dashboard · VantagePlanned

Wrapped Bitcoin Supply by Chain and Issuer

How much wrapped bitcoin exists on each EVM chain, and which tokens make it up?

Every wrapped BTC token on EVM chains, its supply by chain and issuer each day, its custody model and the bitcoin reserves behind it.

ShareEmail itvoltfincrypto.com/apps/wrapped-bitcoin-supply-by-chain
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.

  • Chain
  • Period

Supply

Wrapped BTC supply by chain and token on the latest complete day.

Wrapped BTC on covered chains

BTC

Native supply of every wrapped BTC token on the covered chains on the latest complete day, each bitcoin counted once.

Figuretoken_supply_dailyAwaiting data

Largest token's share

%

The share of total native wrapped supply held in the largest single token, which the tile names.

Figuretoken_supply_dailyAwaiting data

Tokens tracked

count

Wrapped BTC tokens in the registry with a non-zero supply on at least one covered chain.

Figuretoken_supply_dailyAwaiting data

30-day change

%

Change in total native wrapped supply against the same chains 30 days earlier.

Figuretoken_supply_dailyAwaiting data

Supply by chain

BTC

Native wrapped supply per chain on the latest day, split by token.

Stacked barstoken_supply_dailyAwaiting data

Supply by custody model

BTC

Total native wrapped supply by custody model: single custodian, several custodians, threshold signers or staking protocol.

Donuttoken_supply_dailyAwaiting data

Every token on every chain

Each token on each chain with its supply, native or bridged status, issuer, custody model, holders and the issuer's published reserves where they exist.

Tabletoken_holders_snapshotAwaiting data

Mints and burns

Tokens minted and burned, and how each token's supply moved.

Minted, 30 days

BTC

Wrapped BTC minted over the last 30 days, from Transfer events from the zero address, all tokens together.

Figuretoken_transfers_dailyAwaiting data

Burned, 30 days

BTC

Wrapped BTC burned over the last 30 days, from Transfer events to the zero address, all tokens together.

Figuretoken_transfers_dailyAwaiting data

Supply by token over time

BTC

Native supply per token by day over the selected period, for the chain selected.

Stacked areatoken_supply_dailyAwaiting data

Chain
Every covered EVM chain, or all of them together
Period
Last 30 days, last 90 days or last year
About

What it answers, and for whom.

The wrapped bitcoin on each EVM chain is read here from every wrapped BTC token contract at each day's last block: WBTC, cbBTC, tBTC, LBTC and the others, with each chain's total built from the tokens that make it up. It shows how much bitcoin is represented on Ethereum, Base, Arbitrum, BNB Chain and Avalanche, and which issuers stand behind it.

The tokens differ in who holds the bitcoin behind them: a single custodian, a group of custodians, a decentralized signer set or a staking protocol. The dashboard tags each token with its custody model. Where an issuer publishes its Bitcoin addresses, their balance at the same day's end is read on Bitcoin and set beside the token's supply.

Bridged copies are kept apart from native issuance. A token bridged from Ethereum to another chain is backed by tokens locked in the bridge, so adding both chains' supply would count the same bitcoin twice; the dashboard counts each bitcoin once and shows bridged copies as their own series.

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 →
  1. Supply is each token contract's totalSupply() at the last block of each UTC day on every covered chain, scaled by its decimals and kept as an exact amount.
  2. Each token is classed as native issuance or a bridged copy on each chain, and totals add native issuance only, so bitcoin locked in a bridge is never counted twice.
  3. Mints and burns are Transfer events from and to the zero address, summed by token, chain and day.
  4. Where an issuer publishes custody addresses on Bitcoin, their balance at the day's last Bitcoin block is shown beside the token's native supply.
  5. Each token's custody model comes from its issuer's own documentation, recorded with its source.

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.
  • token_transfers_dailyTo buildToken transfer volumeERC-20 and native transfer counts, volume and unique senders and receivers per token per chain per day.
  • token_holders_snapshotTo buildToken holders and concentrationHolder counts, top holders and concentration shares of registry tokens at a pinned block, with contract and exchange labels.
  • 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.
  • address_labelsTo buildAddress labelsLabels for known addresses: exchanges, bridges, protocols, funds, treasuries, sanctioned addresses and known attackers.
  • totalSupply() at day-end blocks of WBTC, cbBTC, tBTC, LBTC, SolvBTC, FBTC, BTCB and BTC.b on each chain they are issued on
  • ERC-20 Transfer logs from and to the zero address, for mints and burns
  • A registry of wrapped BTC contracts per chain, with issuer, custody model and native or bridged status
  • Balances of issuer-published custody addresses on Bitcoin at the day's last block
  • Bridge escrow balances of wrapped BTC tokens, from balanceOf at day-end blocks
Questions

Questions people ask.

What is wrapped bitcoin?

A token on another chain that represents bitcoin held elsewhere, so bitcoin can be used in that chain's applications. Whoever holds the bitcoin, a custodian, a signer group or a protocol, mints tokens when bitcoin is deposited and burns them when it is redeemed.

What is the difference between WBTC, cbBTC and tBTC?

They differ in custody. WBTC is minted through merchants against bitcoin held by its custodians; cbBTC is issued by Coinbase against bitcoin in its custody; tBTC is backed by bitcoin held by a rotating group of signers on the Threshold network. The dashboard tags each token with its model.

Is wrapped bitcoin safe?

It carries risks that bitcoin itself does not: the custodian or signers could fail or be compromised, the token contract has admin powers and bridged copies add bridge risk. The dashboard shows each token's custody model and, where possible, its reserves, but it does not rate safety.

Why not just add up wrapped BTC on every chain?

Because some of it is the same bitcoin. When a token moves from Ethereum to another chain through a bridge, the original tokens stay locked on Ethereum and a copy is minted on the other chain. Adding both would count the locked tokens twice, so totals use native issuance and show bridged copies apart.

How much bitcoin is on Ethereum?

The dashboard's Ethereum total adds the native supply of every wrapped BTC token issued on Ethereum, read from each contract at the day's last block. It counts each token once, and the table below it shows the tokens that make it up.

Native issuance
Tokens minted on a chain directly by their issuer against deposited bitcoin, as opposed to copies bridged in from another chain.
Bridged copy
A token minted on one chain against the same token locked in a bridge on another, so it adds no new bitcoin backing.
Custody model
Who holds the bitcoin behind a token and how: one custodian, several custodians, a threshold signer group or a staking protocol.
Proof of reserves
Published custody addresses or attestations that let anyone compare the bitcoin held with the tokens issued.

Build Wrapped Bitcoin Supply by Chain and Issuer 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.