MUSD, a Bitcoin-backed stablecoin and the flagship product of the Mezo ecosystem, has surpassed $750 million in lifetime transaction volume. The stablecoin now operates natively across Mezo, Ethereum, and Base through Wormhole's cross-chain infrastructure, representing a significant milestone for Bitcoin DeFi — a sector that has grown as projects such as Stacks, Babylon, and others work to unlock Bitcoin's substantial but historically idle capital base for productive use in decentralized finance.

According to protocol data, MUSD recorded approximately $789 million in transaction volume during the first half of 2026 alone and has amassed roughly 41,000 holders.

How MUSD Works

MUSD functions on a collateralized debt position (CDP) model. Users deposit Bitcoin as collateral and mint dollar-denominated stablecoins against it — a mechanism comparable to MakerDAO's DAI, but with Bitcoin serving as the underlying asset rather than Ethereum. While fiat-backed stablecoins like Tether's USDT and Circle's USCC dominate the market by supply, crypto-collateralized alternatives offer different risk and transparency properties, and MUSD extends that category to the largest cryptocurrency by market capitalization.

The protocol permits loan-to-value ratios of up to approximately 90%, with over-collateralization exceeding 110%. This means that for every dollar of MUSD in circulation, more than $1.10 worth of Bitcoin backs it. As of mid-2026, approximately 913 BTC are locked as collateral within the Mezo ecosystem.

Mezo launched its mainnet alongside MUSD on May 28, 2025. The Wormhole integration followed on August 4, 2025, introducing what the protocol calls Native Token Transfers (NTT) — a burn-and-mint mechanism that enables MUSD to move between chains without the liquidity fragmentation typically associated with bridged assets.

Wormhole Integration and Cross-Chain Functionality

Wormhole's NTT standard employs a burn-and-mint approach. When MUSD transfers from Mezo to Ethereum, tokens are burned on the origin chain and minted natively on the destination chain. No wrapped versions or intermediary liquidity pools are involved. The MUSD on Base is identical to the MUSD on Ethereum.

This design has practical implications for DeFi composability. A stablecoin that exists natively on Ethereum and Base can integrate directly with existing lending, trading, and yield infrastructure on those chains without requiring custom integrations for wrapped variants. MUSD holders gain access to Ethereum's deep liquidity pools and Base's low-fee environment while remaining within the same stablecoin ecosystem. Expanding to additional chains and securing integrations with major DeFi protocols on Ethereum and Base would be key indicators of whether MUSD's growth trajectory continues.

Market Position and Risk Profile

While MUSD's lifetime volume does not currently challenge Tether's market dominance, its growth trajectory is notable. Reaching over $750 million roughly one year after mainnet launch — with the majority of volume concentrated in the first half of 2026 — points to sustained adoption rather than an isolated surge.

The 41,000-holder count represents a substantial user base for a protocol that has been operational for just over a year, suggesting organic demand rather than volume driven primarily by incentive farming or wash trading.

The 913 BTC locked as collateral reflects user confidence in the system. Depositing Bitcoin into a smart contract requires trust in both the code and the economic design. The over-collateralization requirement above 110% provides a buffer against liquidation cascades, though it also makes the system less capital-efficient than centralized alternatives — a deliberate trade-off prioritizing safety over leverage.

Risk factors remain present. CDP-based stablecoins depend heavily on the reliability of their liquidation mechanisms. A significant decline in Bitcoin's price could trigger cascading liquidations that stress the stablecoin's peg. Additionally, the Wormhole integration introduces bridge-layer risk that would not exist in a single-chain deployment, and cross-chain messaging protocols have historically been targets of exploits — a consideration relevant to any asset relying on inter-chain infrastructure.