CCTP is now supported on Stellar. In this Release Notes episode, @Hui Jing from Circle DevRel explains what changed, how Stellar fits into CCTP, and what developers should know when building USDC flows to or from Stellar. CCTP, or Cross-Chain Transfer Protocol, is Circle’s burn-and-mint protocol for moving USDC across supported blockchains. With Stellar support, builders can include Stellar in CCTP-powered USDC transfer flows. This episode covers: - Stellar’s CCTP domain ID: 27 - How CCTP message address handling differs on Stellar - When to use the CctpForwarder contract - Why user and muxed accounts need a USDC trustline - How Stellar’s seven-decimal USDC precision maps to CCTP’s six-decimal message amounts Resources: - Supported domains table: [https://developers.circle.com/cctp/concepts/supported-chains-and-domains] - Stellar contract addresses: [https://developers.circle.com/cctp/references/stellar-contracts] - Stellar technical overview: [ https://developers.circle.com/cctp/references/stellar ] - Quickstart: transfer USDC to and from Stellar: [https://developers.circle.com/cctp/quickstarts/transfer-usdc-stellar-arc ]

The final post in the Unified Balance Kit series covers the preflight checks and recovery paths apps need around spend(), especially when delegated flows or mint-side failures can affect execution.

Transaction memos on Arc give developers and businesses a way to attach structured context to onchain actions on Arc. That makes payments, payouts, deposits, withdrawals, and other financial workflows easier to reconcile, attribute, and connect to offchain systems.

Part three of the Unified Balance Kit series focuses on partial liquidity and fallback rules for apps that start from available USDC but still need to validate each execution route.

This opening post in the Unified Balance Kit series explains how payment and treasury apps can start from available USDC instead of source-chain selection, with route readiness and failure handling kept in the app layer.

Uniswap is coming to Arc Mainnet. For builders, this matters because liquidity is not a secondary feature of an onchain economy. It is part of the application layer. Wallets need swap paths. DeFi protocols need routing and pool access.

Arc Testnet is upgrading to v0.7.2 with a hardfork on June 18, 2026 at 12:00 UTC. The developer-facing features are transaction memos, which let builders attach payment references directly onchain, and batch transactions, which let multiple calls execute in one transaction. Node operators must upgrade to v0.7.2 before activation or their nodes will desync from Arc Testnet.

A look at the thinking behind Arc's new privacy whitepaper, and the features that set our approach apart from every other swing at onchain privacy.