Cap, the stablecoin protocol behind cUSD and stcUSD, has integrated LayerZero’s OVault standard to enable cross-chain deposits and minting across four blockchain networks. Users can now interact with a single central hub vault from Ethereum, Tempo, MegaETH, and Katana, sidestepping the fragmented liquidity problem that has plagued multi-chain DeFi for years.
How the plumbing works
Traditional multi-chain deployments require protocols to spin up individual vaults on every supported network, each needing its own liquidity, security monitoring, and maintenance. OVault collapses that into a single vault that communicates across chains through LayerZero’s messaging infrastructure.
For Cap specifically, this means users minting cUSD or stcUSD no longer need to bridge assets manually before depositing. The process happens in one step, with the cross-chain routing handled under the hood. cUSD is minted on a 1:1 basis against blue-chip dollar assets, while stcUSD serves as its yield-bearing staked counterpart.
Cap’s operational model has three layers: users who mint stablecoins at par value, operators who borrow those assets to deploy yield-generation strategies, and delegators who restake with smart contract compliance enforcing the rules.
LayerZero’s OVault standard itself launched in September 2025 and reportedly secured approximately $9 billion in assets on its first day.
Cap’s multi-chain trajectory
Cap first extended to MegaETH on January 5, 2026, using LayerZero’s OFT bridging to support real-time operations for both cUSD and stcUSD. At the time of that launch, Cap reported a total value locked exceeding $400 million and a circulating supply of more than $350 million for cUSD.
Cross-chain messaging layers add complexity, and complexity is where exploits tend to hide. LayerZero’s infrastructure has been battle-tested to a degree, and the $9 billion secured by OVault on launch day suggests meaningful confidence from the market. But any system that routes value across multiple chains introduces attack surface that wouldn’t exist in a single-chain deployment.