Arc, Plasma, Stable: A Developer’s Stablechain Map
You can deploy a smart contract on Circle’s Arc testnet this afternoon. You cannot ship it to production, because Arc has no mainnet, no confirmed launch date, and no guarantee the chain you’re testing against today looks the same when it finally goes live. Meanwhile, Tether already runs two separate mainnets, Plasma and Stable, and they don’t share a gas model, a token, or a design philosophy. If your roadmap touches both USDC and USDT, you’re not choosing one stablecoin blockchain in 2026. You’re choosing between three, and none of them talk to each other natively.
That’s the part most coverage skips. This piece is for the people who actually have to write the code: which chain is real infrastructure today, which is a very well-funded testnet, and what breaks in your architecture if you assume otherwise.
What’s Actually Live vs. What’s Roadmap
Start here, because it’s the single most common source of confusion in developer forums right now.
| Chain | Status (Aug 2026) | Native Gas Asset | Consensus |
|---|---|---|---|
| Circle Arc | Public testnet only, no mainnet date | USDC | Malachite (permissioned PoA) |
| Tether Plasma | Mainnet live since Sept 2025 | USDT (paymaster-abstracted) | PlasmaBFT + Bitcoin anchor |
| Tether Stable | Mainnet live, native STABLE token | USDT (direct, no abstraction) | EVM-compatible BFT |
Circle announced Arc in August 2025 as an independent Layer-1 built around USDC as native gas, a built-in FX engine for institutional price discovery, and sub-second finality. Testnet went live that October. As of Circle’s February 2026 earnings call, the company had shifted its own language from firm mainnet dates to describing an “exploration phase.” If you see a headline promising an imminent Arc mainnet, check the date against Circle’s own blog before you believe it.
Circle Arc: Built for Institutions, Still in Testnet
Here’s what’s genuinely usable right now: developers can connect to Arc’s testnet via standard RPC endpoints, pull test USDC from the faucet, and deploy contracts using ordinary Foundry or Hardhat workflows, per the Arc developer docs. That’s not vaporware. It’s a working environment you can build against today, at zero production risk because there’s nothing live to break.
What developers should actually plan around:
- Permissioned validators. Arc runs proof-of-authority today, with a stated intention to move toward permissioned proof-of-stake. Circle holds a 25% stake in the initial 10 billion token supply and can operate validator infrastructure directly. That’s a very different trust model than the public chains most Solidity developers are used to.
- Failure mode is a halt, not a fork. BFT-style permissioned consensus tends to stop the chain during a partition or validator failure rather than split it. If your mental model of “chain down” comes from Ethereum, recalibrate.
- Token incentives are real but future-dated. Sixty percent of Arc’s 10 billion token supply is earmarked for ecosystem participants, meaning builders and users, separate from the presale investors. In May 2026, Circle closed a $222 million token presale at a $3 billion fully diluted valuation, led by a16z with participation from BlackRock and Apollo. That’s serious capital behind a chain nobody can use in production yet.
Plasma and Stable Are Not the Same Chain
This is where most explainers get lazy, lumping both under “Tether’s chain” as if Tether built one thing. It built two, and they solve different problems.
Plasma: liquidity-first, subsidized fees
Plasma launched in September 2025 and hit $5.6 billion in TVL within its first week. It pairs a custom PlasmaBFT consensus with full EVM compatibility and a Bitcoin security anchor, and it raised roughly $373 million in a public token sale, seven times its original target. More than 100 DeFi protocols, including Aave, Ethena, and Euler, integrated on day one. Gas is abstracted through a paymaster, which is how Plasma delivers zero-fee USDT transfers. That subsidy is a business decision Tether makes, not a protocol-level guarantee, which matters if you’re designing unit economics around permanently free transfers.
Stable: governance-first, direct gas
Stable is a separate Tether and Bitfinex-orbit chain that launched its EVM-compatible mainnet after a pre-deposit campaign pulling in more than $2 billion from over 24,000 wallets, according to The Block’s mainnet coverage. Instead of abstracting gas, Stable uses USDT directly as the fee asset, no separate token required to transact. It shipped with its own STABLE governance token and an independent Stable Foundation, deliberately separating network security decisions from USDT-denominated payment flows. In May 2026 it added StableEarn, a yield product tied to Treasury and gold-backed real-world assets.
Same issuer ecosystem, two genuinely different architectures. Code written for Plasma’s paymaster model doesn’t port cleanly to Stable’s direct-gas model, even though both chains are EVM-compatible.
The Gas Model Problem Developers Underestimate
Every one of these three chains claims EVM compatibility. None of them handle gas the same way, and gas is where user experience actually lives.
| Chain | Gas Mechanic | What it means for your app |
|---|---|---|
| Arc | USDC native gas + built-in FX engine | Institutional RFQ pricing baked in, but permissioned validator dependency |
| Plasma | Paymaster abstracts fees to zero | Great UX today, dependent on Tether’s continued subsidy |
| Stable | USDT used directly, no abstraction | Simple mental model, but fees are visible to end users |
Is a “zero-fee” chain actually free, or is someone just paying the fee for you upstream? On Plasma, it’s the latter, and that’s worth designing around rather than assuming away.
The Fragmentation Bill You’ll Eventually Pay
A USDC balance on Arc and a USDT balance on Plasman or Stable don’t interoperate natively. Moving value between them requires bridging infrastructure, CCTP for USDC, USDT0’s OFT architecture for USDT, and that bridging layer needs to be a first-class part of your architecture, not a patch you add later.
A Bank for International Settlements working paper makes the structural case bluntly: a stablecoin on one chain isn’t the same asset as the identical token minted on another chain by the same issuer. They can’t be directly exchanged, and every bridge between them introduces delay, cost, and smart-contract risk. Stack Arc, Plasma, Stable, and Stripe’s Tempo on top of each other and you’ve recreated the L2-sprawl problem Ethereum already has, just with different issuer logos attached.
What the People Building This Actually Say
Circle CEO Jeremy Allaire has been explicit about the ambition behind Arc, framing it as more than infrastructure. In a CNBC interview announcing the token presale, he described Circle as
“entering the operating system business”Jeremy Allaire, Co-Founder and CEO, Circle Internet Group, CNBC, May 11, 2026
a16z crypto, the lead investor in that raise, framed the underlying problem as one of infrastructure catching up to demand, noting that stablecoins have become one of the most important tools in global finance while the blockchains carrying them remain optimized for crypto-native users rather than banks and corporations, per Bessemer Venture Partners’ stablecoin research.
Not everyone is convinced the model is neutral infrastructure at all. Critics quoted in industry analysis have described Arc’s design as closer to
“a walled garden… for banks”Odaily analysis, October 2025than a genuinely open public network, pointing to Circle’s validator control and permissioned architecture as evidence.
Tether CEO Paolo Ardoino, an advisor and seed investor in both Plasma and Stable, has also been publicly critical of MiCA’s stablecoin rules, arguing they create systemic banking risks, and Tether hasn’t pursued MiCA authorization for USDT. That’s directly relevant if you’re an EU-based developer weighing production deployment on either Tether chain, since it shapes USDT’s regulatory footing in that market.
Quick Answers
No. As of August 2026, Arc remains in public testnet, which launched in October 2025. Circle has confirmed a 2026 mainnet target but hasn’t set a firm date, describing the project as still in an “exploration phase” as of its February 2026 earnings call.
Both use USDT as gas and sit in the Tether and Bitfinex orbit, but they work differently. Plasma abstracts gas through a subsidized paymaster for zero-fee transfers, while Stable uses USDT directly as the gas asset with its own STABLE governance token layered on top.
Yes, on testnet. Developers can connect via RPC endpoints, use Foundry or Hardhat, pull testnet USDC from Circle’s faucet, and deploy EVM smart contracts right now. Production deployment isn’t possible until mainnet ships, and no date is confirmed yet.
Both companies currently settle their stablecoins on third-party chains like Ethereum and Tron, capturing none of the transaction fee revenue those networks generate. Owning the settlement layer lets them keep that fee revenue instead of handing it to someone else’s network.
Yes. USDC balances on Arc and USDT balances on Plasma or Stable don’t interoperate natively. Moving value between them needs bridges like CCTP, and each bridge adds cost, latency, and smart-contract risk that has to be designed around explicitly.
Where This Goes Next
Here’s what you didn’t know walking in: “building on a stablecoin chain” isn’t one decision, it’s at least three, and they don’t converge anytime soon. Arc buys you institutional FX tooling and a serious token incentive, in exchange for building on infrastructure that doesn’t exist in production yet. Plasma buys you the deepest live liquidity and free transfers, subsidized by a company that can change that subsidy on its own schedule. Stable buys you a simpler gas model and a dedicated governance layer, at the cost of user-visible fees.
Watch three things over the next six to eighteen months: whether Circle actually ships an Arc mainnet date rather than another “exploration phase” update, whether Plasma’s zero-fee economics survive a real stablecoin supply contraction, and whether USDT0-style bridging standards mature enough that cross-chain USDT stops being a developer headache. None of these chains exist in a vacuum, and the fragmentation problem they’re each quietly creating is going to need its own solution before any of them scale the way their backers are promising.
Want the next update on this before it hits the wire? Subscribe to The Neural Loop for the developer-angle breakdown every time one of these chains ships something real.
