Stablecoin interoperability: the N×N problem

Stablecoin interoperability is the ability to move value seamlessly between different stablecoins, blockchains, trading venues, and fiat rails, and its absence is the quietest, largest bottleneck in digital settlement. The problem compounds multiplicatively: every new token exists on multiple chains, trades on multiple venues, and must reach multiple fiat endpoints. Each pairing is an integration, a counterparty, and a point of failure. We call this the N×N problem, and this piece explains where it comes from, how value actually crosses chains today, and why solving it - not any single token or chain - is the real product of settlement infrastructure.

What is the N×N problem?

Count the dimensions. USDC is natively issued on more than twenty blockchains. USDT spans a dozen or more, plus bridged variants of both circulating on chains where they aren't native. Add the growing roster of regulated non-USD tokens - euro, dirham, yen, Singapore dollar - each choosing its own chains. Then multiply by the venues where these tokens trade against each other and against fiat, and by the banking rails needed at every fiat endpoint.

A business that wants to "accept stablecoins and settle in local currency" is not facing one integration. It is facing a matrix: tokens × chains × venues × fiat rails, where the number of possible pairings grows with the product of the dimensions, not the sum. Ten tokens on ten chains is not twenty integrations - it is a hundred token-chain combinations before a single venue or bank account enters the picture. This is why "stablecoin adoption" stalls in practice at exactly the moment it should accelerate: every additional option makes the integration burden worse, not better.

The industry's instinct - pick one chain, one token, one venue - doesn't solve the matrix; it just picks one cell of it and hopes counterparties live in the same cell. They don't. As we wrote in our manifesto: interoperability is not a feature of this market, it is the most valuable product.

How does value actually cross chains?

Three mechanisms dominate, with very different trust models:

Lock-and-mint bridges. The original pattern: tokens are locked in a contract on chain A, and a wrapped representation is minted on chain B. The wrapped token is only as good as the bridge securing the locked collateral, which is why bridges became crypto's single most expensive failure mode. The two largest exploits in the industry's history were bridge exploits: roughly $625 million (Ronin, 2022) and $325 million (Wormhole, 2022). Wrapped assets also fragment liquidity further, because a bridged variant is yet another token in the matrix, not a solution to it.

Burn-and-mint (native issuance transfer). The issuer itself burns tokens on the source chain and mints native tokens on the destination. No wrapped assets, no locked collateral pool to steal. Circle's CCTP is the reference implementation, live since 2023 and upgraded since for near-instant transfers. The trust model collapses to the issuer you already trusted. The limitation: it only works within one issuer's token, on the chains that issuer supports. It solves one row of the matrix, beautifully.

Liquidity networks. Pools of the asset on both chains, with transfers netted against the pools rather than bridged. Fast, no wrapped assets, but bounded by pool depth and dependent on rebalancing - thin pools mean slippage or failure at size, which matters enormously for the thin non-USD pairs we've written about before.

The honest summary: burn-and-mint where available, deep liquidity networks where not, lock-and-mint bridges as a last resort with eyes open. Routing among these - per token, per chain pair, per size - is itself an engineering discipline.

The dimensions everyone forgets

Cross-chain gets the attention, but two other dimensions of the matrix do as much damage:

Venue fragmentation. The same token on the same chain still lives in fragmented liquidity across exchanges, OTC desks, and market makers. Converting AED tokens to euro tokens at size is a routing problem across venues before it is ever a blockchain problem.

The fiat edge. Every settlement eventually touches a bank account, and banking rails are the least interoperable layer of all: jurisdiction-specific, counterparty-gated, cut-off-timed. A settlement stack that solves chains but not fiat edges has solved the easy half. This is where regulation becomes part of interoperability: a licensed conversion-and-custody perimeter (the PTSR's exact architecture) is what lets the fiat edge plug into the on-chain matrix lawfully.

What does solving it look like?

Not a winner chain. Not a winner token - denomination diversity is increasing, not decreasing. The solution is a layer: one integration that internalizes the matrix: every supported token, on every supported chain, against every connected venue and fiat rail, and exposes a single interface. Route selection, bridge risk policy, liquidity sourcing, and compliance checks happen inside the layer, invisibly. The customer's problem statement stays what it should have always been: send this value, in this currency, to this endpoint.

That layer is what Thiqwave builds - chain-agnostic by conviction, because betting the infrastructure on any single cell of the matrix repeats the industry's favorite mistake at a layer where it's unforgivable.

Frequently asked questions

What is stablecoin interoperability?
The ability to move value across different stablecoins, blockchains, trading venues, and fiat rails without bespoke integrations for every pairing.

What is the N×N problem?
The multiplicative growth of integration complexity: tokens × chains × venues × fiat rails. Each new option adds a dimension's worth of pairings, so the integration burden grows faster than the ecosystem's usefulness.

Are cross-chain bridges safe?
Lock-and-mint bridges have been the industry's most exploited component - the two largest hacks in crypto history were bridge exploits. Burn-and-mint transfers by the issuer and depth-bounded liquidity networks carry materially different, generally lower, risk profiles.

What is burn-and-mint transfer?
A mechanism where the token's issuer burns tokens on one chain and mints native tokens on another (Circle's CCTP is the best-known example) eliminating wrapped assets and locked collateral pools.

Why not just standardize on one blockchain?
Because counterparties, issuers, and venues never will. Regulated tokens are launching across different chains by design; infrastructure that assumes convergence is infrastructure that breaks on contact with the market.

Sources

• Circle, CCTP documentation

• Spark, stablecoin interoperability and the 2022 bridge exploits (Ronin, Wormhole)

• Chainalysis, 2025 Geography of Cryptocurrency Report