Skip to main content

Multi-Issuer Stablecoin Fungibility Standard

Multi-issuer stablecoin fungibility: atomic-swap primitives, primary-mint pooled inventory, dispute resolution, and the conformance standard for par redemption.

Written by Eco


Multi-issuer stablecoin fungibility is the property that lets a unit of one fiat-referenced stablecoin convert into a unit of another at par, atomically, with deterministic settlement finality. The stablecoin market reached $315.3B in circulating supply as of June 2026 per DeFiLlama, with USDT at $187.2B and USDC at $75.6B. Yet a USDC unit and a USDP unit do not clear 1:1 in size on any venue without spread, slippage, or counterparty exposure. That gap is a structural one. It sits between primary markets (where issuers like Circle, Tether, Paxos and Ripple mint and redeem against reserves) and secondary markets (where automated market makers, request-for-quote desks and exchange order books price the resulting tokens). This piece specifies the technical primitives, inventory model, dispute resolution path and conformance criteria a credible fungibility standard requires, and outlines how a neutral orchestration layer composes those primitives without taking principal risk.

The fungibility problem: why USDC and USDP do not trade 1:1 at scale

USDC, USDP and other regulated dollar stablecoins are each redeemable at par with their own issuer but not with each other. At institutional size, secondary venues quote a spread that reflects inventory imbalance, mint and redemption friction, and bridge latency. The result is fragmented price discovery and execution risk that scales with order size, not a true par market.

Each issuer operates a closed loop. Circle redeems USDC against bank reserves under its transparency program; Tether discloses reserves through its attestation cadence; Paxos publishes monthly attestations for USDP and PYUSD; Ripple publishes RLUSD reserve breakdowns. None of these loops are open to a counterparty holding a different issuer's liability. To move $50M from USDC to USDP, an institution must either route through a market maker who warehouses both, or redeem USDC to bank dollars and mint USDP on the other side. Both paths consume time, balance sheet, and basis risk.

The Bank for International Settlements documented this in its CPMI report Stablecoins in cross-border payments (October 2025), which identified non-uniform redemption rights and bilateral liquidity dependencies as the dominant frictions in cross-issuer flows. Cross-chain stablecoin volume averaged $1.4T monthly in Q1 2026 per Artemis Terminal, and almost all of it cleared within a single issuer's loop. The cross-issuer fraction remained a rounding error precisely because the conversion path lacks a standard.

Atomic-swap primitives: HTLCs, PTLCs, and the settlement-finality gap

Atomic-swap primitives let two parties exchange assets with the guarantee that both legs settle or neither does. Hashed Time-Lock Contracts and Point Time-Lock Contracts are the canonical implementations. Each binds release of asset A to disclosure of a secret that simultaneously unlocks asset B, with a timeout that reverts both legs if disclosure does not occur within the window.

A hashed time-lock contract locks tokens behind a hash preimage. Party A funds a contract releasing USDC to Party B on disclosure of preimage X. Party B funds a mirror contract releasing USDP to Party A on disclosure of the same X. When A claims, B observes the preimage onchain and claims in turn. If A never claims, both contracts refund after timeout. Point time-lock contracts replace the hash with an elliptic curve point, improving privacy and enabling adapter signatures.

The constraint is settlement finality. Stablecoin transfers on Ethereum reach probabilistic finality at roughly 12 minutes (two epochs); on Solana, optimistic confirmation lands in seconds but reorg windows persist. A swap whose two legs sit on chains with mismatched finality clocks inherits the slower clock as its effective settlement time. The Federal Reserve Financial Stability Report has flagged this finality heterogeneity as a constraint on stablecoin clearing at institutional scale. Atomic primitives close the credit gap but not the finality gap; the latter requires either an attestation layer (Circle's CCTP V2 launched March 11, 2025 with sub-30-second attestation per Circle) or a custodial netting layer that absorbs the timing difference.

Primary-mint pooled inventory: the reserve-backed conversion model

Primary-mint pooled inventory is a conversion model where authorized participants hold simultaneous primary-market access across multiple issuers, allowing direct mint of one stablecoin against redemption of another. The pool's reserves sit at each issuer's primary loop, so cross-issuer conversion executes at the sum of two primary-market frictions, not a secondary-market spread.

The model parallels the authorized-participant mechanism in exchange-traded funds. An AP in an SPDR fund holds creation-redemption access against the underlying basket, allowing arbitrage that anchors the fund's market price to net asset value. In stablecoins, an AP holds mint access at Circle and Paxos simultaneously, sufficient bank rails to clear redemption proceeds same-day, and onchain inventory to settle the buy-side leg. When a customer requests $50M USDC for USDP, the AP redeems $50M USDC to bank dollars at Circle, wires to Paxos, and mints $50M USDP, settling the customer leg from inventory and replenishing through the primary loop.

Pooled inventory is the institutional architecture that scales this. Multiple APs contribute primary-market capacity into a common pool, with each contribution tagged to its source issuer. The pool quotes a single par price plus a transparent fee covering bank rails, custody and operational cost. The IOSCO report on stablecoin policy recommendations describes this kind of mutualized primary-market access as a precondition for credible par redemption at market scale. The model preserves issuer neutrality because the pool is reserve-backed at each source, not synthetic.

What happens when an issuer de-pegs mid-swap? Dispute resolution mechanics

If an issuer de-pegs during an in-flight cross-issuer swap, dispute resolution defines which leg settles, which reverses, and how loss is allocated. A credible standard handles four cases: pre-commitment de-peg, mid-flight de-peg, post-confirmation de-peg, and disputed de-peg. Each case has a deterministic resolution rule keyed to attestation timestamps and reference price feeds, with no discretionary intervention.

Pre-commitment de-peg is the simplest. If a reference price oracle reports issuer A's stablecoin trading more than a defined band (commonly 50 basis points) below par at the moment the contract opens, the swap routes around A or fails open. Mid-flight de-peg is the hard case. If A de-pegs after Party 1 has funded the A leg but before Party 2 claims, the time-lock simply expires and both legs refund. The protocol does not attempt to value A's leg at the depressed price.

Post-confirmation de-peg sits outside the swap envelope. Once both legs claim, the swap is settled and counterparty risk transfers to the holder. Disputed de-peg, where oracles disagree on whether de-peg occurred, resolves through a quorum across independent reference rates. The Basel Committee and BIS have outlined oracle-quorum patterns in their work on tokenized settlement; the same architecture applies here. The standard must publish its oracle set, quorum threshold, dispute window and reference price methodology in advance. Discretion is not a dispute resolution mechanism. Determinism is.

Cross-issuer routing: how a stable-agnostic layer abstracts the choice

Cross-issuer routing abstracts the choice of which stablecoin to deliver into a single integration. The caller requests USD value into a destination address; the routing layer determines whether to source USDC, USDT, USDP, PYUSD or RLUSD based on inventory depth, primary-market access, destination-chain support, and customer policy. The execution path stays neutral across issuers.

The architectural pattern is a stable-agnostic interface above an orchestration substrate. Above the interface, applications and payment service providers express intent: "deliver $10M USD value to wallet X on Base by T+0." Below the interface, the orchestration layer reads inventory across primary pools, queries onchain liquidity on Uniswap, Curve and Aave V3 ($11.6B TVL per DeFiLlama), and routes an offchain RFQ to dealer desks where size warrants. The chosen path may be a single-issuer transfer, a cross-issuer pooled-inventory conversion, or a hybrid that uses CCTP V2 for the USDC leg and a Hyperlane bridge for the USDP leg.

Best-execution analytics close the loop. The router publishes the post-trade spread versus a reference rate composed of primary-market par and a weighted secondary-market quote. Institutional buyers want one integration across markets, not twelve KYB processes. Eco is building toward this stable-agnostic layer as a neutral aggregator across primary mint access, onchain liquidity and offchain RFQ, with no principal book on either side of the trade. Routing is a clearing function. The orchestrator does not own inventory risk; the issuers and APs do.

The Fungibility Conformance Standard: a proposed technical specification

A Fungibility Conformance Standard defines the technical contract a stablecoin must satisfy to participate in par-redeemable cross-issuer flows. Conformance covers five dimensions: primary-market access protocol, reserve attestation cadence and format, mint and burn event schema, dispute oracle integration, and best-execution telemetry. Conformance is the input to the orchestration layer's routing decision.

The proposed dimensions and current state of practice across issuers:

Dimension

USDC (Circle)

USDT (Tether)

USDP / PYUSD (Paxos)

RLUSD (Ripple)

Primary-market API

Programmatic via Circle Mint

Bilateral, no public API

Programmatic via Paxos enterprise

Bilateral, growing API surface

Reserve attestation

Monthly third-party

Quarterly attestation

Monthly third-party

Monthly third-party

Native cross-chain transport

CCTP V2 (sub-30s)

Bridge-dependent

Bridge-dependent

Bridge-dependent

Public mint and burn events

Standard ERC-20 with attestation

Standard ERC-20

Standard ERC-20

Standard ERC-20

Circulating supply (Jun 2026)

$75.6B

$187.2B

$2.9B PYUSD; $32M USDP

$1.7B

Supply figures source DeFiLlama and Artemis, June 2026. A conformance standard does not mandate a single API; it mandates an interoperable schema. Issuers retain proprietary control of their primary loops while exposing a common surface for orchestrators to query inventory, request mints, post redemptions, and pull attestation hashes. Without that surface, routing is bespoke and unscalable.

Regulatory alignment: the GENIUS Act, MiCA, and the redemption-at-par mandate

Regulatory frameworks in the United States and European Union now codify redemption at par as a baseline obligation, which is the legal foundation for cross-issuer fungibility. The GENIUS Act advanced through the US Senate in 2025, and the EU Markets in Crypto-Assets Regulation has been in force since 2024. Both frameworks require permissioned stablecoin issuers to redeem in full and on demand against reserves of equivalent fiat or short-dated government paper.

The GENIUS Act establishes a federal framework for payment stablecoin issuers, with reserve composition, attestation and redemption-rights provisions. MiCA Article 49 imposes equivalent par-redemption duties on e-money tokens. The European Central Bank has discussed how these duties create the legal substrate for multi-issuer fungibility: if every conforming issuer must redeem at par, then any two conforming issuers' liabilities are economically equivalent claims on equivalent reserves, differentiated only by operational risk and access friction.

The operational layer still has to exist. Regulatory par redemption gives the right; orchestration gives the path. The CPMI work and IOSCO recommendations both emphasize that par redemption only delivers cross-issuer fungibility when paired with technical infrastructure that lets holders convert without holding accounts at every issuer. The conformance standard is that infrastructure specification.

Implementation checklist for wallets, PSPs, and protocol developers

Wallets, payment service providers and protocol developers integrating multi-issuer fungibility should validate inventory depth, primary-market access protocol, finality clock alignment, dispute oracle subscription, and best-execution reporting before going live. Each item maps to a failure mode observed in production cross-stablecoin flows, and the checklist is the minimum surface for institutional rollout.

For wallets, the user-facing requirement is balance abstraction. Display USD value, not specific issuer balances. Route based on inventory and policy, not on whatever the user happens to hold. For PSPs, the requirement is settlement-time guarantees with deterministic fail-open behavior on de-peg. Offer customers a par price quoted against a transparent reference rate, with spread attributable to bank rails and operational cost.

For protocol developers, the requirement is event-schema conformance. Emit mint, burn, transfer and attestation events on a schema that orchestrators can index without custom adapters. The LayerZero V2 bridge ($7.5B TVL per DeFiLlama, June 2026) and CCTP V2 provide reference patterns for the message structure. Integration with a neutral orchestration layer collapses the twelve-KYB problem into one. That is the institutional outcome that justifies the standard, and it is the composability story that closes the gap between the current $315.3B stablecoin market and a true multi-issuer par market.

Eco's role in the standard

Eco is building toward the neutral orchestration layer that this standard requires. The platform combines primary mint access, onchain liquidity routing across rails like CCTP, Hyperlane and LayerZero, and offchain RFQ to dealer inventory, exposing one integration surface to wallets, payment service providers and tokenization issuers. Eco does not warehouse principal risk; the issuers and authorized participants do. The orchestration function is clearing, not market making.

A neutral aggregator is the only viable home for cross-issuer routing because no single issuer can credibly route to a competitor. Circle does not mint Tether; Paxos does not mint Ripple's RLUSD. The routing decision sits above all of them. By focusing on the orchestration substrate and the conformance schema rather than on token issuance or principal liquidity, Eco builds the layer that the GENIUS Act and MiCA presuppose but do not specify: the technical infrastructure that converts par-redemption rights into par-clearing reality.

Related reading

Methodology

Stablecoin supply figures sourced from DeFiLlama and Artemis as of June 2026. Cross-chain stablecoin volume from Artemis Terminal, Q1 2026 window. Regulatory citations: GENIUS Act (S.1582, 119th Congress) and EU MiCA Regulation 2023/1114. Primary-source reports referenced: BIS CPMI Stablecoins in cross-border payments (October 2025), Federal Reserve Financial Stability Report (April 2024), IOSCO Policy Recommendations for Stablecoin Arrangements. Issuer transparency data from Circle, Tether, Paxos and Ripple disclosure pages. No figure is drawn from secondary aggregators where a primary source exists.

Did this answer your question?