Issuer-native routing means moving a stablecoin across chains through infrastructure its issuer runs or endorses, such as Circle's CCTP for USDC or the USDT0 Network for Tether-issued assets. A neutral router, such as Eco, sits above those rails and moves value across issuers, chains and stablecoins through one API. For a treasury that holds a single stablecoin and moves it between a few chains, the issuer's rail is usually enough. For a treasury that holds more than one stablecoin, pays counterparties who want a different one, or needs one integration across many chains, a neutral router is the better fit.
This page compares the two models on what changes in practice: which assets they cover, how settlement works, speed, cost, and who carries the risk. Background: the stablecoin infrastructure stack and how issuers and routers divide the work.
What is the difference between stablecoin issuers and stablecoin rails?
An issuer creates and redeems the token and holds the reserves behind it. A rail moves the token between places: between chains, between wallets, or between one stablecoin and another. The two jobs used to be bundled because the issuer was the only party that could mint on a new chain. They are now separating, because issuers publish their own transfer tools and independent routers build on top of them.
Issuance itself stays narrow. The Federal Reserve describes stablecoin primary markets as restricted to a set of approved customers that tend to be companies rather than retail traders, and reports a minimum of $100,000 of USDT per mint onchain, per a 2024 FEDS Note on primary and secondary markets for stablecoins. Moving tokens is a separate service that anyone with the token can use.
How does issuer-native routing work?
Issuer-native rails move one issuer's token by destroying it on the source chain and creating it on the destination chain, so no pool of wrapped tokens sits in between.
Circle CCTP. Circle describes the Cross-Chain Transfer Protocol as a permissionless onchain utility that natively transfers USDC across blockchains using burn-and-mint, without traditional bridge liquidity pools, per Circle's CCTP documentation. Circle lists Fast Transfer at roughly 8 to 20 seconds and Standard Transfer at 15 to 19 minutes on Ethereum and L2s, with the fee deducted from the transferred amount. CCTP hooks can trigger actions on the destination chain after the USDC arrives.
Circle Gateway. Gateway gives a unified USDC balance across chains. Users deposit USDC into non-custodial Gateway Wallet contracts on a supported source chain, then mint USDC on a destination chain in under 500 milliseconds once the balance is established, with a 7-day trustless withdrawal option, per Circle's Gateway documentation.
USDT0. The USDT0 Network offers omnichain deployments of Tether-issued assets on LayerZero's Omnichain Fungible Token (OFT) standard. USDT is locked in an OFT Adapter contract on Ethereum, decentralized verifier networks verify the message, and USDT0 is minted on the destination chain, per the USDT0 technical documentation.
How does a neutral router work?
A neutral router does not issue a token. It quotes a route from what the user holds to what the recipient needs, then has a third party deliver the output on the destination chain. The router can use any issuer's rail underneath, or none.
Eco is a neutral router for stablecoins. With the Routes API and Routes CLI, a developer requests a quote, funds it on the source chain and tracks it to delivery. A solver supplies the destination assets and executes the route, and the source-chain contract releases the solver's reward once a prover confirms fulfillment, per Eco's Routes documentation. If fulfillment does not complete, funds can become refundable under the deadline and proof conditions set at quote time. The same request can include a swap, so USDT on one chain can arrive as USDC on another in one flow. Supported chains and tokens come from Eco's live endpoints rather than a fixed list.
Neutral and issuer-native are not opposites. Eco's documentation includes deposit-address flows that land funds in a Circle Gateway balance, per Eco's developer docs. A router can feed an issuer's rail instead of competing with it.
Issuer-native vs neutral routers compared
Dimension | Issuer-native rail (CCTP, Gateway, USDT0) | Neutral router (Eco) |
Assets covered | One issuer's tokens (USDC and EURC for Circle; Tether-issued assets for USDT0) | Multiple stablecoins from different issuers |
Cross-stablecoin swaps | Not the rail's job; a separate swap is needed | Can be part of the same quoted route |
Settlement model | Burn-and-mint or lock-and-mint by the issuer's contracts | Solver delivers on destination, then is repaid on source after proof |
Speed | CCTP Fast Transfer about 8 to 20 seconds, per Circle CCTP docs; Gateway under 500 ms after deposit, per Circle Gateway docs | Depends on route and solver; quoted per request |
Integration | One integration per issuer | One API across issuers and chains |
Main dependency | The issuer's contracts and attestation service | Solver liquidity and the router's contracts and provers |
Should I use my stablecoin issuer to route trades?
Use the issuer's rail when all three of these are true: the treasury holds one stablecoin, the counterparty accepts that same stablecoin, and the issuer supports both chains. Moving USDC between two chains that CCTP supports, to a vendor paid in USDC, is a CCTP job. A router adds a layer you do not need.
Use a neutral router when any of these is true:
The treasury holds USDC and USDT and wants to rebalance between them without a separate exchange step.
A counterparty wants a different stablecoin than the one you hold.
You pay out across chains that no single issuer rail covers.
Your team wants one integration and one status API instead of one per issuer.
Many treasuries end up using both. The issuer rail handles same-token moves on routes it supports, and the router handles the rest and can deliver into issuer products such as a Gateway balance.
Why are stablecoin rails being unbundled from issuers?
Three things pulled them apart. Issuers made transfer permissionless: CCTP is open to anyone moving USDC, so routing is no longer something only the issuer does on request. Tokens multiplied across chains, and each issuer only covers its own token, so a business holding two stablecoins needs something that spans both. And primary-market access stays restricted to approved, mostly corporate customers, per the Federal Reserve note above, so most users move stablecoins through rails and secondary venues rather than through the issuer directly.
For a deeper look at who operates each layer, see the 5-layer stablecoin stack.
Stablecoin orchestration vs issuance: who wins long-term?
They do different jobs, so one does not have to replace the other. Issuance scales with how much of a token exists. Routing scales with how many chains, stablecoins and counterparties a business has to connect, so the more fragmented supply gets, the more routing work there is. A treasury does not need to pick a winner. It needs to know which layer each provider sits in so it does not pay a router for a same-token move the issuer does natively, or build five issuer integrations where one router would do.
FAQ
Is CCTP a bridge?
Circle describes CCTP as burn-and-mint transfer without traditional bridge liquidity pools. USDC is destroyed on the source chain and created on the destination chain by Circle's contracts.
Can a neutral router move USDT to USDC across chains in one step?
Eco's Routes documentation says a quote can include a source swap, a destination swap or several intents, so a cross-stablecoin, cross-chain move can be quoted as one route. Check the live token endpoints for the specific pair.
Does using a router mean giving up the issuer's guarantees?
No. The token you receive is still issued and redeemable by its issuer. What changes is who delivers it on the destination chain and which contracts you depend on during the transfer.