Stablecoin Issuance on New Chains: Deploying, Bridging, and Reporting the Right Way

Stablecoin teams can now go live on more chains than ever—but the technical, security, and regulatory bar in 2025 is much higher. This guide condenses the newest patterns we use at 7Block Labs to launch, bridge, and report stablecoins correctly across EVM L2s, Solana, Cosmos, Sui/Aptos, and emerging L1s.

---

Why 2025 is different: regulation, rails, and risk

• In the U.S., the GENIUS Act (Public Law 119-27) became law on July 18, 2025. It requires permitted payment-stablecoin issuers to hold 1:1 reserves in tightly defined instruments, publish monthly reserve composition, obtain a monthly attestation by a registered public accounting firm, and be able to seize/freeze/burn under lawful order—among other constraints. Plan your product, legal entity, reserve stack, and smart-contract controls around those obligations from day one. (congress.gov)
• In the EU, MiCA’s e-money token (EMT) and asset‑referenced token (ART) regimes are fully rolling out. Issuers must meet liquidity/composition RTS and, for non‑EU‑currency EMTs/ARTs “used as means of exchange,” monitor the cap of 1,000,000 transactions or €200,000,000 per day on a quarterly‑average basis and file a reduction plan if exceeded. Build reporting pipelines now. (eba.europa.eu)
• Cross‑chain execution has matured. Circle’s CCTP burn‑and‑mint is now on more domains (V1 legacy and V2) and replaces lock‑and‑mint for USDC; Chainlink CCIP is GA with rate limits and anomaly‑response; Wormhole’s Native Token Transfers (NTT) and LayerZero v2 OFT let you run one canonical supply across chains with configurable security. These are the rails your cross‑chain USDC/EMT strategy should prefer. (circle.com)
• Bridge risk remains real. 2024–2025 brought more bridge incidents (e.g., Orbit Bridge, $80M+), and research catalogs multi‑billion historical losses since 2021. If you must bridge, enforce strict rate‑limits, circuit breakers, and “global accountant” supply checks. (coindesk.com)

---

Choose the right issuance model for each chain

There are four workable patterns today. Pick deliberately; mixing models without a supply‑of‑record plan causes liquidity fragmentation and compliance headaches.

1. Native issuance on each chain

• What it is: Independent token contracts per chain, each minted/burned by the issuer.
• When to use:
  • Chains with robust direct mint/redeem demand (e.g., Base, OP Mainnet, Arbitrum, Solana).
  • Ecosystems where you can use a burn‑and‑mint mobility layer (CCTP, OFT/NTT) to preserve singleness of money.
• Pros: Best UX and redemption guarantees; easiest for CEX/fiat on‑ramps.
• Cons: More contracts/ops; must coordinate supply across chains.

1. Burn‑and‑mint interoperability as the mobility layer

• What it is: Burn on source, attest, mint on destination—no wrapped IOUs.
• Rails to consider:
  • USDC: Circle’s CCTP (V1 legacy and newer V2 variants). Verify domain support for your target chains. (developers.circle.com)
  • Protocol‑agnostic: Wormhole NTT (burn‑and‑mint mode) or LayerZero v2 OFT (vanilla OFT burns/mints). Both support per‑chain rate limits and standardized message flows. (wormhole.com)
  • Institutional requirements (rate limits, pause, anomaly response): Chainlink CCIP includes token‑bucket rate‑limiting and a dedicated risk‑management network. (docs.chain.link)
• Pros: No wrapped liquidity to babysit; unified circulating supply.
• Cons: You depend on the availability of that mobility rail on every chain in your scope.

1. Hub‑and‑spoke for legacy tokens or phased migrations

• What it is: Lock on a “hub” chain and mint on “spokes,” with a global cap; later migrate to burn‑and‑mint everywhere.
• Rails: Wormhole NTT (hub‑and‑spoke mode) gives you a global accountant and per‑chain limits while you unwind legacy wrappers (e.g., historical “USDC.e” migrations on L2s). (wormhole.com)

1. Cosmos and Polkadot specifics

• Cosmos: Issue natively on Noble so USDC circulates across IBC without wrapping; this is the canonical path for Cosmos USDC and now holds hundreds of millions in circulation. (usdc.com)
• Polkadot: Issue on Asset Hub and distribute via XCM to parachains; many teams now standardize on the Asset Hub native USDC. (theblock.co)

Practical recommendation: Treat “native + burn‑and‑mint mobility” as the default. Use hub‑and‑spoke only as a stepping‑stone to eliminate wrapped variants over time.

---

Chain selection: what “native” means on today’s networks

• EVM L2s (Base, OP Mainnet, Arbitrum, Polygon PoS): Native USDC exists and is mobile via CCTP V1 (and expanding V2). Confirm whether your chain is on CCTP V1 (Standard) or V2 and whether “fast transfer” is available. Design for the V1 sunset timeline (CCTP V1 is set for deprecation beginning July 31, 2026) and map your migration path. (developers.circle.com)
• Solana: Native USDC and CCTP V1 are live; CCIP support is expanding across ecosystems. Budget for priority fees and implement idempotent instructions for large‑scale mints/burns. (developers.circle.com)
• Sui/Aptos (Move): Native USDC on Sui launched in Oct 2024; CCTP support is active for Sui. For omnichain tokens you can also deploy LayerZero v2 OFT on Sui with shared‑decimals handling. (developers.circle.com)
• Cosmos: Use Noble (IBC) for canonical USDC across appchains; exchanges now support Noble routes directly. (usdc.com)
• Polkadot: Use Asset Hub for canonical USDC; return flows to Asset Hub before redemption to keep circle‑mint operations simple. (theblock.co)
• TON: USDT went live in 2024 and usage exploded thanks to Telegram mini‑apps; if you’re issuing a non‑USDC stable there, plan for scale, fee abstraction, and sanctions geo‑blocks in wallets. (theblock.co)

---

Token contract design that survives audits and audits-by-regulators

Concrete choices we standardize:

• Decimals and metadata
  • Most fiat‑backed stables use 6 decimals; ensure your cross‑chain math actually normalizes amounts (e.g., USDC 6 vs on‑chain 18). We’ve seen production bugs where TVL math or redemption quotes silently mis‑scale. Add per‑chain decimal registries and invariant tests. (codehawks.cyfrin.io)
• Authorization flows
  • Support at least one gasless pattern: EIP‑2612 Permit or EIP‑3009 (transferWithAuthorization). Circle documents both patterns for USDC integrators; use them to reduce retail friction and lower customer support load. (docs.openzeppelin.com)
• Administrative controls and role separation
  • Roles: Minter, Pauser, Blacklister/Blocklister (to comply with lawful orders), Upgrader (if UUPS/proxy), and Operator for cross‑chain managers. Put each under separate multi‑sig with HSM/MPC signers and a timelock on upgrades.
  • Emergency pause: Chain‑specific pausable hooks that integrate with CCIP/NTT/OFT rate‑limits for cross‑chain throttling.
• Upgradeability
  • If you must use proxies, align with the latest OpenZeppelin guidance (EIP‑712 domain caveats on upgrades) and run a canary environment to catch domain‑separator changes that could brick Permit signatures after upgrades. (docs.openzeppelin.com)
• Observability
  • Emit standardized events for mint/burn/blacklist/pause and cross‑chain transfers. Ship a public subgraph or indexer schema and a transparent, documented supply‑reconciliation report per chain.

---

Bridging the right way (and avoiding the traps)

• Avoid lock‑and‑mint for fiat‑backed stables whenever possible. It fragments liquidity and adds smart‑contract custody risk. Prefer burn‑and‑mint like CCTP V1/V2 for USDC, or “native multichain” frameworks (Wormhole NTT burn‑and‑mint; LayerZero v2 OFT). Configure:
  • Per‑direction rate limits (daily notional and token units).
  • Global accountant to enforce “sum(minted) − sum(burned) == 0” across domains.
  • M‑of‑N attestation thresholds if your framework supports additional verifiers. (circle.com)
• If you must run a legacy wrapped asset, publish a deprecation and migration plan on day one. Incentivize DEXs and apps to switch to native, as Circle and ecosystems did during “USDC.e” migrations. (cointelegraph.com)
• Implement circuit breakers:
  • Chainlink CCIP libraries provide token‑bucket rate‑limiting; combine with risk‑management network triggers to pause anomalous flows during cross‑chain incidents. (docs.chain.link)
  • For NTT/OFT, add governance‑controlled pause on the transceiver/endpoint and pre‑wire emergency governance paths.

Security context to share with leadership: 2024’s Orbit Bridge exploit crossed $80M and academic surveys tally multi‑billion losses in bridge incidents since 2021; your board will expect documented rate‑limits, invariants, and drills. (coindesk.com)

---

Compliance and reporting that stands up in 2025 audits

• U.S. GENIUS Act playbook (effective timeline “earlier of 18 months from enactment or 120 days after final rules”):
  • Reserves: 1:1 in cash, Fed balances, insured deposits, short‑dated Treasuries, and specified repos; no rehypothecation (limited exceptions). Publish monthly reserve composition; monthly third‑party examination; CEO/CFO certification to the primary regulator. Build these disclosures into your investor relations site with machine‑readable JSON for DeFi integrations. (congress.gov)
  • Orders: Maintain technical capability to seize/freeze/burn under lawful orders. Ensure operational runbooks exist for each supported chain. (congress.gov)
• EU MiCA (ART/EMT)
  • Liquidity/reserve composition RTS and custodial diversification apply. For non‑EU currency EMTs/ARTs used “as means of exchange,” track the 1,000,000 tx / €200,000,000 daily thresholds on a quarterly average, and submit a reduction plan within 40 working days if breached. Instrument your off‑ and on‑chain telemetry accordingly; exclude the carved‑out categories ESAs identified (e.g., trading, certain collateral uses). (eba.europa.eu)
• State frameworks (U.S.)
  • California DFAL licensing (operative July 1, 2026) and stablecoin requirements will apply to many U.S. programs even with federal licensure; plan for dual reporting and exam coordination. NYDFS guidance (baseline criteria since 2022) remains a practical benchmark for reserve composition and daily redeemability SLAs. (dfpi.ca.gov)
• Accounting for corporate holders (your customers)
  • FASB ASU 2023‑08 (effective for fiscal years beginning after Dec 15, 2024) moves in‑scope crypto assets to fair‑value. Provide custodial statements, on‑chain proofs, and pricing references to help enterprise holders close books cleanly. (kpmg.com)
• Chain risk governance
  • Factor chain exits/entries into policy. Circle’s 2024 exit from Tron is a good case study for chain risk thresholds, wind‑down comms, and redemption continuity. Build similar clauses into your disclosures. (reuters.com)

---

Real‑time transparency that goes beyond PDFs

• Monthly attestations remain table stakes (Circle publishes monthly reserve attestations). Provide downloadable machine‑readable reserve composition and chain‑by‑chain circulation, with a consistent schema. (circle.com)
• On‑chain Proof of Reserve (PoR) as a control, not just marketing:
  • Chainlink PoR lets you put reserve data on‑chain and wire it into mint logic (“Secure Mint”) so mints fail automatically when reserves lag. For bridged or cross‑chain contexts, PoR helps prevent over‑issuance. Publish your PoR feed details and how they gate minting. (chain.link)
• Compliance automation
  • Connect your KYT to operational controls. KYT vendors provide APIs to screen flows and counterparties; wire “deny/pause” hooks to cross‑chain endpoints to block mints/redemptions dynamically if risk crosses policy thresholds. (kytdoc.kyt-dev.e.chainalysis.com)

---

A deployment blueprint (EVM L2 + Solana + Sui)

Below is a condensed plan we’ve executed with minimal variance across programs.

1. Entity, reserves, and controls

• Stand up an issuing entity aligned to your target jurisdictions (GENIUS Act permit or state‑qualified issuer; EU EMT/ART authorization if EU‑facing).
• Finalize reserve policy: cash + insured deposits + ≤93‑day Treasuries/repos; custodial diversification and segregation; monthly attestation vendor. Publish redemption SLAs, fees, and lawful‑order policy. (congress.gov)

1. Contracts per chain

• ERC‑20 (6 decimals) with Permit and roles; Solana SPL with freeze authority; Sui Move package with OFT wiring if you need omnichain mobility.
• Admin hygiene: separate multi‑sigs for minter/pauser/blacklister/upgrader; HSM/MPC controls; timelocked upgrades; per‑chain emergency pause.

1. Cross‑chain mobility

• For USDC‑like deployments: integrate CCTP where available (Arbitrum, Avalanche, Base, Ethereum, OP Mainnet, Polygon PoS, Solana, Sui, etc.). For chains outside CCTP, add LayerZero v2 OFT or Wormhole NTT in burn‑and‑mint mode with:
  • Per‑direction and per‑asset rate limits.
  • Global accountant invariant checks.
  • Extra verifiers if supported by your framework. (developers.circle.com)

1. Observability and reporting

• Indexer that reconciles per‑chain net mints/burns vs. PoR/attestation numbers daily.
• MiCA “means‑of‑exchange” counter: count only in‑scope tx categories and single currency area; store quarterly rolling averages. Alert at 80% cap. (eba.europa.eu)

1. Compliance plumbing

• KYT pre‑ and post‑transaction checks on mints/redemptions and large transfers; auto‑pause via CCIP/NTT/OFT if an alert fires above threshold. Keep auditable logs. (chainalysis.com)

1. Exchange and wallet integrations

• Provide native token addresses by chain, deprecate wrapped tickers with migration instructions, and supply a canonical chainlist JSON. Coordinate with market makers to re‑seed pools on native tickers first.

---

Example: A three‑month, three‑chain rollout

• Week 0–4: Entity & reserves
  • Secure licensure path (GENIUS Act permit or state‑qualified), KYC/KYT stack, reserve banking and MMF mandates. Draft redemption policy and disclosures. (congress.gov)
• Week 3–6: Contracts & audits
  • Ship ERC‑20 with Permit, SPL, and Sui Move modules; complete security review; stage on testnets with mock PoR gate.
• Week 6–9: Cross‑chain mobility
  • Wire CCTP (where applicable) and LayerZero OFT or Wormhole NTT for the remaining chains; configure per‑direction limits (e.g., $25M/24h initially) and emergency pause runbooks. (developers.circle.com)
• Week 8–10: Reporting stack
  • Deploy subgraphs/indexers, PoR feeds (if used), monthly attestation pipeline, MiCA counters, and JSON reserve/circulation endpoints. (chain.link)
• Week 10–12: Migrate liquidity
  • Coordinate with major DEXs/CEXs to list the native contract addresses; publish canonical tickers and deprecate any legacy bridged variants (USDC.e‑style) via incentives. (cointelegraph.com)

---

Emerging best practices we recommend adopting now

• Default to burn‑and‑mint mobility for singleness of money. Treat wrapped variants as transitional only. (circle.com)
• Bake in rate‑limits and anomaly‑driven pauses across your bridging stack (CCIP/NTT/OFT). Practice incident drills with your operations team. (docs.chain.link)
• Put transparency on‑chain where it matters (PoR “Secure Mint” gating mints; machine‑readable circulation per chain). (chain.link)
• Instrument MiCA monitoring correctly (exclude trading/collateralized transactions as clarified by authorities; count within single currency areas). Automate the 40‑working‑day plan workflow. (eba.europa.eu)
• Publish a “chain eligibility” policy and be willing to off‑board chains that no longer meet your risk bar—just as we saw with Tron/USDC. (reuters.com)
• Help enterprise holders account properly under FASB ASU 2023‑08 with fair‑value data, custody attestations, and reconciliation exports. (kpmg.com)

---

What good looks like in production

• Technical
  • Native deployment on target chains; mobility via CCTP/OFT/NTT; no liquidity trapped in wrapped IOUs.
  • Explicit decimals handling; audited math for cross‑decimals conversions; idempotent cross‑chain handlers.
• Security
  • Rate‑limited endpoints with pause hooks; invariant checks on total supply; automated mint‑gating via PoR.
  • Per‑role multi‑sig with HSM/MPC; emergency upgrade runbooks and time‑boxed freezes.
• Compliance and reporting
  • Monthly reserve composition with third‑party examination; machine‑readable reserve and circulation feeds; MiCA counters; KYT‑driven operational controls with audit trails.
  • Clear, tested lawful‑order workflows to seize/freeze/burn on each chain.

Do the above, and your stablecoin can expand to new chains while staying interoperable, safe, and regulator‑ready.

---

Further reading and references

• Circle Cross‑Chain Transfer Protocol (CCTP) supported blockchains and V1/V2 info. (developers.circle.com)
• Wormhole Native Token Transfers (NTT) overview and architecture. (wormhole.com)
• LayerZero v2 OFT quickstart and endpoint model. (docs.layerzero.network)
• Chainlink CCIP GA and rate‑limiting; risk‑management network. (prnewswire.com)
• MiCA RTS/caps and supervisory materials. (eba.europa.eu)
• U.S. GENIUS Act text and analyses. (congress.gov)
• Accounting: FASB ASU 2023‑08 effective dates. (kpmg.com)
• Bridge risk case study: Orbit Bridge. (coindesk.com)
• USDC on Noble (Cosmos) and Polkadot Asset Hub guidance. (usdc.com)
• Circle transparency page (monthly attestation). (circle.com)

---

7Block Labs helps issuers design, ship, and operate compliant, cross‑chain stablecoins with production‑grade observability and controls. If you’d like a readiness assessment or an implementation sprint for CCTP/NTT/OFT + PoR, we’re happy to help.