Circle announced Friday that native USDC and its Cross-Chain Transfer Protocol are now live on X Layer, OKX's Ethereum-compatible blockchain, enabling transfers across chains and expanding stablecoin availability on the network.
X Layer operates as a layer-2 solution built on Ethereum and is compatible with the Ethereum Virtual Machine. The addition of native USDC and CCTP functionality allows users to move the stablecoin between X Layer and other supported chains without wrapping or relying on third-party bridges. CCTP handles the burn-and-mint mechanism that settles transfers across compatible blockchains.
Circle has deployed USDC across more than 10 blockchains since launching the stablecoin in 2018. The company introduced CCTP in 2023 to reduce counterparty risk in cross-chain transfers by eliminating the need for intermediaries. X Layer joins networks including Ethereum, Polygon, Optimism, Arbitrum, Solana, and Base as destinations for native USDC and CCTP support.
OKX operates one of the world's largest cryptocurrency exchanges by trading volume. The exchange launched X Layer in February 2024 as an infrastructure play to reduce withdrawal fees and settlement times for its users. The network has processed billions in transaction volume since launch, according to on-chain data.
The native USDC deployment and CCTP integration follow OKX's broader push to build developer tooling and liquidity on X Layer. Circle prioritized X Layer as OKX stands as a major conduit for trading activity and institutional access to crypto markets.
USDA expansion across layer-2 solutions and emerging chains has accelerated over the past two years as developers seek native stablecoin liquidity without relying on wrapped versions. The X Layer deployment adds another infrastructure piece to the ecosystem, though USDC remains concentrated on Ethereum mainnet and a handful of high-volume chains like Arbitrum and Optimism.
The number to watch is whether X Layer's USDC transaction volume reaches meaningful scale within six months, indicating whether the integration drives material user activity or remains a technical availability play.
