LayerZero and Keeta Plan Native Cross-Chain Tokenized Bank Deposits
Key Takeaways
- •LayerZero’s OFT standard will be used to coordinate native cross-chain movement without relying on wrapped versions of the same token.
- •Keeta’s planned stablecoins are backed by commercial bank deposits through Bivo rather than short-term securities portfolios.
- •The initial launch is scheduled for later in July 2026 across Keeta Network, Ethereum, Solana, and Base.
- •The first currency lineup is expected to include USD, EUR, JPY, CNY, GBP, CAD, MXN, AED, and HKD.
- •Users should not assume deposit insurance or guaranteed redemption unless those protections are stated in the issuer’s documents.

LayerZero and Keeta are moving tokenized bank deposits from concept to a scheduled rollout, with plans to make deposit-backed stablecoins natively transferable across multiple blockchains rather than relying on sidecar bridges or wrapped assets.
The initiative will enable tokenized commercial bank deposits to move natively across Keeta Network, Ethereum, Solana, and Base, according to a LayerZero blog post. The planned launch later in July 2026 includes nine fiat currency units: USD, EUR, JPY, CNY, GBP, CAD, MXN, AED, and HKD.
Keeta’s stablecoins are designed to be backed by commercial bank deposits held through Bivo, described by The Block as a U.S.-licensed fintech with access to U.S. payment rails and a partner-bank network. Cross-chain movement will use LayerZero’s Omnichain Fungible Token, or OFT, standard, while issuers retain contract authority as tokens move between chains. LayerZero says its infrastructure supports more than 170 public blockchains.
The model is aimed at payment applications, foreign-exchange desks, on-chain treasurers, and developers that need multi-currency settlement without leaving crypto rails. That places the project in a broader push to connect regulated money movement with programmable blockchain infrastructure, while keeping the underlying backing and redemption mechanics tied to off-chain financial institutions. The main caveat is that legal claims, redemption rights, KYC requirements, and freeze controls depend on the issuer’s documentation. Users should not assume deposit insurance or guaranteed redemption unless the relevant offering documents explicitly provide it.
What tokenized bank deposits are
A tokenized bank deposit is a digital token that represents money held in a bank account. It is not a claim on short-term Treasuries, not a central bank digital currency, and not designed as a speculative asset. In principle, the token’s value mirrors a commercial bank deposit in a specific currency: one token for one unit of fiat.
The legal structure is critical. In some models, the token may be a direct liability of a bank. In others, it may be issued by a nonbank entity that holds deposits at partner banks. Keeta’s announced design is based on deposits held through Bivo’s bank network, with Bivo described as a licensed U.S. fintech platform connected to U.S. payment rails.
As a result, the user is relying on the issuer’s structure, the banking partners, and the contractual terms that govern redemption. The token moves on blockchains, but the underlying value remains off-chain in commercial bank balances.
How LayerZero moves the tokens across chains
Interoperability is the central feature of the rollout. If a euro-denominated deposit token exists on Ethereum but a counterparty needs it on Solana, the token must move cleanly to be useful. Traditional bridges can support this activity, but they often introduce wrapped assets, additional custodial assumptions, and operational complexity.
LayerZero’s OFT standard is designed to coordinate a unified token across supported chains. Under issuer-controlled rules, tokens can be burned on a source chain and minted on a destination chain, keeping supply consistent across networks. The goal is to avoid multiple wrapped versions of the same asset and preserve a single canonical token across chains.
LayerZero says its stack connects more than 170 public chains, giving issuers a broad network for deployment. For Keeta’s rollout, native movement is planned across Keeta Network, Ethereum, Solana, and Base. That set includes EVM liquidity, Solana throughput, and Keeta’s own payments-oriented rail.
Cross-chain messaging still introduces a security layer. Even without wrapped assets, users rely on the messaging protocol’s assumptions and the issuer’s contract permissions. The infrastructure should be treated as production financial plumbing rather than an experimental convenience.
Keeta, Bivo, and the banking layer
Keeta is preparing a family of fiat stablecoins scheduled to go live later in July 2026 across USD, EUR, JPY, CNY, GBP, CAD, MXN, AED, and HKD. The distinguishing feature is not only the multi-currency design, but the stated use of commercial bank deposits instead of securities portfolios.
The reserves are held through Bivo, which is described as a licensed U.S. fintech with domestic payment-rail access and a partner-bank network. That arrangement matters because it may support bank-grade minting and redemption flows, while also giving users a regulatory and operational footprint to review.
Key diligence points include the issuer’s legal entity and the exact liability holder; whether the token represents a direct claim on a bank or on Keeta’s issuing entity; who can redeem; minimum redemption sizes; fees; settlement windows; cut-off times; the bank counterparty list; concentration limits; reserve audit and attestation cadence; and freeze or blacklist policies.
Businesses evaluating the tokens should also request operational documentation, including service-level terms for payment outages, delayed redemptions, failed cross-chain messages, and incident response procedures.
Potential use cases at launch
Multi-currency payroll and vendor payouts
A company could pay a contractor in GBP on Solana while holding USD treasury balances on Base. If the token moves natively across chains, counterparties may avoid receiving wrapped variants they do not support. Foreign exchange remains a separate requirement, but the settlement rail is designed to be consistent.
Global commerce and faster settlement
Marketplaces could settle payouts in local currency on a same-day basis. If AED or MXN tokens can be minted, a business could wire funds once to seed float and then run tracked, programmable payouts on-chain.
DeFi with real-world cash legs
Treasury teams could hold EUR-denominated tokens as liquidity for market-making on Solana while maintaining USD liquidity on Ethereum. If the tokens are fungible across chains under one coordinated supply, rebalancing may not require third-party bridges.
On- and off-ramp operations
Payment companies could connect to Bivo’s rails for deposits and redemptions, then allow users to move between chains inside the same application. Fewer operational steps can reduce support burdens, but bank-linked reserves still bring compliance requirements.
None of these use cases removes KYC or monitoring obligations. Activities involving bank-held reserves should be expected to involve onboarding and compliance controls.
Risks and documents to review
1. Legal and credit exposure
Users need to know who they have a claim against. If deposits are held through partner banks by an issuer, exposure may include both the issuer and the banks. If a partner bank fails, recoveries depend on the legal structure. Deposit insurance should not be assumed to cover token balances.
2. Redemption friction
Some fiat token issuers allow only institutions or approved entities to redeem directly. Retail users may need exchanges or market makers, adding spreads and operational dependence. Eligibility, timing, and fees should be reviewed in the issuer’s documentation.
3. Freeze controls and blacklists
Regulated fiat tokens commonly include freeze rights for compliance purposes. Any trading, treasury, or payment workflow should account for the possibility that an address could be restricted under the issuer’s policies.
4. Cross-chain message risk
OFT can reduce wrapped-asset complexity, but messages still need to be validated. Users moving large balances should understand confirmation processes, outage procedures, and protections against replay or spoofing.
5. Liquidity fragmentation
Launching nine currencies across multiple chains is operationally ambitious. Early order books and automated market maker pools may be thin, and slippage or wider spreads may occur until market makers deploy sufficient liquidity.
6. FX transparency
Holding a CNY or AED token is not the same as holding a CNY or AED bank account. Users should review how currency conversions are priced if they move between currencies within the issuer’s ecosystem.
Deposit tokens, reserve-backed stablecoins, and CBDCs
| Feature | Deposit-backed tokens, Keeta-style | Reserve-backed stablecoins, such as USDC or Tether | CBDCs |
|---|---|---|---|
| Issuer | Nonbank or bank-linked issuer holding deposits at commercial banks | Nonbank issuer holding cash and short-term securities | Central bank |
| Backing assets | Commercial bank deposits | Cash, bank deposits, and short-duration government securities | Central bank liability |
| Legal claim | Against issuer under the terms; not typically deposit-insured | Against issuer under the terms; not deposit-insured | Direct claim on central bank |
| Interoperability | With OFT, native movement across supported chains | Usually single-chain issuance with bridges or wrappers | Varies by jurisdiction and design; often permissioned |
| Who can redeem | Depends on issuer policy; often KYC-approved users or institutions | Varies; many allow institutional redemptions only | Policy-defined access, typically through banks or wallets |
| Key risks | Bank counterparty and issuer credit, freeze controls, cross-chain messaging | Portfolio risk, issuer credit, bank exposure, chain bridges | Privacy, programmability limits, policy changes |
Keeta’s manifesto includes an architecture diagram describing Keeta Network’s multi-rail, multi-currency settlement design and its high-throughput positioning, including an 11M+ TPS claim. The diagram is intended to show how tokenized bank deposits map onto Keeta’s infrastructure.
Practical checklist for users
Before using these tokens, users should request the latest attestation and reserve methodology from the issuer; verify contract addresses on each chain from an official source; confirm custody support across target chains; and test cross-chain transfers with small amounts before scaling.
Organizations should document which employees or systems can initiate mints, burns, and chain transfers, and should use role-based permissions. They should also ask how incidents are handled if a cross-chain message is delayed or a transfer fails.
For non-USD units, users should model spreads and assume early liquidity may be thinner. If only certain entities can redeem directly, organizations may need to arrange market-maker relationships or alternative liquidity channels.
Maintaining small monitoring balances on each chain planned for use can help track operational health without exposing the primary float.
What to watch during the 2026 rollout
Key items to monitor include go-live confirmations for the nine-currency lineup later in July 2026 and the initial chain set of Keeta Network, Ethereum, Solana, and Base. Documentation on redemption eligibility and timelines will be important, particularly for non-U.S. users.
Independent security reviews of the OFT integrations and issuer contracts will also be relevant, along with liquidity deployments on major exchanges and automated market makers. Early spreads and pool depth may indicate how usable each currency is across chains.
Banking disclosures from Bivo and any additional partner banks, including concentration metrics, will be another area to review. Users should also watch how FX between the nine currencies is handled, including whether conversions occur in-app or through market makers. Stablecoin and deposit-token policy guidance may also affect product design.
Frequently asked questions
Are these tokens the same as stablecoins like USDC?
They are similar in that they aim to track fiat currencies 1:1, but the backing differs. Keeta’s announced design uses commercial bank deposits through Bivo’s partner-bank network, rather than a portfolio of cash and short-term securities. Legal terms and redemption rules will depend on the issuer.
Which chains will the first versions support?
The partnership highlights native movement across Keeta Network, Ethereum, Solana, and Base at launch, with LayerZero’s OFT standard coordinating supply across chains.
Are balances covered by deposit insurance?
Deposit insurance should not be assumed. Even if reserves are held as bank deposits, token holders typically have a claim against the issuer rather than direct bank insurance on token balances. The offering documents and legal structure should be checked.
Is KYC required to use or redeem?
KYC should be expected for minting and redeeming. Some issuers may allow broader on-chain holding or transfers while restricting direct redemptions to approved entities. Details should be set out in the issuer’s policies.
How do tokens move across chains without wrapping?
Using OFT, issuer contracts burn tokens on the source chain and mint them on the destination chain under coordinated supply rules, maintaining one canonical token across chains. This reduces wrapped-token complexity but still relies on cross-chain message security.
What currencies are planned first?
The planned initial lineup includes USD, EUR, JPY, CNY, GBP, CAD, MXN, AED, and HKD, with launch slated for later in July 2026.
Who are the intended users?
The design is aimed at builders needing multi-currency settlement, treasurers seeking faster movement between chains, and payment firms connecting on- and off-ramps. Counterparty, legal, liquidity, and cross-chain risks remain material considerations.
Disclaimer: This article is provided for informational purposes only. It is not offered or intended to be used as legal, tax, investment, financial, or other advice.