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

Stablecoin teams have more options than ever to launch on different chains, but let’s be real: by 2025, the standards for technical, security, and regulatory compliance have shot up. This guide breaks down the latest strategies we’re using at 7Block Labs to effectively launch, bridge, and report stablecoins across EVM L2s, Solana, Cosmos, Sui/Aptos, and the new L1s that are popping up.

---

Why 2025 is different: regulation, rails, and risk

• In the U.S., the GENIUS Act (Public Law 119-27) officially became law on July 18, 2025. This law has some specific requirements for payment-stablecoin issuers: they need to keep 1:1 reserves in well-defined instruments, publish a monthly breakdown of those reserves, get a monthly attestation from a registered public accounting firm, and be ready to seize, freeze, or burn under lawful orders--along with a few other rules. So, when you’re planning your product, legal entity, reserve stack, and smart-contract controls, make sure you account for these obligations right from the start. (congress.gov)
• Over in the EU, the MiCA regulations for e-money tokens (EMTs) and asset-referenced tokens (ARTs) are now in full swing. Issuers need to comply with liquidity and composition RTS, and for those non-EU currency EMTs/ARTs that are “used as means of exchange,” they have to keep an eye on a cap of either 1,000,000 transactions or €200,000,000 per day on a quarterly average, filing a reduction plan if they go over. You might want to start building your reporting pipelines now. (eba.europa.eu)
• Cross-chain execution has really come a long way. Circle’s CCTP burn-and-mint is showing up on more domains (both V1 legacy and V2) and is stepping in to replace the lock-and-mint process for USDC. Chainlink CCIP is now generally available with rate limits and anomaly-response features, while Wormhole’s Native Token Transfers (NTT) and LayerZero v2 OFT allow you to maintain one canonical supply across different chains with customizable security. These systems are definitely the ones you should be looking at for your cross-chain USDC/EMT strategy. (circle.com)
• But keep in mind that bridge risk is still a significant concern. From 2024 to 2025, there were more bridge incidents (like the Orbit Bridge losing over $80M), and research shows multi-billion dollar losses since 2021. If you absolutely have to bridge, make sure to implement strict rate limits, circuit breakers, and “global accountant” supply checks to protect your assets. (coindesk.com)

---

Choose the right issuance model for each chain

There are four solid patterns to choose from today. Make your selection carefully; mixing models without a supply-of-record plan can lead to liquidity fragmentation and compliance issues.

1) Native Issuance on Each Chain

• What it is: We're talking about having separate token contracts for each chain, where every token is minted or burned by the issuer.
• When to use:
  • For chains that see a strong demand for direct minting and redeeming, like Base, OP Mainnet, Arbitrum, and Solana.
  • In ecosystems where you can leverage a burn-and-mint mobility layer (think CCTP or OFT/NTT) to keep the money flow streamlined.
• Pros: You get the best user experience and solid redemption guarantees, plus it's the simplest route for centralized exchanges and fiat on-ramps.
• Cons: On the flip side, you have to deal with a bunch of contracts and operations, and you’ll need to coordinate supply across different chains.

2) Burn-and-mint interoperability as the mobility layer

What it is:

The idea is pretty straightforward--burn the tokens on the source chain, attest to that action, and then mint the same tokens on the destination chain. No need for those wrapped IOUs here!

Rails to consider:

• USDC: Check out Circle’s CCTP, which comes in both the legacy V1 and the newer V2 options. Just make sure to verify domain support for the chains you're targeting. (developers.circle.com)
• Protocol-agnostic: You’ve got options like Wormhole NTT in burn-and-mint mode or LayerZero’s v2 OFT. Both of these allow for per-chain rate limits and have standardized message flows. (wormhole.com)
• Institutional requirements: If you have specific needs like rate limits, pause capabilities, or anomaly responses, Chainlink’s CCIP has you covered. It includes token-bucket rate limiting and a dedicated risk-management network. (docs.chain.link)

Pros:

You won’t have to worry about managing wrapped liquidity; it keeps everything streamlined with a unified circulating supply.

Cons:

The catch? You’ll need to rely on the availability of that mobility rail across all the chains you're looking at.

3) Hub-and-spoke for Legacy Tokens or Phased Migrations

• What it is: Basically, you lock up your tokens on a “hub” chain and then mint them on different “spokes,” all while keeping a global cap in place. Eventually, you’ll migrate to a system where you burn and mint tokens across the board.
• Rails: The Wormhole NTT (hub-and-spoke mode) acts as your global accountant and helps you set limits for each chain as you peel away those old legacy wrappers (think about the earlier “USDC.e” migrations on L2s). You can find out more here.

4) Cosmos and Polkadot specifics

• Cosmos: You can issue USDC directly on Noble, which allows it to flow through IBC without needing to wrap it. This is the go-to method for Cosmos USDC, and it's already circulating in the hundreds of millions. Check it out here: (usdc.com)
• Polkadot: For Polkadot, the USDC is issued on the Asset Hub and then distributed to parachains via XCM. Lots of teams are now using the native USDC from the Asset Hub as a standard. For more info, click here: (theblock.co)

Practical Recommendation

Consider making “native + burn-and-mint mobility” your go-to strategy. Use the hub-and-spoke model just as a temporary measure to phase out wrapped variants in the long run.

---

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

• EVM L2s (Base, OP Mainnet, Arbitrum, Polygon PoS): You've got native USDC up and running, and it's pretty mobile thanks to CCTP V1 (with plans for V2 coming soon). Double-check if your chain is using CCTP V1 (the standard) or V2, and see if “fast transfer” is in the mix. Remember, CCTP V1 is slated to start winding down on July 31, 2026, so keep that timeline in mind as you map out your migration strategy. (developers.circle.com)
• Solana: Native USDC is live and kicking, plus CCTP V1 is good to go; CCIP support is also on the rise across various ecosystems. Make sure to budget for priority fees and set up idempotent instructions, especially if you’re dealing with large-scale mints or burns. (developers.circle.com)
• Sui/Aptos (Move): Native USDC on Sui launched in October 2024, and CCTP support is active for it. If you're looking at omnichain tokens, you can deploy LayerZero v2 OFT on Sui, which handles shared decimals quite nicely. (developers.circle.com)
• Cosmos: For canonical USDC, just use Noble (IBC) across the appchains; it's sweet that exchanges now support Noble routes directly. (usdc.com)
• Polkadot: Go for the Asset Hub to manage your canonical USDC; make sure to funnel return flows back to Asset Hub before redemption so your circle-mint operations stay smooth and simple. (theblock.co)
• TON: USDT launched in 2024, and its usage took off, largely thanks to Telegram mini-apps. If you're planning to issue a non-USDC stablecoin there, keep scaling, fee abstraction, and sanctions geo-blocks in wallets on your radar. (theblock.co)

---

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

Concrete Choices We Standardize:

• Color palette: We stick to a specific set of colors to keep our branding consistent.
• Font styles: Our go-to fonts are chosen for clarity and style, making sure we look professional across all our materials.
• Logo usage: There are specific guidelines on how our logo should be displayed to maintain its integrity.
• Imagery: We use a defined style for images that reflect our brand's personality.
• Tone of voice: Our communications have a casual, approachable tone to connect better with our audience.

By standardizing these choices, we ensure that everything we put out into the world feels cohesive and true to our brand.

• Decimals and Metadata
  • Most fiat-backed stablecoins stick to 6 decimal places, so it's crucial to make sure your cross-chain calculations are on point. For example, USDC uses 6 decimals, but when it's on-chain, it goes up to 18. We’ve seen some hiccups in production where things like Total Value Locked (TVL) or redemption quotes got messed up due to these discrepancies. It’s a good idea to add per-chain decimal registries and set up invariant tests. Check this out: (codehawks.cyfrin.io).
• Authorization Flows
  • Make sure to support at least one gasless pattern. You can choose from EIP-2612 Permit or EIP-3009 (transferWithAuthorization). Circle provides documentation for both of these patterns specifically for USDC integrators, and using them can really help reduce friction for retail customers and ease the support load. Get the details here: (docs.openzeppelin.com).
• Administrative Controls and Role Separation
  • Think about your roles: you’ll need a Minter, a Pauser, a Blacklister/Blocklister (to handle lawful orders), an Upgrader (if you’re using UUPS/proxy), and an Operator for cross-chain managers. It’s smart to put each role under a separate multi-signature wallet with HSM/MPC signers. Don’t forget to implement a timelock on upgrades.
  • For emergency pauses, set up chain-specific pausable hooks that integrate with CCIP/NTT/OFT rate limits for cross-chain throttling.
• Upgradeability
  • If proxies are a must-have, make sure you're aligned with the latest guidance from OpenZeppelin. Pay attention to EIP-712 domain caveats during upgrades, and run a canary environment to catch any changes in domain separators that could potentially mess up Permit signatures after you upgrade. Check it out here: (docs.openzeppelin.com).
• Observability
  • It’s important to emit standardized events for minting, burning, blacklisting, pausing, and cross-chain transfers. Also, consider shipping a public subgraph or indexer schema along with a clear, documented supply-reconciliation report for each chain.

---

Bridging the right way (and avoiding the traps)

• Try to steer clear of using lock-and-mint for fiat-backed stablecoins whenever you can. It tends to break up liquidity and introduces some risks with smart-contract custody. Instead, go for burn-and-mint options, like CCTP V1/V2 for USDC, or check out these "native multichain" frameworks (Wormhole NTT burn-and-mint; LayerZero v2 OFT). Here’s a quick setup guide:
  • Set up per-direction rate limits (think daily notional and token units).
  • Use a global accountant to ensure that “sum(minted) − sum(burned) == 0” across different domains.
  • If your framework allows, set M-of-N attestation thresholds for extra verification. (circle.com)
• If you absolutely have to use a legacy wrapped asset, make sure to announce a deprecation and migration plan right from the get-go. Encourage DEXs and applications to transition to native assets, just like Circle and its ecosystems did during the “USDC.e” migrations. (cointelegraph.com)
• Don’t forget to implement circuit breakers:
  • The Chainlink CCIP libraries offer token-bucket rate-limiting--pair those with risk-management network triggers to pause any weird flows during incidents across chains. (docs.chain.link)
  • For NTT/OFT, it’s a good idea to add a governance-controlled pause on the transceiver/endpoint and have emergency governance routes ready to go.

Security Context for Leadership

Hey team, just a heads up: the recent Orbit Bridge exploit from 2024 has hit over $80 million. Plus, academic surveys are pointing out that bridge incidents have racked up losses in the billions since 2021. With numbers like these, you can bet your board will be looking for documented rate-limits, invariants, and drills to keep everything secure. Check out the full story here: (coindesk.com).

---

Compliance and reporting that stands up in 2025 audits

• U.S. GENIUS Act Playbook (Timing: “earlier of 18 months from enactment or 120 days after final rules”):
  • Reserves: Make sure you're keeping a 1:1 reserve in cash, Fed balances, insured deposits, short-dated Treasuries, and certain repos--no rehypothecation unless there are very limited exceptions. You’ll need to publish your reserve composition every month. Plus, expect a monthly third-party examination and get your CEO/CFO to certify everything to the primary regulator. It’s a good idea to add these disclosures to your investor relations site with machine-readable JSON for easy DeFi integration. (congress.gov)
  • Orders: Keep your tech ready to seize, freeze, or burn assets under lawful orders. You'll want operational runbooks for each chain you support. (congress.gov)
• EU MiCA (ART/EMT)
  • The liquidity and reserve composition RTS along with custodial diversification are in play. For non-EU currency EMTs/ARTs used “as means of exchange,” you need to keep track of that 1,000,000 transactions / €200,000,000 daily threshold on a quarterly basis. If you go over, you’ve got 40 working days to submit a reduction plan. Don’t forget to tune your on- and off-chain telemetry for this and leave out the categories that ESAs have excluded (like trading and certain collateral uses). (eba.europa.eu)
• State Frameworks (U.S.)
  • California’s DFAL licensing kicks in on July 1, 2026, and its stablecoin requirements will affect many U.S. programs even if you have fed licenses. Get ready for some dual reporting and exam coordination. Also, keep in mind that the NYDFS guidance has been the baseline criteria since 2022--good to use as a practical benchmark for your reserve composition and daily redeemability SLAs. (dfpi.ca.gov)
• Accounting for Corporate Holders (Your Customers)
  • The FASB ASU 2023-08 (effective for fiscal years starting after Dec 15, 2024) is shifting in-scope crypto assets to fair-value accounting. Make sure you provide custodial statements, on-chain proofs, and some solid pricing references to help those enterprise holders close their books without a hitch. (kpmg.com)
• Chain Risk Governance
  • Keep chain exits and entries in mind as you set your policies. Circle’s plan to exit Tron in 2024 is a great example of how to handle chain risk thresholds, communicate about wind-downs, and ensure redemption continuity. Make sure to add similar clauses to your disclosures. (reuters.com)

---

Real‑time transparency that goes beyond PDFs

• Monthly attestations are a must-have. Circle does a great job by putting out their monthly reserve attestations. They also provide downloadable, machine-readable reserve composition and chain‑by‑chain circulation, all laid out in a consistent format. Check it out here: (circle.com).
• On‑chain Proof of Reserve (PoR) should be seen as a control mechanism, not just a marketing gimmick:
  • Chainlink's PoR lets you place reserve data right on the blockchain and integrates it into mint logic via “Secure Mint.” This means that if reserves are low, mints just won’t go through automatically. In scenarios where you're dealing with bridged or cross‑chain assets, PoR is essential to avoid over‑issuance. Don’t forget to share your PoR feed details and how they influence minting processes. More info here: (chain.link).
• Compliance automation is key:
  • Link your Know Your Transaction (KYT) to operational controls. Some KYT vendors have APIs that can help you screen flows and counterparties. You can also set “deny/pause” hooks to cross‑chain endpoints, which allows you to block mints or redemptions on the fly if any risks go beyond your policy limits. For more details, check out: (kytdoc.kyt-dev.e.chainalysis.com).

---

A deployment blueprint (EVM L2 + Solana + Sui)

Here’s a streamlined plan that we’ve rolled out pretty consistently across all programs.

1. Entity, Reserves, and Controls

• Set up an issuing entity that fits with your target jurisdictions (think GENIUS Act permit or state-qualified issuer; for EU-facing, consider EU EMT/ART authorization).
• Nail down your reserve policy: a mix of cash, insured deposits, and those ≤93-day Treasuries/repos. It’s important to have some custodial diversification and segregation going on, plus a monthly attestation vendor. Don’t forget to publish your redemption SLAs, fees, and lawful-order policy. (congress.gov)

2) Contracts per chain

• For ERC‑20, think 6 decimals, plus features like Permit and roles. On the Solana side, you'll want SPL with freeze authority. If you're looking for omnichain mobility, check out the Sui Move package with OFT wiring.
• Keeping things secure is key: use separate multi-sigs for different roles like minter, pauser, blacklister, and upgrader. Don’t forget HSM/MPC controls, timelocked upgrades, and a per-chain emergency pause just in case.

3) Cross‑chain Mobility

• If you're working with USDC-like deployments, make sure to integrate CCTP wherever it's available--think Arbitrum, Avalanche, Base, Ethereum, OP Mainnet, Polygon PoS, Solana, Sui, and so on. For those chains that don't support CCTP, you can use LayerZero v2 OFT or Wormhole NTT in a burn-and-mint setup with the following in mind:
  • Set rate limits based on direction and asset type.
  • Conduct global accountant invariant checks.
  • Include extra verifiers if your framework allows for it. You can find more info here.

4) Observability and Reporting

• We've got an indexer that checks daily to see how the net mints and burns are doing for each chain compared to the PoR and attestation numbers.
• For the MiCA “means-of-exchange” counter, we're keeping track of just the in-scope transaction categories and the single currency area. We also store rolling averages each quarter. If we hit 80% of the cap, we’ll send out an alert. Check it out here: eba.europa.eu

5) Compliance Plumbing

• We run KYT checks before and after transactions for mints/redemptions and big transfers. If something triggers an alert over our set limit, we’ll auto-pause using CCIP/NTT/OFT. Plus, we make sure to keep an auditable record of everything. You can learn more about this on Chainalysis.

1. Exchange and Wallet Integrations

• Share native token addresses for each chain, move away from wrapped tickers (don’t worry, we’ll include migration instructions), and offer a canonical chainlist in JSON format. Let’s team up with market makers to ensure we re-seed the pools using the native tickers first.

---

Example: A three‑month, three‑chain rollout

• Week 0-4: Entity & Reserves
  • Kick things off by nailing down the licensure path (think GENIUS Act permit or state-qualified), and setting up the KYC/KYT stack. You'll also want to cover reserve banking and MMF mandates. Don't forget to draft a redemption policy and some disclosures. You can check out the details here: (congress.gov).
• Week 3-6: Contracts & Audits
  • Time to get your hands dirty! Ship the ERC‑20 with Permit, SPL, and Sui Move modules. Complete that all-important security review, and stage everything on testnets using a mock PoR gate.
• Week 6-9: Cross-Chain Mobility
  • Next, let’s wire up CCTP (where it makes sense) and implement LayerZero OFT or Wormhole NTT for the other chains. Set up per-direction limits (like starting at $25M/24h) and create emergency pause runbooks to keep everything safe. You can dive deeper into this here: (developers.circle.com).
• Week 8-10: Reporting Stack
  • Now it’s time to deploy subgraphs or indexers, set up PoR feeds (if you’re using them), and get that monthly attestation pipeline in place. Make sure to cover MiCA counters and JSON reserve/circulation endpoints too. More info can be found here: (chain.link).
• Week 10-12: Migrate Liquidity
  • Wrap things up by coordinating with major DEXs and CEXs to make sure the native contract addresses are listed. Publish those canonical tickers and phase out any old bridged variants (like USDC.e-style) using incentives. For a bit more context, check this out: (cointelegraph.com).

---

Emerging best practices we recommend adopting now

• Go for burn-and-mint mobility as your default for keeping money simple. Think of wrapped versions as just a temporary fix. (circle.com)
• Make sure to include rate limits and set up anomaly-triggered pauses in your bridging stack (like CCIP/NTT/OFT). It’s a good idea to run some practice incident drills with your operations team. (docs.chain.link)
• Keep things transparent on-chain where it really counts (like PoR “Secure Mint” gating mints and machine-readable circulation for each chain). (chain.link)
• Get your MiCA monitoring set up right (remember to leave out trading and collateralized transactions as per the authorities’ clarifications, and only look at single currency areas). Don’t forget to automate that 40-working-day plan workflow! (eba.europa.eu)
• Release a “chain eligibility” policy, and be prepared to off-board chains that don’t make the cut anymore--like we did with Tron/USDC. (reuters.com)
• Assist enterprise holders in accounting properly under FASB ASU 2023-08 by providing fair-value data, custody attestations, and reconciliation exports. (kpmg.com)

---

What good looks like in production

• Technical
  • We’ve got native deployment on target chains, so you can move around seamlessly with CCTP/OFT/NTT--plus, there’s no liquidity stuck in those wrapped IOUs.
  • We handle decimals explicitly, have audited our math for cross-decimal conversions, and ensure our cross-chain handlers are idempotent.
• Security
  • Our endpoints are rate-limited and come with pause hooks. We also run invariant checks on the total supply and automate mint-gating using Proof of Reserves (PoR).
  • Security features include per-role multi-signature using HSM/MPC, along with emergency upgrade runbooks and time-limited freeze options.
• Compliance and Reporting
  • We provide a monthly overview of reserve composition that’s checked by a third party. You’ll also get machine-readable feeds for reserve and circulation, MiCA counters, and operational controls driven by Know Your Transaction (KYT) that come with audit trails.
  • Our workflows for lawful orders--whether it's to seize, freeze, or burn on each chain--are tested and straightforward.

By following these steps, your stablecoin can smoothly expand to new chains while remaining interoperable, secure, and compliant with regulations.

---

Further reading and references

• Check out the Circle Cross‑Chain Transfer Protocol (CCTP) supported blockchains along with the V1/V2 details right here.
• Want to know about Wormhole's Native Token Transfers (NTT)? Dive into the overview and architecture here.
• If you're curious about LayerZero v2's OFT quickstart and endpoint model, you can find all the info you need here.
• Chainlink has launched its CCIP GA, complete with rate‑limiting and a risk‑management network; get the scoop here.
• For those interested in MiCA RTS/caps and supervisory materials, check them out here.
• Here’s the lowdown on the U.S. GENIUS Act text and analyses; you can read through it here.
• If you're looking for the effective dates for FASB ASU 2023‑08, take a look at the details here.
• Check out a bridge risk case study on Orbit Bridge and see what went down here.
• Interested in USDC on Noble (Cosmos) and Polkadot Asset Hub? Get all the guidance you need here.
• And don’t forget to keep an eye on Circle's transparency page for their monthly attestation; you can find it here.

---

7Block Labs: Your Go-To for Stablecoins

At 7Block Labs, we’re all about helping issuers create, launch, and manage compliant, cross-chain stablecoins. We bring in top-notch observability and controls that ensure everything runs smoothly.

Interested in a readiness assessment or need to kick off an implementation sprint for CCTP/NTT/OFT + PoR? Just reach out--we’re here to assist!