Blockchain Interoperability: A Technical Guide for Engineers

Last Updated: November 3, 2026

The top bridging solutions for blockchain interoperability layers in November 2026 are Circle’s CCTP for native USDC, LayerZero, Across, Relay, Chainlink CCIP and Wormhole, while IBC, Hyperlane, Axelar and deBridge serve more specialized roles. By Blockchainreporter’s calculation from DefiLlama data, CCTP and LayerZero alone carried about 62% of the $48.8 billion in bridge volume that DefiLlama tracked in the 30 days to November 3, 2026.

Blockchain interoperability lets independent distributed ledgers transfer assets, relay messages, and verify state across network boundaries without requiring either chain to trust the other’s internal consensus. This guide covers the main interoperability mechanisms, including atomic swaps, relays, notary schemes, cross-chain messaging, intent-based bridges, and multi-chain frameworks such as IBC. It also examines their trust models and security trade-offs, including the interoperability trilemma; production deployments from Cosmos to Polkadot to Chainlink CCIP; the bridge exploits of 2026; and a step-by-step implementer checklist. Named standards such as ERC-7786 and ERC-7683 appear alongside the security incidents that shaped current best practices.

What you will learn:

• The seven major interoperability mechanism types and how their trust assumptions differ
• How the top bridging solutions compare on verification model, chain coverage, volume, and notable users
• How the interoperability trilemma forces design trade-offs between trustlessness, extensibility, and generalizability
• Where bridge exploits have concentrated, including the April 2026 Kelp DAO incident, and why verifier diversity changes the risk profile
• How to secure bridging across permissioned and institutional chains
• Production deployments across DeFi, real-world assets, NFTs, gaming, and enterprise supply chains
• A numbered checklist for teams designing or auditing cross-chain systems
• Current standards (IBC v2, ERC-7786, ERC-7683, wallet standards), what changed since 2025, and what an open, interoperable digital currency requires

Key Takeaways

Blockchain interoperability’s security and scalability depend on choosing the right trust model at the protocol layer, rather than patching it at the application layer.

Table of Contents

• Why blockchain interoperability matters for real applications
• Taxonomy of interoperability approaches and how each mechanism works
• How the interoperability stack breaks down by layer
• What are the top bridging solutions for interoperability layers?
• Major security risks, the interoperability trilemma, and practical mitigations
• Representative projects and concrete cross-chain use cases
• A practical checklist for teams building cross-chain systems
• Standards, emerging proposals, and the future of blockchain interoperability
• Which standards make digital wallets interoperable?
• What are the characteristics of an open, interoperable digital currency?
• Frequently Asked Questions
• What engineers and decision-makers should prioritize now
• Sources

Why blockchain interoperability matters for real applications

Without cross-chain communication, every blockchain is an island. Liquidity fragments across dozens of networks, users pay redundant fees to move assets manually, and developers rebuild the same logic on every chain they target. Interoperability is the prerequisite for a multi-chain ecosystem to work as one system rather than a collection of silos.

What does cross-chain interoperability mean?

Cross-chain interoperability is the ability of two separate blockchains to exchange value or instructions and to verify that what one chain reports actually happened. An interoperable blockchain can prove its state to another chain, or accept proofs from it, so an asset or message can move without a trusted middleman holding the funds. Every design answers one question differently: who or what verifies the message between chains?

Two terms are often mixed up. Interoperable blockchains, such as Cosmos chains running IBC or Polkadot parachains exchanging XCM messages, build communication into the protocol itself. Cross-chain bridges and messaging networks, such as LayerZero, Chainlink CCIP, Wormhole, and Axelar, connect chains that were not designed to talk to each other, which adds an external trust layer that must be secured on its own.

What interoperability delivers in practice

The practical benefits fall into four categories:

• Liquidity aggregation: A DeFi protocol that can draw from liquidity pools on Ethereum, Solana, and Avalanche simultaneously offers tighter spreads and deeper order books than one locked to a single chain. Cross-chain DEX aggregators and cross-chain yield strategies depend entirely on this.
• Composability: Smart contracts on one chain can call logic on another. This enables yield strategies, cross-chain governance votes, and multi-step financial products that span networks.
• Workflow acceleration: In enterprise deployments, interoperability removes manual reconciliation between counterparties running different ledgers, which is where much of the business value sits.
• New cross-domain use cases: Supply-chain data sharing between a permissioned enterprise ledger and a public settlement layer, cross-border payments with tokenized deposits, tokenized funds issued on several chains, and interoperable NFT provenance records all require chains to exchange verifiable state.

The governance parallel matters too. Technical standards alone rarely deliver lasting interoperability; stakeholder engagement, data-quality programs, and governance frameworks determine whether it scales.

Blockchain is no different. Teams that treat interoperability as only an engineering problem and skip governance design tend to find their cross-chain systems fragile under real operating conditions.

Taxonomy of interoperability approaches and how each mechanism works

Interoperability solutions fall into seven broad models: atomic swaps, lock-and-mint bridges, chain relays with light clients, notary schemes, cross-chain messaging protocols, intent-based bridges, and native multi-chain frameworks. Each has a distinct trust model and cost profile.

Atomic swaps

Two parties lock assets in hash time-locked contracts (HTLCs) on their respective chains. The same cryptographic secret unlocks both legs, so neither party can claim the counterparty’s asset without releasing their own.

No custodian is involved. The limitation is that both chains must support compatible hash functions and time-lock semantics, which rules out many heterogeneous pairings.

Cross-chain bridges (lock-and-mint / burn-and-release)

A user locks a native asset on the source chain, and a bridge contract mints a wrapped representation on the destination chain. Security depends entirely on who controls the minting key.

Federated bridges use a multisig committee. Optimistic bridges add a fraud-proof window, while ZK bridges use cryptographic validity proofs. The custody model is the single biggest variable in bridge risk.

Issuer-run burn-and-mint is a special case. Circle’s Cross-Chain Transfer Protocol (CCTP) burns USDC on the source chain and mints native USDC on the destination after Circle attests to the burn, so no wrapped copy or locked pool exists. The trust anchor is Circle itself, which makes CCTP a USDC-specific route rather than a general messaging layer.

Chain relays and light-client verification

A relay submits block headers from chain A to a smart contract on chain B. That contract runs a light-client verification routine and checks proof-of-work or proof-of-stake finality proofs against the submitted headers.

No trusted third party is needed; the cryptographic proof is the trust anchor. This is the model IBC uses and is generally considered the most trustless approach available today.

Notary schemes

A set of designated validators, or notaries, observes events on one chain and attests to them on another. Security depends on the assumption that the notary set is honest.

Fully centralized notaries introduce a single point of failure. Threshold signature schemes (TSS) with large, diverse validator sets reduce but do not eliminate that risk.

Cross-chain messaging protocols

Rather than moving assets directly, these protocols relay arbitrary message payloads between smart contracts. The receiving contract interprets the message and acts on it locally.

Chainlink’s CCIP, LayerZero, Axelar, Wormhole, and Hyperlane all operate in this space, with different relay and verification architectures. Most also offer token standards built on their messaging, such as LayerZero’s Omnichain Fungible Token (OFT), Wormhole’s Native Token Transfers (NTT), and Axelar’s Interchain Token Service (ITS), which let an issuer keep one supply across many chains instead of creating wrapped copies.

Data layers are another piece of cross-chain design. In July 2024, Synternet integrated with the Interchain ecosystem to improve real-time data sharing across blockchains.

Intent-based bridges and solver networks

In an intent-based bridge, the user signs an order describing the outcome they want, for example receiving USDC on Base in exchange for USDC on Arbitrum. Independent relayers or solvers compete to fill the order from their own inventory, then get repaid on the source chain once the fill is verified.

The user does not wait for a slow cross-chain message, and less liquidity sits idle in a pool that attackers can target. The trust question shifts from who guards the pool to how solver repayments are verified, so intent systems still need an oracle or messaging layer underneath. ERC-7683 is the draft Ethereum standard for describing these cross-chain orders.

Multi-chain frameworks (IBC / Polkadot XCMP)

These are protocol-level standards built into the chain’s consensus layer. IBC defines a transport, authentication, and ordering layer that any IBC-compatible chain can use natively. IBC v2, announced for an end-of-March 2025 launch, slimmed the protocol so chains outside Cosmos can implement it, and the IBC protocol site now lists Ethereum among IBC-connected ledgers.

Polkadot’s cross-chain message passing design carries XCM messages between parachains under the relay chain’s shared security. In current deployments those messages travel over HRMP channels routed through the relay chain, which Polkadot’s developer documentation tells teams to open between parachains. Both IBC and Polkadot eliminate the need for external bridge infrastructure between participating chains.

Trust-model primitives to look for when evaluating any solution:

• Light-client proofs or finality proofs (cryptographic, no trusted party)
• Fraud proofs with on-chain dispute windows (optimistic security)
• Multiple independent verifiers, never a single verifier on a production route
• Formal verification of bridge and messaging contracts
• Decentralized relayer sets with economic slashing

How the interoperability stack breaks down by layer

Interoperability is not a single protocol. It is a stack of responsibilities. Conflating those responsibilities causes many design mistakes.

• Transport / message-delivery layer: This layer gets a packet from chain A to chain B reliably. IBC’s transport layer handles packet ordering, acknowledgment, and timeout. The question at this layer is liveness: will the message arrive, and when?
• Protocol and verification layer: This layer proves that the message is authentic and that the source chain’s state contains what the message claims. Light-client proofs, finality proofs, and verifier networks belong here. Security is either enforced here or delegated to a trusted party.
• Semantic / data-schema layer: This layer ensures that what chain A calls a “transfer of 10 units of asset X” means the same thing to chain B’s contracts. Without schema mapping and shared ontologies, two chains can exchange valid packets that each interprets differently. This layer is frequently underbuilt.
• Application orchestration layer: This layer contains the smart contracts and off-chain services that combine cross-chain calls into user-facing workflows. Cross-chain DEX aggregators, multi-chain governance systems, and enterprise workflow engines sit here.

Security enforcement belongs at the protocol and verification layer, not the application layer. Teams that push trust assumptions into application logic can end up with systems where a single compromised contract drains funds across multiple chains.

Message-passing designs should pass verified, finalized state. The application layer should never be the first place a message’s authenticity is checked.

Which infrastructure services do multi-chain crypto platforms use?

Multi-chain crypto platforms rarely build their own bridges. They assemble the stack from specialized infrastructure services, each mapping to one of the layers above:

• Messaging and verification networks: LayerZero, Chainlink CCIP, Wormhole, Axelar, and Hyperlane deliver and verify messages between chains.
• Cross-chain token standards: LayerZero’s OFT, Wormhole’s NTT, and Axelar’s ITS keep one token supply across chains, while Circle’s CCTP moves native USDC by burning and minting it.
• Intent and solver networks: Across, Relay, and deBridge fill transfers from solver inventory for speed.
• Wallet connectivity: WalletConnect links wallets and apps across chains through one integration.
• Compliance engines: Chainlink’s Automated Compliance Engine, integrated with CCIP 2.0, applies issuer-defined eligibility checks, approvals, and transaction limits.
• Analytics and monitoring: Dashboards such as DefiLlama track cross-chain flows, and monitoring services compare minted supply against locked collateral in real time.

What should I consider when choosing a blockchain API for my project?

Blockchain APIs facilitate Web3 development by giving applications a standard way to read chain data, submit transactions, and track cross-chain messages without running their own nodes on every network. When choosing one for a multi-chain project, check:

1. Chain coverage: Does the API support every chain and testnet you need, with consistent identifiers such as CAIP-2 chain IDs so multi-chain code stays portable?
2. Reliability: Look for published uptime figures, failover across regions, and clear handling of reorgs and finality.
3. Data depth: Decide whether raw RPC access is enough or you need indexed data such as balances, token transfers, and cross-chain message status.
4. Wallet integration: If you build wallet features, confirm support for WalletConnect sessions and EIP-6963 wallet discovery.
5. Security and compliance: Ask how keys and user data are handled and whether independent audits or SOC 2 reports exist.
6. Limits, pricing, and lock-in: Compare rate limits and overage costs, and keep a standard JSON-RPC interface so you can switch providers.

What are the top bridging solutions for interoperability layers?

The top bridging solutions for interoperability layers in November 2026 are Circle’s CCTP, LayerZero, Across, Relay, Chainlink CCIP, and Wormhole by volume, with IBC, Hyperlane, Axelar, and deBridge serving specific ecosystems and use cases. No single solution is best for every route: the right choice depends on the verification model you can accept, the chains you need, and who already relies on the system.

Blockchainreporter’s comparison of the main bridges (November 2026) combines each protocol’s verification model with its chain coverage, DefiLlama’s 30-day volume to November 3, 2026, and notable users named on official sites or by major outlets. Chain counts come from each protocol’s own site where it publishes one, otherwise from DefiLlama’s tracking.

How to read the table: volume measures usage, not safety. DefiLlama tracks a subset of each protocol’s chains and lists some LayerZero-based products, such as USDT0 and Stargate, separately, so protocols’ own chain counts can be higher than DefiLlama’s. A lower-volume protocol such as Hyperlane or Axelar can still be the right choice for a specific chain pair or an institutional token deployment.

Three patterns stand out in 2026:

1. Stablecoins dominate cross-chain flow. Circle’s CCTP and Tether’s USDT0 together accounted for about 42% of the 30-day bridge volume DefiLlama tracked to November 3, 2026.
2. Intent-based bridges rival messaging bridges for user transfers. Across, Relay, and deBridge moved about $10.5 billion in those 30 days, compared with LayerZero’s $12.5 billion.
3. Institutions choose on verification and compliance. After the April 2026 Kelp DAO exploit, Kelp, Kraken, and Lombard moved to Chainlink, and CCIP 2.0 added institution-run verifiers, according to Decrypt.

How do you choose the best crypto bridge for a transfer?

The best crypto bridge for a given transfer is usually the route the asset’s issuer supports, not the bridge with the highest volume. A practical order of checks:

1. Use the native route when one exists: Circle’s CCTP for USDC, USDT0 for Tether’s omnichain USDT, or a network’s canonical bridge, such as the Polygon, Arbitrum, Optimism, or Base bridges that DefiLlama tracks.
2. Compare intent bridges for speed: Across, Relay, and deBridge fill most transfers between major chains in seconds from solver capital.
3. Check the verification model and incident history in the comparison table above before moving large amounts.
4. Confirm the destination token is the official asset, not an unofficial wrapped copy, by checking the contract address on the issuer’s site, CoinGecko, or CoinMarketCap.
5. Send a small test transfer first and keep the transaction hash until the funds arrive.

Major security risks, the interoperability trilemma, and practical mitigations

The interoperability trilemma

The interoperability trilemma, analogous to the blockchain trilemma, states that a cross-chain system can optimize for at most two of three properties simultaneously: trustlessness (no honest-majority assumption), extensibility (works across many heterogeneous chains), and generalizability (supports arbitrary message types, not just asset transfers). The case for interoperability is also laid out in this piece on preventing a Web3 collapse through multichain compatibility.

IBC maximizes trustlessness and generalizability but requires chains to implement IBC natively, limiting extensibility. Federated bridges maximize extensibility and generalizability but sacrifice trustlessness. ZK bridges move toward trustlessness and generalizability but remain expensive and chain-specific in their current form.

Where incidents concentrate

Bridge exploits have caused around $3 billion in documented losses, according to a survey published in Communications of the ACM. Most losses trace to three root causes: private-key compromise of validator or multisig sets, logic errors in lock-and-mint contracts, and replay attacks enabled by missing nonce or chain-ID validation.

In the survey’s words, “around USD $3B in losses happened only in blockchain bridges” (Communications of the ACM). That count predates the 2026 incidents below.

The pattern is consistent. The weakest link is almost never the underlying chain’s consensus, but the bridge’s own custody and verification logic.

Bridge exploits in 2026

• Kelp DAO rsETH bridge, April 18, 2026 (about $292 million): At 17:35 UTC an attacker tricked LayerZero’s messaging layer into accepting a forged instruction, and Kelp’s bridge released 116,500 rsETH, about 18% of the token’s supply, according to CoinDesk. Kelp’s pauser multisig froze its contracts 46 minutes later, and Aave, SparkLend, and Fluid froze rsETH markets. The bridge relied on a single verifier (a 1-of-1 DVN setup); LayerZero later apologized for its response and admitted fault in the single-verifier setup (The Block), and Decrypt reported that hackers linked to North Korea’s Lazarus Group carried out the attack. Kelp’s developer, Evercrest Technologies, sued LayerZero Labs and its CEO in the Supreme Court of British Columbia in September 2026; LayerZero disputes Kelp’s account.
• NEAR Intents, October 1, 2026 (about $3.8 million): NEAR Intents paused its cross-chain swap services after a bug in how its Omni deposit and withdrawal system interacted with its smart contract, and said in its preliminary report that affected users would be reimbursed in full.
• Cysic bridge, October 17, 2026: The Cysic Foundation said an attacker combined unauthorized access to a database supporting bridge services with a flaw in message-processing logic to mint 10 million CYS tokens on BNB Smart Chain, and about 7.2 million had moved before the receiving address was frozen.

In each 2026 case the underlying chains kept working. The failures sat in verifier configuration, off-chain infrastructure, or contract logic, which is exactly where the mitigations below apply.

Mitigation checklist

• Prefer light-client or ZK-proof verification over multisig custody wherever the chain pair supports it
• Never run a production route on a single verifier; require at least two independent verifier networks or signers from separate organizations
• Apply formal verification to all bridge and messaging contracts before mainnet deployment
• Use modular adapter designs so a compromised adapter can be swapped without redeploying the core protocol
• Implement on-chain timelocks, rate limits, and dispute windows for high-value transfers (optimistic security)
• Distribute validator or relayer sets with economic slashing to deter collusion
• Run continuous bug-bounty programs and schedule third-party security audits at each major upgrade
• Monitor for anomalous mint/burn ratios in real time; a wrapped asset supply that exceeds locked collateral is an early exploit signal
• Keep an emergency pause with clear authority and rehearse it; Kelp’s pause came 46 minutes after the April 2026 drain

How do you secure bridging across permissioned chains?

Permissioned chains, such as bank ledgers and private enterprise networks, add requirements that public bridges were not built for: known participants, confidentiality, legal finality, and compliance checks before value moves. The best ways to secure bridging across permissioned chains in 2026 are:

1. Keep assets on the institution’s own ledger and coordinate transfers. Chainlink said at Sibos on September 28, 2026 that it is enabling banks to connect their systems and key-signing infrastructure to Swift’s blockchain ledger through the Chainlink Runtime Environment, so tokenized deposits stay on banks’ balance sheets and banks keep control of the keys that authorize transactions. Swift first tested CCIP with banks including Citi and BNY Mellon in 2023.
2. Add verification you control. CCIP 2.0 lets issuers run Cross-Chain Verifiers themselves, or hire firms such as Infosys or Nethermind, on top of Chainlink’s default network, so a transfer executes only after the institution’s own check passes.
3. Enforce compliance before execution. Chainlink’s Automated Compliance Engine applies issuer-defined eligibility checks, approvals, and transaction limits inside CCIP 2.0 rather than in a separate application.
4. Use attestors or light clients instead of a single relayer. IBC supports attestors for permissioned networks and consensus or zero-knowledge light clients for permissionless ones, according to the IBC protocol site.
5. Synchronize privacy-preserving ledgers rather than exposing them. Canton Network describes its Global Synchronizer as the decentralized interoperability backbone of a privacy-enabled network for regulated markets, and DTCC announced its tokenization service on Canton as live on October 28, 2026.
6. Choose finality per transfer. CCIP 2.0 lets issuers choose faster-than-finality transfers or wait for full source-chain finality; reserve fast settlement for amounts the institution can afford to unwind.
7. Never accept a single point of verification. The Kelp DAO exploit showed that one verifier can be the only barrier between a forged message and hundreds of millions of dollars.

Pro Tip: Design every cross-chain state transition to be explicitly recoverable. Define what “failure” looks like at the protocol level, not just in application logic. A packet that times out should revert the source-chain state atomically; a message that arrives with an invalid proof should be rejected with a logged reason code, not silently dropped. Systems that handle failure gracefully are dramatically easier to audit and far less likely to leave funds in an unrecoverable limbo state.

Representative projects and concrete cross-chain use cases

IBC / Cosmos

IBC defines a transport, authentication, and ordering protocol that participating chains implement at the consensus layer. Two chains establish a connection by running light clients of each other, while permissionless off-chain relayers submit cryptographic proofs.

The IBC protocol site counts more than 115 connected chains and more than $50 billion in transaction volume since 2021, and lists Ethereum, Hyperledger Besu, and Cardano among IBC-connected ledgers. For permissioned networks, IBC can use attestors in place of light clients.

The trust model is as close to trustless as current technology allows for heterogeneous chains. Production use cases include cross-chain token transfers across the Cosmos ecosystem, cross-chain staking, and interchain accounts that let one chain’s contract control an account on another.

The primary risk is that IBC requires native implementation. Connecting a non-IBC chain therefore requires a gateway or bridge at the boundary.

Polkadot / XCMP

Polkadot’s relay chain provides shared security for connected parachains. Parachains exchange XCM messages over HRMP channels routed through the relay chain, so the full validator set backs the security of each cross-parachain message.

This eliminates the bridge-custody problem within the ecosystem. The trade-off is that each parachain must buy coretime on the relay chain under Polkadot’s Agile Coretime model, which replaced the earlier parachain slot auctions, and connecting to chains outside the Polkadot ecosystem still requires a bridge.

Platform choice directly affects security, governance, and integration complexity in ways that are difficult to change after deployment.

Chainlink CCIP

Chainlink’s Cross-Chain Interoperability Protocol uses a decentralized oracle network to relay messages and verify state across chains. By default, a committee of 16 independent node operators checks each message, according to Decrypt.

CCIP 2.0, launched on September 28, 2026, lets issuers add Cross-Chain Verifiers run by their own teams or by third parties such as Infosys and Nethermind, choose faster-than-finality or full-finality transfers, and apply Chainlink’s Automated Compliance Engine. Chainlink says CCIP secures more than $84 billion in cross-chain token value and that $15 billion in tokenized assets moved to its rails in the four months before launch, both self-reported figures cited by Decrypt.

CCIP’s separate Risk Management Network, long presented as an independent second check that could halt transfers, no longer plays its automated off-chain role in current deployments, according to Chainlink’s documentation as reported by Decrypt; it is expected to return as an optional validation layer.

The trust model is federated but now lets each institution add its own defense layer. Production deployments include cross-chain token transfers for institutional DeFi and institutional asset flows where auditability and compliance hooks matter. Kelp DAO, Kraken, and Lombard Finance moved to Chainlink after the April 2026 Kelp exploit, and parts of Coinbase’s cbBTC and BitGo’s wrapped bitcoin migrated to CCIP, according to Decrypt.

The risk note: security depends on the oracle network’s honest-majority assumption, and an issuer that adds no verifiers of its own relies on a single verification network.

LayerZero

LayerZero V2 makes security configurable per application. Each app chooses one or more Decentralized Verifier Networks (DVNs) that must attest to a message, and an Executor delivers the message on the destination chain; the original V1 design paired an Oracle with a Relayer.

LayerZero carried $12.5 billion in the 30 days to November 3, 2026 across 113 chains tracked by DefiLlama, the second-largest total after Circle’s CCTP, and products built on it, including Tether’s USDT0 and the Stargate bridge, add more.

That flexibility is also the risk. Kelp DAO’s rsETH bridge ran on a single DVN when it was drained in April 2026 (details in the exploit section above), and Decrypt reported that LayerZero then stopped supporting that configuration for new deployments.

Axelar

Axelar operates as a proof-of-stake blockchain dedicated to cross-chain routing. Validators on the Axelar network, more than 75 according to Axelar’s site, observe events on connected chains and reach consensus before relaying messages. Its Interchain Token Service reaches more than 80 blockchains.

The model is closer to a notary scheme, with economic security from staked AXL. It supports general message passing and is used in production for cross-chain DeFi, NFT transfers, and tokenized-asset workflows, including a J.P. Morgan Onyx case study on portfolio rebalancing that Axelar features.

On December 15, 2025, Circle agreed to acquire the team and proprietary intellectual property of Interop Labs, Axelar’s initial developer, to accelerate its Arc and CCTP roadmaps, with closing expected in early 2026. Circle said the Axelar network, its foundation, and the AXL token would continue to operate independently under community governance, with Common Prefix taking over Interop Labs’ activities.

The risk is that the Axelar validator set is the trust anchor. A supermajority compromise would be catastrophic.

Wormhole

Wormhole uses a set of 19 Guardian nodes, run by established validator companies, that observe and attest to cross-chain messages. A quorum of 13 of 19 signatures is required to produce a valid attestation.

Wormhole supports more than 45 blockchains and reports about $68 billion in all-time transfer volume on its website. It also matters for tokenized assets: Securitize named Wormhole its official interoperability provider, and BlackRock’s BUIDL fund and Apollo’s ACRED fund use it for cross-chain transfers, according to Wormhole’s blog.

XRPL is among the networks that adopted it; in June 2025, Ripple integrated Wormhole to improve multichain interoperability on the XRP Ledger.

The 2022 exploit that drained about $320 million resulted from a signature verification flaw in the Solana contract, not a Guardian compromise. The incident shows that contract-level bugs are as dangerous as validator-set attacks.

Hyperlane

Hyperlane is a permissionless interoperability protocol: any team can deploy it to a new chain without approval from the core team, and each application chooses the security modules that verify its messages. Hyperlane’s site lists more than 150 chains across 7 virtual machines and more than $10 billion bridged, with case studies from Paradex, M0, and Aerodrome.

The trade-off mirrors LayerZero. Configurable security is only as strong as the modules an application selects, so teams must treat module choice as a security decision, not a default.

Across, Relay, and deBridge

Across, Relay, and deBridge are the leading intent-based bridges. Across says it has moved more than $40 billion for about 5 million users through a permissionless relayer network, with average fills of 1.2 seconds and no user funds lost. deBridge reports a median settlement time of 1.96 seconds, zero security incidents since launch, and more than 26 audits. Relay carried $4.65 billion in the 30 days to November 3, 2026, across 78 chains tracked by DefiLlama.

Intent bridges limit how much pooled liquidity is at risk, but they depend on solver capital and on the system that verifies solver repayments.

ERC-7786 and cross-chain messaging interfaces

ERC-7786 defines a standard gateway interface for cross-chain messaging. Instead of locking applications to a specific messaging protocol, it specifies a common API: a source gateway exposes a sendMessage function, and destination gateways deliver payloads to the recipient’s receiveMessage function, with sender and recipient written in the ERC-7930 interoperable address format.

ERC-7786 has reached Final status on eips.ethereum.org (checked November 3, 2026), so it is no longer just a proposal. It reduces vendor lock-in and lets applications switch underlying messaging networks without rewriting their contracts.

Cross-chain solutions for real-world assets

Tokenized funds and securities increasingly live on several chains at once, and issuers use interoperability protocols to keep one unified supply and ownership record:

• BlackRock BUIDL (via Securitize): Securitize named Wormhole its official interoperability provider, and BUIDL expanded to chains including BNB Chain and Solana with Wormhole-powered interoperability, according to Wormhole’s blog.
• Apollo ACRED: Securitize’s tokenized Apollo Diversified Credit fund uses Wormhole for transfers to Ink and Sei.
• J.P. Morgan Asset Management: On October 22, 2026, the firm made its MONY and JLTXX tokenized money market funds available on Solana to qualified U.S. investors, adding a second chain for the funds.
• Chainlink CCIP 2.0: Chainlink says $15 billion in tokenized assets moved to its rails in the four months before September 28, 2026, and 18 companies were listed as launch partners, according to Decrypt.
• DTCC on Canton: Canton Network’s site promotes the DTCC Tokenization Service on Canton for DTC-custodied tokenized U.S. Treasuries, equities, and ETFs, which DTCC announced as live on October 28, 2026.

The design lesson for real-world assets is that transfer restrictions, investor eligibility, and transfer-agent records must travel with the token. That is why RWA issuers favor native or burn-and-mint token standards with compliance hooks over wrapped tokens held in a pool. For a builder’s view of compliant RWA infrastructure, see our interview on real-world asset tokenization.

Use cases across domains

• DeFi: Cross-chain DEX aggregators route swaps through the cheapest or deepest pool regardless of which chain it sits on. Cross-chain lending lets collateral on one chain back a loan on another.
• Payments: Chainlink says it is connecting banks to Swift’s blockchain ledger for 24/7 cross-border payments with tokenized deposits that stay on banks’ balance sheets (Sibos, September 2026).
• NFTs: Interoperable provenance records let an NFT’s ownership history follow it across chains. Cross-chain royalty enforcement is an active area of development.
• Gaming: In-game assets minted on a high-throughput gaming chain can be traded on a mainnet marketplace without wrapping or manual bridging.
• Enterprise supply chain: A permissioned ledger tracking goods can write verified state to a public settlement chain for payment release. This eliminates the manual reconciliation that currently adds days to trade-finance cycles.

A practical checklist for teams building cross-chain systems

1. Define the trust boundary first. Decide whether your application can tolerate an honest-majority assumption or requires cryptographic trustlessness. This decision narrows your mechanism options before any other evaluation.
2. Choose multi-chain over cross-chain when security is critical. Deploying natively on multiple chains through a shared framework (IBC, Polkadot) eliminates bridge custody risk within that ecosystem. Reserve cross-chain bridges for cases where multi-chain deployment is not feasible.
3. Prefer light-client or ZK-proof verification, and never rely on a single verifier. If the chain pair supports it, cryptographic verification is preferable to a federated validator set. On configurable networks such as LayerZero or Hyperlane, require at least two independent verifiers; the Kelp DAO exploit showed the cost of one.
4. Audit every contract in the cross-chain path. The bridge contract, the messaging adapter, the receiving contract, and any oracle or relayer interface all need independent security audits. A flaw in any one of them can drain the entire system.
5. Implement timelocks and circuit breakers. High-value transfers should have a delay window during which anomalies can be detected and halted. Monitor wrapped-asset supply against locked collateral continuously.
6. Standardize schemas at the semantic layer early. Agree on data formats, asset identifiers, and event schemas before building application logic. Retrofitting schema mapping onto a live system is expensive and error-prone.
7. Build for explicit failure modes. Every cross-chain call should have a defined timeout and a revert path. Test timeout and partial-failure scenarios as rigorously as the happy path.
8. Run cross-chain fuzzing in staging. Standard unit tests rarely catch edge cases that appear when two chains have different block times, finality rules, or reorg depths. Fuzzing tools that simulate chain-level conditions catch these earlier.
9. Capture telemetry on relayer latency, packet acknowledgment rates, and proof-verification failures. These metrics surface degradation before it becomes an incident. A blockchain explorer integrated into your monitoring stack helps inspect cross-chain transactions in real time.
10. Review regulatory and compliance requirements for your jurisdiction. Cross-chain asset transfers may trigger reporting obligations, AML screening requirements, or securities regulations depending on the asset type and the chains involved. The CLARITY Act debate and MiCA implementation are active examples of how regulatory frameworks are catching up to cross-chain activity.
11. Establish a governance framework for protocol upgrades. Who can change the bridge parameters? What is the upgrade delay? How are validator set changes approved? Governance gaps are as dangerous as code bugs.

Additional developer notes:

• Use simulation environments that replicate both chains’ finality rules before deploying to testnet
• Define fallback strategies for partial failures: what happens if the destination chain is congested and a packet times out?
• Rehearse incident response with real roles and keys, and follow post-mortems of past incidents, such as those collected in our blockchain security coverage

Standards, emerging proposals, and the future of blockchain interoperability

The lack of universal standards is the single biggest structural barrier to cross-chain interoperability today. Standards such as IBC, ERC-7786, and ERC-7683 respond directly to the fragmentation that forces every application to choose a vendor and accept lock-in.

Current standards and proposals:

• IBC (Inter-Blockchain Communication): A fully specified, production-deployed protocol covering transport, authentication, and ordering for any IBC-compatible chain. IBC v2 slimmed the protocol so chains outside Cosmos can adopt it, and projects such as Datachain’s ibc-solidity extend IBC to EVM chains and enterprise ledgers. IBC is the closest thing to a ratified standard in the public blockchain space.
• ERC-7786 (Final): A standard gateway interface for cross-chain messaging. It defines how smart contracts send and receive arbitrary payloads through any conforming gateway, so applications can swap messaging networks without rewriting contracts.
• ERC-7683 (Draft): Cross Chain Intents, created in April 2024, defines a solver-facing interface in which intent protocols expose orders that a resolver contract translates into common steps and payments, so solvers can support new protocols without custom integration work.
• ERC-7930 (interoperable addresses): A chain-aware address format that both ERC-7786 and ERC-7683 reference, so one string identifies an account and the chain it lives on.
• ISO and industry consortia efforts: ISO/TC 307 develops international blockchain and distributed ledger standards, from vocabulary and reference architecture to governance. Enterprise consortia, including Hyperledger projects, are working on connector specifications for permissioned-to-public chain integration.
• CCIP as a de facto standard: Chainlink’s CCIP has enough production adoption that its message format and token-transfer interface are becoming reference points for enterprise integrations, even without formal standardization.

What changed since 2025

• 2025: IBC v2 was scheduled for launch at the end of March 2025, and Ethereum’s Pectra upgrade on May 7, 2025 brought EIP-7702 smart-account features to ordinary wallets.
• 2025: The Ethereum Foundation set out an interoperability framework meant to make layer 2 networks feel like one chain, according to The Block.
• December 15, 2025: Circle agreed to acquire the Interop Labs team, Axelar’s initial developer.
• April 18, 2026: The Kelp DAO rsETH bridge exploit (about $292 million) exposed the risk of single-verifier configurations.
• May and July 2026: The BIS reported on May 27 that Project Agorá’s prototype was delivered, and real-value testing followed in July.
• September 28, 2026: Chainlink launched CCIP 2.0 and outlined how it connects banks to Swift’s blockchain ledger.
• October 2026: NEAR Intents (October 1) and Cysic (October 17) suffered exploits, J.P. Morgan Asset Management added Solana for two tokenized funds (October 22), and DTCC’s tokenization service on Canton went live (October 28).
• November 3, 2026: ERC-7786 is Final, ERC-7683 is still a Draft, and DefiLlama tracked $48.8 billion in 30-day bridge volume. For market context, bitcoin traded near $76,900 at 10:40 UTC (CoinMarketCap), and the Crypto Fear and Greed Index read 26, Fear, on November 3 (alternative.me).

What is the future of blockchain interoperability?

Five trends define where blockchain interoperability is heading after 2026:

1. Intents replace manual bridging. Users state the result they want and solvers compete to deliver it. ERC-7683 aims to give solvers one interface for many intent protocols, and Across alone reports more than $40 billion moved.
2. Chain abstraction hides the chain. Wallets and apps show one balance while the interoperability layer routes funds behind the scenes. ERC-4337 and EIP-7702 smart accounts, plus ERC-7930 interoperable addresses, are the building blocks.
3. Shared sequencing and native rollup interoperability. Shared sequencers order transactions for several rollups at once, which can make cross-rollup actions atomic; Espresso Systems raised a $28 million Series B led by a16z crypto to build a shared sequencing marketplace (The Block). The Ethereum Foundation’s interoperability framework pursues the same goal of making layer 2 networks feel like one chain.
4. Verifier diversity becomes the norm. After the Kelp exploit, CCIP 2.0 added institution-run verifiers and LayerZero stopped supporting single-verifier setups for new deployments, according to Decrypt.
5. Institutional rails converge with public chains. Swift’s blockchain ledger, DTCC’s tokenization service on Canton, and BIS Project Agorá all test how tokenized deposits, securities, and central bank money can interoperate with public networks.

The expected direction over the next few years follows a clear path. Specification (where ERC-7683 sits now) leads to adapter adoption (ERC-7786 gateways), and production norms and governance frameworks could then lower switching costs enough to break vendor lock-in.

Semantic interoperability is the hardest layer to standardize, and the most work remains there. Chains can exchange valid packets today, but they still need agreement on what those packets mean across different asset models, governance structures, and legal jurisdictions.

Technical standards without shared data semantics and governance produce systems that are connected but not truly interoperable.

Which standards make digital wallets interoperable?

Wallet interoperability means one wallet can connect to many apps and chains, and one app can work with many wallets, without custom integrations for each pair. Six standards do most of that work in 2026:

For users, the practical effect is fewer wrong-network errors and fewer manual bridges: a chain-abstracted wallet can show one balance and route a payment across chains in the background, using the interoperability protocols compared above. For developers, supporting EIP-6963 and WalletConnect covers most wallet connections, while CAIP identifiers and ERC-7930 addresses help prevent funds from being sent to the right address on the wrong chain.

Security still sits with the wallet. Smart accounts add recovery options and spending limits, but a delegated EIP-7702 account is only as safe as the contract it delegates to, so wallets should show users exactly what they are signing. Compare individual wallets in our crypto wallet reviews.

What are the characteristics of an open, interoperable digital currency?

An open, interoperable digital currency is money that keeps the same value and legal standing wherever it moves, across wallets, platforms, blockchains, and payment systems, without a closed network deciding who can use it. Its main characteristics are:

1. Singleness: One unit is always worth one unit, whichever issuer, platform, or chain holds it. The BIS 2025 Annual Economic Report tested stablecoins against singleness, elasticity, and integrity and found them lacking.
2. Settlement finality and atomicity: Transfers settle irrevocably, and both legs of a trade can settle together. Project Agorá tests atomic settlement of tokenized commercial bank deposits and tokenized central bank reserves on a shared programmable platform.
3. Open standards and access: Common token, address, and messaging standards, such as ERC-7786 and CAIP identifiers, let any compliant wallet or institution connect.
4. Native multi-chain issuance: The issuer controls supply on every chain, as with Circle’s burn-and-mint CCTP for USDC or issuer-controlled standards such as LayerZero’s OFT, so wrapped copies do not fragment value.
5. Programmability with guardrails: Smart contracts can automate payments and conditions, but within rules set by the issuer and the regulator.
6. Compliance and integrity built in: KYC, sanctions screening, and transfer limits run at the protocol level, as with Chainlink’s Automated Compliance Engine in CCIP 2.0; in the United States, the GENIUS Act sets the rules for payment stablecoin issuers.
7. Privacy suited to regulated markets: Counterparties see what they need and no more, the design goal of privacy-enabled networks such as Canton.
8. Clear governance: Defined operators, upgrade processes, and dispute handling, because a payment network is only as trustworthy as its rulebook.

Where Project Agorá and mBridge stand

• Project Agorá: A BIS Innovation Hub project with central banks including the Bank of England, the Bank of France (for the Eurosystem), the Bank of Japan, the Bank of Korea, and the Swiss National Bank, plus more than 40 financial institutions convened by the Institute of International Finance. The BIS lists it as ongoing: its May 27, 2026 report said the prototype was delivered, real-value testing took place in July 2026 with 28 financial institutions and central banks completing transactions, and the next phase envisions an enhanced role for the private sector.
• Project mBridge: A multi-CBDC platform for instant cross-border payments developed with the Hong Kong Monetary Authority, the Bank of Thailand, the People’s Bank of China’s Digital Currency Institute, and the Central Bank of the UAE, with the Saudi Central Bank joining in 2024. It reached the minimum viable product stage in mid-2024, the BIS handed the project over to the partners in October 2024, and the BIS now lists its involvement as concluded.

Frequently Asked Questions

What is blockchain interoperability?
Blockchain interoperability is the ability of separate blockchains to exchange assets, messages, and verified state without a central intermediary holding the funds. It works through light-client protocols such as IBC, messaging networks such as LayerZero, Chainlink CCIP, Wormhole, Axelar, and Hyperlane, intent-based bridges such as Across, and issuer protocols such as Circle’s CCTP. Security depends on who verifies messages between chains.

How does cross-chain interoperability work?
Cross-chain interoperability works in three steps. An application on the source chain emits a message or locks or burns tokens, a verifier proves that the event happened, and a contract on the destination chain checks the proof and executes, for example by minting tokens. Designs differ mainly in the verifier: light clients, validator committees, optimistic watchers, solvers, or zero-knowledge proofs.

Which are the most popular blockchain bridge platforms today?
Measured by DefiLlama’s 30-day volume to November 3, 2026, the most popular are Circle’s CCTP at $17.6 billion, LayerZero at $12.5 billion, Across at $5.7 billion, Relay at $4.65 billion, Tether’s USDT0 at $2.9 billion, and Chainlink CCIP at $1.3 billion. Wormhole’s Portal, Stargate, deBridge, IBC, Hyperlane, and Axelar follow. Popularity shows usage, not safety.

What are the main blockchain interoperability protocols?
The main protocols fall into four groups. Messaging networks include LayerZero, Chainlink CCIP, Wormhole, Axelar, and Hyperlane. Native frameworks include IBC for Cosmos and other IBC-connected chains, and XCM for Polkadot. Token standards include LayerZero’s OFT, Wormhole’s NTT, Axelar’s ITS, and Circle’s CCTP. Intent protocols such as Across, Relay, and deBridge fill transfers with solver capital.

What is the future of blockchain interoperability?
Interoperability is moving from manual bridging toward intents, chain abstraction, and shared standards. ERC-7786 for cross-chain messaging reached Final status, ERC-7683 for cross-chain intents is still a draft, and Chainlink’s CCIP 2.0 lets institutions add their own verifiers. Shared sequencing and Ethereum’s interoperability work aim to make many layer 2 networks feel like one chain.

What are the best ways to secure bridging across permissioned chains?
Use several independent verifiers, keep assets on the institution’s own ledger where possible, and enforce compliance before a transfer executes. Chainlink’s CCIP 2.0 supports institution-run Cross-Chain Verifiers, IBC supports attestors for permissioned networks, and Canton Network synchronizes privacy-preserving ledgers. Add rate limits, timelocks, strict key management, independent audits, and real-time monitoring of minted supply against reserves.

Which standards make digital wallets interoperable?
WalletConnect links more than 700 wallets with tens of thousands of apps through one integration. CAIP identifiers describe chains, accounts, and assets in a chain-agnostic format, and EIP-6963 lets browser apps detect every installed wallet. ERC-4337 smart accounts and EIP-7702, live since Ethereum’s Pectra upgrade in May 2025, add batching, gas sponsorship, and programmable security.

What are the characteristics of an open, interoperable digital currency?
An open, interoperable digital currency keeps one unit worth one unit on every platform and chain, settles with finality, follows open technical standards, and works with many wallets and payment systems. It also needs built-in compliance, privacy suited to regulated markets, controlled programmability, and clear governance. The BIS-led Project Agorá is testing these properties with tokenized deposits and central bank reserves.

How do real-world assets move across blockchains?
Issuers usually deploy a tokenized asset on several chains and use an interoperability protocol to keep one unified supply and ownership record. BlackRock’s BUIDL fund, issued through Securitize, uses Wormhole, Chainlink says $15 billion in tokenized assets moved to CCIP in four months, and J.P. Morgan Asset Management added Solana for two tokenized money market funds in October 2026.

What infrastructure services do multi-chain crypto platforms need?
Most multi-chain platforms combine a messaging or bridging network, a token standard that keeps supply unified across chains, solver networks for fast transfers, wallet connectivity, compliance controls, and monitoring. Common choices include LayerZero’s OFT, Wormhole’s Native Token Transfers, Axelar’s Interchain Token Service, Circle’s CCTP for USDC, intent networks such as Across and Relay, and WalletConnect for wallet sessions.

Are cross-chain bridges safe in 2026?
Bridges remain one of the riskiest parts of crypto infrastructure. A Communications of the ACM survey counts around $3 billion in bridge losses, and on April 18, 2026 an attacker drained about $292 million of rsETH from Kelp DAO’s LayerZero-based bridge, which relied on a single verifier. Safety depends on the verification model, verifier diversity, audits, rate limits, and incident response.

What are the most effective blockchain scalability solutions available today?
Layer 2 rollups are the most common way to scale Ethereum today: they execute transactions away from the main chain and post data or proofs back to it. App-specific chains and high-throughput layer 1 networks are the other main approaches. Every approach adds networks, so scalability depends on interoperability: rollup bridges, shared sequencing, and messaging protocols let users move between them safely.

What engineers and decision-makers should prioritize now

The field has matured enough that the core design question is no longer “should we use interoperability?” but “which trust model can we actually defend?” Most teams underestimate how much of their security posture is determined by that choice, which is often made before the first line of application code is written.

Verification-first design is the clearest priority. If the chain pair supports light-client proofs or ZK validity proofs, use them. Where you rely on a configurable messaging network, require several independent verifiers; the April 2026 Kelp DAO loss came down to one. The performance cost of stronger verification is real but shrinking as proof-generation hardware and algorithms improve.

The alternative, a federated multisig with 5 or 7 signers, is cheaper today and catastrophically expensive when one key is compromised.

Schema standardization deserves attention earlier than most teams give it. The semantic layer is where interoperability quietly fails in production: two chains exchange valid, verified packets, and the receiving contract misinterprets the asset identifier or decimal precision.

Fixing this after launch requires coordinated upgrades across every chain in the system.

For decision-makers evaluating platforms, the governance structure of the interoperability layer matters as much as the cryptography. Who controls the validator set? What is the upgrade process? What happens when a connected chain forks?

These questions have answers in IBC and Polkadot’s designs. They are often unanswered in bespoke bridge deployments.

Blockchainreporter covers the technical and market developments shaping cross-chain infrastructure continuously. For ongoing analysis of how interoperability shifts liquidity flows and institutional positioning, the site’s market coverage tracks the real-world signals that matter to both engineers and decision-makers.

Sources

For engineers working on specifications and implementation:

• A brief history of blockchain interoperability, Communications of the ACM
• ERC-7786: Cross-Chain Messaging Gateway (Ethereum Improvement Proposals)
• ERC-7683: Cross Chain Intents (Ethereum Improvement Proposals)
• IBC protocol
• Wormhole Guardians documentation
• DefiLlama bridge volume rankings

For policy, governance, and enterprise readers:

• The current state of interoperability between blockchain networks (EU Blockchain Observatory report)
• BIS Innovation Hub: Project Agorá
• BIS Innovation Hub: Project mBridge
• Chainlink: Sibos 2026 recap (CCIP 2.0 and Swift)
• Circle: agreement to acquire the Interop Labs team and intellectual property

Recommended

• Bybit.eu Secures EMI Licence In Austria Amid EU Compliance Shuffle
• Arthur Hayes: AI Boom Is A 2008-Style Infrastructure Bubble, And Bitcoin Will Benefit
• WhiteBIT Expands UK Offering With Automated Spot Trading Bots