Circle confirmed on August 7, 2026, that native USDC and CCTP are now live on X Layer, OKX’s Ethereum layer-2 network. The launch replaces the bridged USDC.e token X Layer previously relied on.
Key Takeaways
- Circle’s developer account announced native USDC and CCTP are live on X Layer, OKX’s zero-knowledge Ethereum scaling network.
- Native USDC is issued directly by Circle, not wrapped or bridged, and Circle describes USDC as the world’s largest regulated dollar stablecoin.
- CCTP, short for Cross-Chain Transfer Protocol, lets apps move USDC across chains, and supports payouts, treasury operations, payments, and crosschain flows.
- Circle published a developer quickstart guide so builders can start integrating USDC into their apps right away.
- The quickstart uses Viem and Node.js to transfer USDC between wallets on EVM chains, requiring Node.js v22.6+ and a funded testnet wallet.
What Happened?
X Layer developers can now build directly against Circle-issued USDC instead of the bridged version of the token. Circle’s official developer account posted that native USDC and CCTP are live on X Layer, and that the integration lets builders manage payouts, treasury, payments, and crosschain flows while powering USDC movement with CCTP.
Before this launch, X Layer supported USDC through the Circle-endorsed Bridged USDC Standard, which mints a bridged representation of the token (commonly labeled USDC.e) once the original USDC is locked on Ethereum. That model works, but it ties every dollar on X Layer to the bridge contract’s own security and liquidity. Native issuance removes that middle layer entirely, so a USDC balance on X Layer is now the same asset Circle mints anywhere else, not a claim on tokens locked somewhere else.
Native USDC and CCTP are now live on @XLayerOfficial!
— Circle Developer (@BuildOnCircle) August 7, 2026
→ Build with the world’s largest regulated dollar stablecoin
→ Manage payouts, treasury, payments, and crosschain flows
→ Power seamless USDC movement with CCTP
→ Easily integrate USDC into your apps
Start building… pic.twitter.com/m14MHFbTav
How Native USDC and CCTP Work?
Native USDC means Circle mints and redeems the token directly on X Layer, with each unit backed 1:1 by Circle’s reserves rather than by a bridge’s locked collateral. CCTP is the mechanism that moves that native USDC between chains.
It burns USDC on the source chain and mints an equivalent amount natively on the destination chain, instead of locking tokens and issuing a wrapped IOU. Circle frames CCTP as the tool for powering seamless USDC movement across chains, which removes the wrapped-asset step that bridged USDC.e required.
That distinction matters for institutional users moving stablecoin liquidity across chains, where counting on a third-party bridge’s solvency adds a layer of risk on top of smart-contract risk. Decentralized stablecoin adoption has been tracked closely as more of that liquidity shifts onto native, non-custodial rails instead of wrapped bridge tokens, and a burn and mint model removes one of the recurring failure points in that architecture: the bridge contract itself.
X Layer runs on Polygon’s Chain Development Kit as a zero-knowledge Ethereum layer-2, with OKB as its native gas and settlement token. Circle’s post links directly to its USDC Quickstart Guide for developers building on the network.
Circle has followed a similar playbook elsewhere: its native USDC rollout on Hyperliquid also replaced a bridged representation with direct issuance, and its own Arc blockchain is built around native USDC settlement from the outset rather than retrofitting it later.
What Builders Get?
Circle shipped a companion resource for developers alongside the announcement rather than leaving the integration to trial and error. The quickstart guide shows how to transfer USDC between wallets on EVM chains using Viem and Node.js, walking through a script that checks wallet balances and sends a test USDC transfer on a testnet. Running it requires Node.js v22.6 or later, a funded testnet wallet holding testnet USDC, and native testnet tokens for gas, with Circle’s own faucet available to fund the testnet USDC balance.
The script relies on client attached ERC-20 token actions and the USDC token definition from Viem’s token library, so the same transfer flow works across supported EVM testnets without separate handwritten configurations per chain. For a network like X Layer that competes for developer attention against other exchange-linked layer-2s, a ready-made, chain-agnostic transfer script lowers the cost of shipping a USDC-native app on day one.
CoinLaw’s Takeaway
This launch reads as infrastructure hygiene rather than a standalone product bet. X Layer gains the same native issuance, burn and mint stablecoin rail that Circle has been rolling out across its other layer-2 partners, and the practical effect for builders is that a USDC balance on X Layer stops being a synthetic claim on locked collateral and becomes the same instrument Circle issues everywhere. The quickstart Circle shipped alongside the launch signals it expects developers to start moving payouts, treasury balances, and app payments through this rail immediately, not just hold the token.
The mechanism is what carries the real weight here. Burn and mint CCTP eliminates the bridge-operator and locked liquidity trust assumptions that come with a wrapped token like USDC.e, which matters most for treasury and payments use cases where counterparty risk in the settlement rail is unacceptable. Extended to the rest of Circle’s multichain footprint, the pattern points toward native, regulator-legible USDC becoming the default settlement layer across major EVM-compatible networks, with bridged wrapped tokens phased out as each integration matures.
