Cross-Chain Interoperability for Tokenized Assets

Blockchain fragmentation is already costing tokenized real-world asset markets $600M–$1.3B annually — and at projected 2030 market sizes of $16T–$30T, the same friction rate implies $30B–$75B in annua

Introduction

Blockchain fragmentation is already costing tokenized real-world asset markets $600M–$1.3B annually — and at projected 2030 market sizes of $16T–$30T, the same friction rate implies $30B–$75B in annual losses. (RWA.io, CoinTelegraph, Dec 2025) This is the economic case for cross-chain interoperability: not an engineering preference, but a financial imperative. In November 2025, SWIFT enabled its 11,500 member banks to settle tokenized assets directly across blockchains using Chainlink CCIP — transforming multi-chain asset movement from a roadmap item into a live institutional priority. This article explains how cross-chain interoperability works, which protocols are purpose-built for regulated assets, and what the convergence of SWIFT, CCIP, and emerging identity frameworks means for the next decade of tokenized finance.

Why Can't Tokenized Assets Move Freely Between Blockchains Today?

Tokenized assets issued on one blockchain cannot natively interact with liquidity pools, custodians, or compliant trading venues on any other chain. This structural isolation defeats the core promise of programmable finance: that any asset, anywhere, should be accessible to any authorized counterparty in real time. Understanding why this wall exists — and what it costs — is the prerequisite for evaluating every interoperability solution that follows.

What Cross-Chain Interoperability Means for RWA

Cross-chain interoperability is the technical capacity for a tokenized asset issued on one blockchain to be recognized, transferred, and settled on a different blockchain without manual intervention or trust in a centralized intermediary. For real-world assets (RWAs) — tokenized bonds, equities, real estate, and funds — interoperability means a treasury token issued on Ethereum can be used as collateral on an Avalanche-based DeFi protocol, or a tokenized fund share on a private permissioned chain can settle against a stablecoin on a public network. Current blockchain architecture makes this technically non-trivial because each chain maintains its own state machine, consensus rules, and finality guarantees. A token on Ethereum has no native awareness of any state on Polygon, Solana, or a private Hyperledger network. Without an interoperability layer, these chains are functionally separate financial systems that happen to share a common name — blockchain.

The Isolation Problem Defined

Blockchain isolation is an inherent consequence of each network optimizing independently for security and throughput. Every blockchain achieves finality within its own validator set. When an asset is issued on Chain A, its ownership record is maintained exclusively by Chain A's consensus mechanism. Chain B has no mechanism to read or verify that record without external infrastructure. To move value between chains, some party must attest that a state on Chain A is valid and act accordingly on Chain B. When that party is a centralized bridge operator, the security model collapses to a single point of failure. When it is a decentralized messaging protocol, new questions emerge around latency, liveness, and cryptographic proof integrity. Neither model is trivially safe, and for regulated financial assets, neither is trivially compliant.

Why Single-Chain Issuance Fails Institutions

Institutional adoption of tokenized assets has concentrated on individual chains — Ethereum for public DeFi, private permissioned networks for bank-to-bank settlement, Solana for high-throughput applications. Each siloed deployment serves one use case but cannot serve all simultaneously. A bank issuing a tokenized bond on its proprietary chain cannot offer it to DeFi yield protocols without a bridge. A fund manager on Ethereum cannot use those shares as collateral on a JPMorgan Onyx chain. Institutions must either choose one chain and forfeit access to all others, or issue duplicate representations — creating reconciliation overhead, legal ambiguity over canonical ownership, and the fragmentation costs quantified in Section 5. Single-chain issuance is the default for institutions lacking interoperability infrastructure, and it caps the total addressable liquidity for every tokenized asset in existence.

Cross-chain interoperability for tokenized assets moves from the question of what assets to tokenize toward the harder question of how to make those assets universally accessible once tokenized.

How Much Does Cross-Chain Fragmentation Actually Cost Tokenized Markets?

Blockchain fragmentation drains $600M–$1.3B from tokenized RWA markets annually through pricing inefficiencies and capital movement friction — a figure that scales to $30B–$75B per year as the market reaches projected 2030 sizes. (RWA.io, CoinTelegraph, Dec 2025) This is not a theoretical cost. It is measurable in the spread between identical assets on different chains and in the fees extracted by every cross-chain transfer today.

The $1.3B Annual Fragmentation Tax

The $600M–$1.3B annual drag comes from two compounding sources: price divergence between identical assets on non-interoperable chains, and the explicit costs of moving capital between those chains. RWA.io's December 2025 report quantified both effects across the tokenized asset market and concluded that fragmentation is already the single largest source of value leakage in institutional blockchain deployments. (RWA.io, CoinTelegraph, Dec 2025) The lower bound of $600M reflects observable pricing gaps during periods of low cross-chain arbitrage activity. The upper bound of $1.3B accounts for periods when arbitrage is suppressed by high bridge costs or smart contract risk aversion — when the cost of the cross-chain transfer exceeds the spread, the spread simply stays. At the current market size of roughly $24B in tokenized public-chain assets (as of Q1 2026 ), a sustained 2%–5% friction rate on active cross-chain flows generates this range reliably. The implication is that every dollar of interoperability infrastructure investment eliminates a multiple of that amount in annual drag.

Pricing Gaps Across Chains

Economically identical tokenized assets — claims on the same underlying bond, fund, or commodity — routinely trade at spreads of 1%–3% across major networks when interoperability is absent. (RWA.io, 2025) This occurs because cross-chain arbitrage, the mechanism that normally closes price gaps, requires paying bridge fees, absorbing slippage, and accepting the smart contract risk of the bridge itself. When those costs exceed the spread, arbitrageurs stand aside and the divergence persists. For a tokenized treasury with a 4% annual yield, a sustained 2% pricing gap represents half the annual return — a structurally unacceptable discount for institutional investors who track performance against benchmark. Price fragmentation also undermines price discovery. If the same asset trades at different prices on five chains simultaneously, there is no authoritative market price. Index providers, fund administrators, and risk systems cannot mark positions accurately, which creates cascading reporting and risk management failures downstream.

Capital Movement Friction Costs

Moving capital between non-interoperable chains costs 2%–5% per transaction in fees, slippage, transfer overhead, gas costs, and timing risk. (RWA.io, 2025) For institutional flows in the tens or hundreds of millions of dollars, this friction is prohibitive. A $100M reallocation from an Ethereum-based tokenized fund into a Solana-based yield protocol would consume $2M–$5M in transfer costs under current conditions. No treasury manager would accept those economics when a wire transfer to a traditional venue costs basis points. The friction also creates asymmetric liquidity: chains with more issuance attract more liquidity, which attracts more issuance, while chains with less activity become progressively less viable. Cross-chain fragmentation is therefore a self-reinforcing dynamic that concentrates tokenized assets on one or two dominant chains. The resilience and choice that multi-chain architecture was intended to provide disappear with it.

Data current as of May 2026.

RWA.io projects that applying today's 2%–5% friction rate to a $16T–$30T tokenized market by 2030 implies annual losses of $30B–$75B — making interoperability the most economically urgent infrastructure problem in institutional DeFi. (RWA.io, 2025)

What Technical Mechanisms Enable Tokenized Assets to Cross Blockchains?

Three distinct mechanisms move tokenized assets between blockchains: messaging protocols, custodial bridges, and atomic swaps. Each carries different trust assumptions, latency profiles, and failure modes. Choosing the wrong mechanism for a regulated RWA is not a performance decision — it is a legal and security decision, because each model assigns custody, counterparty risk, and finality differently.

Messaging Protocols vs Bridge Architectures

Messaging protocols do not move tokens directly; they transmit verified state information between chains so smart contracts on the destination chain can act on instructions from the source chain. Chainlink CCIP and LayerZero operate in this category. The source chain emits a message — "wallet X on Chain A has burned N tokens" — and the messaging layer delivers a cryptographically verified version of that message to Chain B, which then mints an equivalent representation. No custodian holds the underlying asset. Bridge architectures, by contrast, hold assets in a smart contract vault on the source chain while issuing representations on the destination chain. This custodial model concentrates risk: the vault becomes a high-value target, and several major exploits — including the $620M Ronin Bridge hack in 2022 — stemmed from compromised validator sets controlling those vaults. For regulated RWA, the custodial model also creates legal title ambiguity that messaging protocols sidestep by never taking custody.

Lock-and-Mint vs Burn-and-Mint Transfer Models

Lock-and-mint is the dominant bridge model: tokens are locked in a contract on Chain A, and wrapped representations are minted on Chain B. This preserves the original supply but creates wrapped derivatives — WBTC, cbBTC, bridged USDC — each trading as a distinct asset with distinct liquidity. For RWA, wrapped representations create regulatory complexity: if a tokenized bond is locked on Ethereum and wrapped representations circulate on Avalanche, which jurisdiction governs the wrapped version and who is the legal issuer? Burn-and-mint eliminates this problem by destroying tokens on the source chain and minting native tokens on the destination chain. Supply is conserved without derivative representations. Chainlink's Cross-Chain Token (CCT) standard implements burn-and-mint with permissioned transfer rules — allowing institutional issuers to maintain supply control and compliance enforcement across every chain simultaneously.

Atomic Swaps and Hash Time-Locked Contracts

Atomic swaps execute a trustless exchange between assets on two different chains using hash time-locked contracts (HTLCs). Both parties lock assets with a cryptographic hash; the swap completes when both reveal the preimage before the time lock expires. If either party fails to act, both locks expire and assets return. Atomic swaps require no intermediary and no bridge vault — the most trust-minimized cross-chain mechanism available. The practical limitation is counterparty discovery: swaps require a willing counterparty holding the exact asset on the exact destination chain. For liquid pairs — BTC/ETH swaps were the original use case — liquidity aggregators can match counterparties efficiently. For long-tail RWA, finding a counterparty willing to exchange a tokenized municipal bond for a tokenized corporate loan on a different chain is far harder. Atomic swaps are therefore viable for large liquid asset classes and less viable for specialized RWA instruments.

How Are Chainlink CCIP and SWIFT Connecting Banks to Every Blockchain?

In November 2025, SWIFT enabled its 11,500 member banks across 200+ countries to attach blockchain wallet addresses to payment messages and settle tokenized assets directly across chains — using Chainlink CCIP as the underlying protocol connecting 60+ public and private blockchains. (SWIFT.com, 2025; Chainlink Blog, 2025) This is the single largest expansion of cross-chain tokenization infrastructure in history. Banks connect to the on-chain asset ecosystem without rebuilding their technology stacks — SWIFT handles the messaging, CCIP handles execution.

Chainlink CCIP Architecture and 60-Chain Reach

CCIP is a messaging and token transfer protocol built on Chainlink's decentralized oracle network. It operates through three components: a risk management network that independently monitors cross-chain transactions for anomalies, a primary oracle network that validates cross-chain messages, and smart contract routers on each supported chain that execute instructions upon verified delivery. Cross-chain transfer volume via CCIP surged 1,972% to $7.77B in 2025, and the protocol now secures $33.6B in cross-chain tokens across 60+ blockchains. (Chainlink Blog, 2025) The CCT standard allows token issuers to define permissioned transfer rules — who can hold, transfer, and redeem tokens on each chain — while CCIP enforces those rules at the protocol level. An issuer can specify that their tokenized bond transfers only to KYC-verified wallets on destination chains, and CCIP enforces that constraint without requiring the issuer to operate chain-specific smart contracts on every network.

The SWIFT-Chainlink Integration for 11,500 Banks

SWIFT's November 2025 rollout connected its ISO 20022 payment messaging standard directly to blockchain settlement. Any SWIFT member institution can now embed blockchain wallet addresses in standard SWIFT messages and trigger on-chain settlement events — including tokenized asset redemptions and cross-chain transfers — without replacing existing infrastructure. (SWIFT.com, 2025) A SWIFT message specifying a tokenized bond redemption from an Ethereum-based issuer into a Polygon-based cash account routes through CCIP, which validates and executes the cross-chain instructions. SWIFT provides the messaging standard and 11,500 institutional counterparties; Chainlink provides the execution layer. In December 2025, SWIFT completed a proof of concept with HSBC and Ant International for cross-border tokenized deposit transfers using ISO 20022 standards — demonstrating the architecture works for bank-to-bank settlement across jurisdictions. (SWIFT.com, 2025)

Coinbase and Ondo: Institutional CCIP Adoption

Two institutional adoptions in late 2025 validated CCIP as the default cross-chain standard for regulated asset issuers. Coinbase selected CCIP as the exclusive bridge infrastructure for all Coinbase Wrapped Assets — cbBTC, cbETH, cbDOGE, cbLTC, cbADA, and cbXRP — with an aggregate market cap of approximately $7B as of December 2025. (CoinDesk, Dec 2025) Ondo Finance, the largest institutional tokenized treasury issuer, selected Chainlink as its official oracle infrastructure and CCIP as its preferred interoperability solution for its regulated tokenized stocks platform. (Chainlink Blog, 2025) Ondo's choice matters because tokenized treasuries are regulated securities — by selecting CCIP with its permissioned CCT standard, Ondo can enforce KYC and transfer restrictions across every chain where its tokens circulate. These adoptions create a network effect: as more regulated asset issuers standardize on CCIP, the protocol becomes the de facto interoperability layer for institutional cross-chain tokenization. Each new issuer that joins reduces integration costs for all subsequent ones.

Data current as of May 2026.

Which Interoperability Protocols Are Purpose-Built for Multi-Chain RWA?

Cosmos IBC, Polkadot XCMP, and Polygon AggLayer each take a distinct architectural approach to native cross-chain token transfers. Unlike bridge-based solutions that create wrapped derivatives, these protocols move native tokens directly between connected chains — eliminating the wrapped-token fragmentation problem at the cost of tighter ecosystem coupling.

Cosmos IBC and Zone-Based RWA Transfers

The Inter-Blockchain Communication protocol (IBC) is the native interoperability standard for the Cosmos ecosystem. It moves tokens directly between any two IBC-enabled blockchains — called zones — without wrapping or custodial intermediaries. IBC uses light client proofs: each chain maintains a minimal verifier for its counterparty chains, validating cross-chain transaction finality independently. For RWA, IBC's strength is its permissioned zone model. An issuer deploys a compliance zone — a sovereign blockchain with KYC/AML rules baked into consensus — and connects it via IBC to liquidity zones where secondary trading occurs. Compliance rules follow the token via IBC's packet metadata. Noble functions as a cross-chain stablecoin issuance zone with architecture directly applicable to regulated RWA. The key limitation is that IBC requires both chains to run compatible light clients — workable within Cosmos but not natively extendable to Ethereum, Solana, or EVM chains without additional bridging layers.

Polkadot XCMP and Native Cross-Parachain Tokens

Polkadot's Cross-Consensus Messaging (XCM) and XCMP enable native asset transfers between parachains — specialized blockchains sharing Polkadot's relay chain security. Unlike IBC, parachains do not maintain individual light clients for each counterparty; security is inherited from the relay chain's unified validator set. A tokenized bond issued on one parachain transfers to a DeFi protocol on another with relay-chain-level security — no wrapped token, no bridge validator set to compromise. A regulated issuer parachain can enforce compliance rules at the consensus level, and assets crossing to adjacent parachains carry those rules under the same validator set. The constraint is that XCMP's guarantee only applies within Polkadot. Assets moving to Ethereum require a bridge — Snowbridge or Hyperbridge — which reintroduces the external trust assumptions that parachain-native transfers avoid.

AggLayer and Polygon CDK for Institutional Chains

Polygon's AggLayer is a unified cross-chain aggregation protocol designed for chains built with the Polygon CDK (Chain Development Kit). It enables cross-chain asset transfers and liquidity sharing between CDK chains through a single aggregated proof system — a ZK-proof that validates the state of all connected chains simultaneously. For institutional issuers, CDK enables the deployment of purpose-built compliance chains — a bank can operate its own Polygon CDK chain with permissioned validators, KYC-gated accounts, and custom compliance logic — while AggLayer provides native interoperability with every other CDK chain and, through bridging, with Ethereum mainnet. The ZK-proof architecture means cross-chain transfers are cryptographically verified rather than relying on a validator set's honesty. This reduces the trust surface substantially for multi-chain tokenized assets. Plume Network, a dedicated RWA chain built on CDK, uses AggLayer's SkyLink component to enable tokenized assets to interact across Ethereum, Solana, and Polygon simultaneously. Cross-chain RWA deployments on Plume account for over 15% of the $24B tokenized asset market as of Q1 2026. (RWA.io, 2026 )

What Is the xRWA Framework and How Does It Solve Identity Across Chains?

The xRWA framework, published in September 2025 by academic researchers, addresses the identity and authentication gap that all interoperability protocols leave unsolved: how does a tokenized asset prove its compliance credentials on Chain B when those credentials were established on Chain A? (arxiv.org/abs/2509.12957, Sep 2025) Using decentralized identifiers (DIDs) and verifiable credentials (VCs) anchored to SPV proofs, xRWA enables a tokenized asset to authenticate once and reuse that credential across any connected chain — eliminating the re-registration and repeat KYC processes that currently block institutional cross-chain deployment.

DID and Verifiable Credentials for Cross-Chain Asset Identity

A decentralized identifier (DID) is a cryptographically controlled identifier that resolves to a DID document containing public keys, authentication methods, and service endpoints — without relying on any centralized registry. A verifiable credential (VC) is a tamper-proof attestation issued by a trusted party and cryptographically bound to a DID. In xRWA, every tokenized asset receives a DID at issuance. The issuer attaches VCs covering KYC approval for authorized holders, compliance attestations, and transfer restriction rules. This DID-VC bundle travels with the asset across chains. When the asset arrives on Chain B, a smart contract resolver verifies the VC signatures against the issuer's public key — without re-running KYC and without requiring Chain B to have any prior relationship with Chain A's compliance infrastructure. The model is analogous to a passport: issued by one authority, verified by any border control that recognizes the issuing authority's cryptographic signature.

SPV Proof Authentication Without Re-Registration

Simplified Payment Verification (SPV) proofs allow a lightweight client to verify that a transaction was included in a block without downloading the full chain history. xRWA applies this to cross-chain authentication: when an asset is KYC-verified on Chain A, a compact SPV proof is generated and attached to the asset's DID. Any chain that can verify SPV proofs — requiring only Chain A's block headers, not its full state — can confirm the authentication is final without a trusted relayer attesting to compliance status. The proof is self-verifying: Chain B validates independently, with the same security guarantee Chain A's own nodes have. Once a holder's KYC credential is established on Chain A and encoded in an SPV-backed VC, that credential is valid on every chain supporting xRWA verification contracts — a single KYC check satisfying compliance requirements across the entire multi-chain deployment.

Cross-Chain Channel Settlement for Frequent RWA Transactions

For high-frequency cross-chain RWA interactions — collateral movements, yield distributions, automated rebalancing — xRWA proposes a channel-based settlement model. Two parties open a channel by locking a small deposit on both chains. All subsequent interactions occur off-chain, with only cryptographic state commitments exchanged; the final state is submitted on-chain when the channel closes. This reduces per-transaction cost from a full on-chain transaction to a cryptographic signature exchange — orders of magnitude cheaper for daily collateral rebalancing or automated yield distributions across custodians on different chains. Off-chain state updates are near-instant; on-chain finality is deferred to the settlement event. For use cases where settlement frequency is high but finality can be batched — dividend payments, margin calls — xRWA channels provide institutional-scale throughput without congesting base-layer chains.

How Does Cross-Chain Tokenization Handle KYC, AML, and Regulatory Compliance?

Cross-chain RWA compliance requires portable identity credentials that satisfy KYC and AML rules in every destination jurisdiction simultaneously. Current bridge architectures do not natively support this: a token can cross a bridge, but its compliance metadata does not cross with it. Without identity portability, every cross-chain transfer of a regulated asset creates a compliance gap — the receiving chain has no verified record of who holds the asset or whether that holder is authorized.

KYC-AML Identity Portability Across Jurisdictions

The compliance challenge for cross-chain RWA is jurisdictional rather than technical. KYC and AML rules differ across the US, EU, UK, and Singapore. A KYC check under FinCEN rules may not satisfy EU AMLD6 requirements or MAS guidelines. When a tokenized asset crosses from a US-compliant chain to an EU-regulated venue, the receiving venue must verify the holder's identity under its own rules — or rely on a mutual recognition framework that does not yet broadly exist. The xRWA DID-VC model addresses this by encoding jurisdiction-specific compliance attestations as separate VCs on the same DID. A holder's DID can carry a US FinCEN VC, an EU AMLD6 VC, and an MAS VC simultaneously — each issued by a KYC provider in the relevant jurisdiction and cryptographically bound to the same identity. Cross-chain smart contracts resolve which VC applies based on the destination chain's jurisdiction settings. Compliance travels with the asset without requiring a single global KYC standard.

Regulatory Jurisdiction Conflicts in Multi-Chain Issuance

Multi-chain issuance creates legal questions no interoperability protocol can fully resolve. If a tokenized bond is issued on a Cayman-domiciled permissioned chain and representations circulate on US Ethereum, which securities law governs secondary trading? The SEC's January 2026 joint staff statement confirmed that tokenizing a security does not change its legal status — a bond remains a bond, subject to registration and disclosure requirements regardless of chain. (SEC.gov, Jan 2026) Issuers cannot reduce regulatory obligations by moving tokens cross-chain. The underlying instrument and the parties to the transaction determine obligations, not the chain. Every chain on which the asset trades must enforce the full requirements of the most restrictive applicable jurisdiction — meaning permissioned transfer rules, enforced via CCIP's CCT standard or IBC's compliance zones, must apply regardless of where trading activity occurs.

MiCA and Cross-Border Compliance Standards

The EU's Markets in Crypto-Assets (MiCA) regulation, which entered full effect in December 2024, establishes the most comprehensive cross-border framework for tokenized asset issuance and trading in any major jurisdiction. MiCA requires crypto-asset service providers in the EU to maintain AML compliance, investor disclosure, and operational resilience standards regardless of which chain the underlying token trades on. For cross-chain RWA, MiCA creates a de facto global floor: any asset trading on EU-regulated venues must comply, meaning the entire multi-chain deployment must support identity verification, transaction monitoring, and reporting capabilities. Issuers designing multi-chain RWA for institutional distribution tend to build to MiCA standards globally — EU market access is commercially essential, and MiCA compliance approximates the requirements of most other major jurisdictions. ISDA's digital asset definitions and DTCC's tokenization initiatives, covered in Section 13, complement MiCA's requirements at the contractual and infrastructure level.

Data current as of May 2026.

Which Institutions Are Already Running Live Cross-Chain Tokenized Asset Products?

Ondo Finance, BlackRock BUIDL, and Franklin Templeton are operating live tokenized treasuries and fund shares across multiple chains as of Q1 2026 — demonstrating that cross-chain RWA is operational infrastructure, not a roadmap item. Each institutional deployment reveals a different architectural model for managing multi-chain issuance at regulated scale.

Ondo Finance and Multi-Chain Tokenized Treasuries

Ondo Finance operates OUSG (Ondo Short-Term US Government Bond Fund) and USDY (Ondo US Dollar Yield) across Ethereum, Solana, Polygon, Arbitrum, Aptos, Sui, and Mantle — seven chains as of Q1 2026. Each deployment uses Chainlink CCIP and the CCT standard to enforce KYC-gated transfer restrictions across all chains simultaneously. An investor who passes Ondo's KYC process on any one chain receives a credential that authorizes transfers on all supported chains — the portability model described in the xRWA framework applied at production scale. Ondo's multi-chain deployment grew rapidly in 2025 as institutional demand for on-chain US Treasury exposure expanded beyond Ethereum's DeFi ecosystem into newer, higher-throughput chains. Solana's addition to CCIP in late 2025 unlocked $19B+ of assets for cross-chain deployment, and Ondo was among the first issuers to use the new Solana CCIP integration for treasury token flows. (Chainlink Blog, 2025) Ondo's total value locked across chains exceeded $1B in 2025, establishing it as the benchmark deployment for compliant multi-chain RWA at institutional scale.

BlackRock BUIDL Expansion Across Chains

BlackRock's USD Institutional Digital Liquidity Fund (BUIDL), launched on Ethereum in March 2024, expanded to Aptos, Arbitrum, Avalanche, Optimism, and Polygon in 2025 — the first registered fund token deployed across six chains simultaneously by an institutional asset manager. BUIDL uses Securitize as its transfer agent and token administrator, with Securitize's compliance infrastructure enforcing KYC and transfer restrictions across each chain deployment. The multi-chain expansion reflects institutional investor demand: different DeFi protocols and institutional venues operate on different chains, and BUIDL's value as a yield-bearing collateral asset depends on its accessibility wherever collateral is needed. BUIDL crossed $1B in assets under management in 2024, making it the first tokenized fund to reach that threshold, and continued growing through its multi-chain expansion. The BUIDL deployment demonstrates that a registered fund — subject to the Investment Company Act, SEC reporting requirements, and full AML/KYC compliance — can operate natively across multiple chains without any relaxation of its regulatory obligations.

Franklin Templeton and Cross-Chain Fund Shares

Franklin Templeton's OnChain US Government Money Fund (FOBXX) was the first US-registered fund to use a public blockchain for transaction processing, originally deployed on Stellar. It subsequently expanded to Polygon and, in 2025, to Arbitrum and Base — multi-chain issuance of a registered mutual fund across both purpose-built financial chains and general-purpose EVM networks. FOBXX crossed $500M in assets under management in 2025, becoming the first institutional fund available as collateral across multiple EVM-compatible DeFi protocols. Its deployment on Base — Coinbase's L2 — connects FOBXX to Coinbase's 110M+ verified users directly. Each new chain required Franklin Templeton to extend transfer agent infrastructure independently, underscoring the compliance overhead that CCT or xRWA-style unified identity layers are designed to eliminate.

What Does Cross-Chain Interoperability Mean for Collateral and Settlement by 2030?

Applying today's 2%–5% cross-chain friction rate to the projected $16T–$30T tokenized asset market by 2030 implies annual fragmentation losses of $30B–$75B — making cross-chain interoperability infrastructure the largest single lever for value preservation in institutional DeFi. (RWA.io, 2025) The more consequential transformation, however, is not loss prevention but capability creation: unified cross-chain collateral mobility enables real-time margin calls, automated rebalancing, and 24/7 settlement across asset classes that currently operate on incompatible infrastructure and settlement cycles.

Cross-Chain Collateral Mobility and Margin Unification

Collateral mobility — the ability to move assets between venues in real time to meet margin requirements — is constrained by chain boundaries. A bank holding tokenized Treasuries on Ethereum cannot post them as margin for a derivatives position on a Hyperledger-based clearing house without a cross-chain transfer costing both time and basis points. Cross-chain interoperability enables atomic cross-chain collateral substitution: the asset unlocks on Chain A and locks as margin on Chain B in a single atomic transaction, with no window of uncollateralized exposure. Chainlink's cross-chain capital markets research identifies this as the primary institutional use case driving CCIP's 2025–2026 adoption roadmap. Real-time cross-chain collateral management reduces total collateral required system-wide — assets deploy precisely where needed rather than being pre-positioned on every chain that might require margin.

Real-Time Settlement Unification

Today's multi-chain tokenized asset ecosystem settles on incompatible cycles: Ethereum settles in ~12 seconds, Solana in ~400ms, private chains on T+0 to T+2 schedules defined by their operators. Cross-chain settlement — where payment on Chain A must coordinate with asset delivery on Chain B — requires the slower chain to define the settlement window, which in mixed public-private deployments means the private chain's T+1 or T+2 cycle governs the entire transaction. Interoperability protocols that support atomic cross-chain delivery-versus-payment (DvP) eliminate this asymmetry: both legs of the trade lock simultaneously, and settlement finalizes only when both locks confirm. SWIFT's ISO 20022 + CCIP architecture, described in Section 7, targets atomic DvP for bank-to-bank tokenized asset settlement as its primary production use case by 2026. The OECD's January 2025 report on tokenization in financial markets identified T+0 cross-chain DvP as the settlement standard that would unlock the full efficiency benefits of tokenization — currently unrealized because fragmented chain infrastructure prevents the atomic coordination that T+0 requires. (OECD, Jan 2025)

2030 Fragmentation Cost Projections

RWA.io's fragmentation model projects that at a $16T tokenized market — the conservative BCG/ADDX estimate for 2030 — today's 2%–5% friction rate implies $30B–$75B in annual losses from pricing gaps and transfer costs alone. (RWA.io, 2025) At the aggressive $30T projection, the implied loss range reaches $60B–$150B annually. These figures assume no improvement in interoperability infrastructure — a baseline that grows less plausible as CCIP adoption, AggLayer deployments, and xRWA standards advance. The more realistic scenario has interoperability investment cutting effective friction toward 0.1%–0.5% for standardized assets on well-connected chains, reducing annual fragmentation losses by 80%–95% even as the market grows. The interoperability market itself is projected to reach $1,832.3M by 2035 from $332.8M in 2025, a CAGR of 18.6% driven by the economic incentive to capture this fragmentation drag. (Future Market Insights, 2025)

Data current as of May 2026.

What Standards and Governance Frameworks Will Govern Cross-Chain RWA Markets?

ISDA's digital asset derivatives definitions, DTCC's tokenization interoperability initiatives, and ISO 20022 adoption by SWIFT form the governance and legal layer that transforms cross-chain technical capability into legally enforceable financial contracts. Without this standards layer, cross-chain RWA transfers create assets that can move but cannot be enforced — legally ambiguous instruments that no institutional counterparty can accept as collateral or settlement.

ISDA Digital Asset Derivatives Definitions

ISDA published its Digital Asset Derivatives Definitions in 2024, establishing standardized contractual terms for derivatives referencing tokenized securities. These definitions specify how settlement, valuation, disruption events, and fallback provisions apply when the underlying asset is a token on a blockchain. For cross-chain RWA, they create the legal infrastructure for multi-chain derivative contracts: a credit default swap referencing a tokenized bond trading on three chains requires a contractual definition of which chain's price governs settlement, what constitutes a disruption event if one chain becomes unavailable, and how fallback valuation applies when cross-chain price divergence exceeds defined thresholds. ISDA's Master Agreement guidance also confirms that on-chain derivatives execution is governed by ISDA documentation — the netting and close-out mechanics apply whether settlement occurs on-chain or off-chain.

DTCC Tokenization Interoperability Initiative

The Depository Trust & Clearing Corporation (DTCC) received a no-action letter from the SEC in December 2025, authorizing its plan to tokenize DTC-custodied assets — equities, fixed-income products, and government debt — with a production rollout targeted for 2026. (SEC.gov, Dec 2025) DTCC is the central securities depository for US markets, holding custody of virtually all US equities and bonds. Tokenized DTCC-custodied assets would make the entire US capital markets infrastructure accessible to cross-chain settlement. DTCC's Project Ion initiative tested blockchain-based equity settlement across multiple distributed ledger platforms and identified cross-chain atomic DvP as the prerequisite for replacing T+2 settlement with T+0 on-chain settlement. DTCC settles over $2.15 quadrillion in securities annually — its interoperability standards will become the de facto baseline for cross-chain RWA in US markets.

ISO 20022 as the Cross-Chain Messaging Standard

ISO 20022 is the global financial messaging standard used by SWIFT, TARGET2, and over 70 central banks worldwide. Its adoption as the cross-chain messaging layer — through SWIFT's blockchain integration and DTCC's tokenization architecture — means cross-chain RWA transactions can be described, routed, and settled using the same data structures that govern $5T+ in daily global payment flows. ISO 20022's rich data fields accommodate asset identifiers, compliance metadata, jurisdictional markers, and settlement instructions in a single structured message — the natural carrier for the cross-chain identity and compliance data that xRWA's DID-VC model generates. As ISO 20022 migration completes by 2026 across major payment systems, every cross-chain RWA transaction becomes expressible in a format that every bank, custodian, and clearing house in the world can parse and act on. The convergence of ISO 20022, CCIP, and DID-VC represents the emerging architecture for a unified global tokenized asset market.

The path to a unified liquidity layer for tokenized assets is not a single protocol or a single regulation. It is the convergence of messaging standards, execution protocols, identity frameworks, and legal definitions — each being built in parallel and beginning to connect in 2025–2026 in ways that were purely theoretical three years ago.

FAQ

References / Sources