LayerZero and Keeta Bring Tokenized Bank Deposits On-Chain

Tokenized bank deposits are getting serious infrastructure behind them. LayerZero Labs, the interoperability protocol connecting over 170 blockchains, and Keeta, a regulated payment and settlement platform, announced a partnership to bring commercial bank deposits on-chain across Ethereum, Solana, Base, and the Keeta Network. Using LayerZero's Omnichain Fungible Token standard, the system lets institutions issue and transfer bank-backed tokens across multiple public blockchains, no wrapped assets required, no external liquidity pools, and no stablecoin-style reserve structure standing between the token and the actual deposit.

What LayerZero and Keeta Are Actually Building

The architecture is simpler than most cross-chain value transfer systems, which is the whole point. Bivo, a payment rail and banking network, sits between the regulated bank account and the on-chain token. Institutions issue their commercial bank deposits through Bivo onto the supported networks. Each token represents money held directly as a commercial bank deposit, not a pooled reserve, not collateral in a smart contract. That distinction separates this from every major stablecoin on the market today.

LayerZero connects over 170 blockchains via its interoperability protocol, giving this setup broad distribution reach before a single institution has signed on. Keeta brings the settlement layer and the compliance controls. Bivo connects the actual banking rails. The three-party structure is designed to let regulated financial institutions stay in control without requiring them to directly touch crypto-native infrastructure.

For treasury teams managing funds across multiple chains, the practical benefit is concrete: one consistent view of token supply, no fragmented balances scattered across networks, no reconciliation problems from multiple token versions sitting on different chains.

How Does the OFT Standard Work for Bank Deposit Transfers?

LayerZero's Omnichain Fungible Token framework is what makes consistent cross-chain supply possible. When an institution moves a tokenized deposit from Ethereum to Solana, the token on Ethereum is burned at the contract level. A new token mints on Solana. Total supply stays constant and is readable directly from the contracts across every supported chain, with no external oracle required to verify it.

That burn-and-mint design matters more for regulated finance than it does for a typical DeFi protocol, where a supply discrepancy might be a technical nuisance but rarely triggers an audit finding or regulatory review that puts a banking license at risk. Banks and treasury departments carry strict auditability obligations. Being able to read total supply directly from the contract, rather than through a third-party bridge attestation, is compliance infrastructure, not a technical preference. Wrapped assets introduce counterparty assumptions that regulated institutions cannot easily document in a risk framework.

Keeta layers its own governance controls on top of the settlement layer. Issuers set verification rules, compliance parameters, transfer limits, and other regulatory safeguards at the token level. Tokenized bank deposits move through LayerZero's cross-chain infrastructure, but the institution that issued them retains decision-making authority throughout. That split between settlement infrastructure and issuance control is deliberate. No bank hands over operational authority to a protocol it cannot audit.

Nine Currencies, Four Chains, and a Performance Number That Needs Context

The rollout starts with U.S. dollar-backed tokens. Eight additional currencies follow before the end of July 2026: EUR, JPY, CNY, GBP, CAD, MXN, AED, and HKD. Nine currencies across four blockchains is a serious scope commitment for a first deployment, covering most major global reserve and trade currencies in one announcement.

Keeta ran a public stress test with Google's Spanner engineering team that reached 11.2 million transactions per second on its dedicated blockchain network. That number is legitimately impressive. It is also a controlled lab result, not a live network measurement, and there is a meaningful gap between peak throughput in a benchmarking environment and what happens when regulated institutions start running actual compliance-gated flows through a production payment system with real capital on the line.

Both companies have been quiet on the adoption side. No participating banks have been named. No transaction volume estimates have been shared. That silence is not unusual at this stage of a partnership announcement, but it is the part of the story that deserves the most scrutiny.

The Security Incident That Changed the Default Settings

On April 18, the KelpDAO protocol was exploited for 116,500 rsETH valued at $292 million through a single-verified configuration setup that LayerZero had supported. The company responded by discontinuing support for that configuration type and raising its default security standards across new deployments.

That decision carries direct implications for the Keeta rollout. The KelpDAO breach showed what happens when a cross-chain bridge setup prioritizes simplicity over layered verification. Commercial bank deposits carry a fundamentally different risk profile than DeFi protocol tokens, and a treasury team at a regulated bank has auditors, regulators, and counterparties monitoring every transfer, which means a nine-figure loss in that context would not just be a technical post-mortem item but would invite regulatory intervention and potentially end the careers of whoever approved the configuration.

How Keeta's institutional clients choose to configure the security controls on their tokenized deposits will ultimately determine the real-world security posture of this system. The underlying technology is sound. Whether pressure to onboard quickly leads institutions toward lighter security configurations is the actual open question. That pattern has preceded every major cross-chain incident so far.