Vyper's recent work on Arc Testnet brings three layers into one stack that rarely show up together: agent identity through ERC-8004, software-native settlement through x402 and Circle, and programmable financial controls like escrow, subscriptions, split payments, and spending limits.

The Arc Privacy Whitepaper frames privacy as opt-in confidentiality for real-world financial workflows, not anonymity. The core message is confidentiality with oversight: giving applications a way to protect sensitive transaction data and private smart contract state when needed, while supporting governed visibility for authorized parties. In this livestream, Circle will walk builders through the whitepaper and the design principles behind privacy on Arc. The discussion should cover why public-by-default transparency can limit use cases such as payroll, treasury operations, trading, lending, and swaps, how the Arc roadmap approaches confidential execution through ArcaneVM, and what developers should understand now while privacy functionality remains on the roadmap. Arc’s privacy features reflect a proposed design that includes selective shielding of certain onchain data elements. The scope, functionality, and rollout timeline of the Arc privacy features are subject to change and may be modified, delayed, limited, or discontinued at any time in the sole discretion of Arc Network Services LLC. See Arc Privacy Sector: Keeping Blockchain State, Transactions, and Accounts Private and Quantum Safe for more. --- Arc is offered by Circle Technology Services, LLC (“CTS”). CTS is a software provider and does not provide regulated financial or advisory services. You are solely responsible for services you provide to users, including obtaining any necessary licenses or approvals and otherwise complying with applicable laws. Arc has not been reviewed or approved by the New York State Department of Financial Services. The product features described in these materials are for informational purposes only and may be modified, delayed, or cancelled without notice at the sole discretion of Circle Technology Services, LLC. Nothing herein constitutes a commitment, warranty, guarantee, or investment advice. USDC is issued by regulated affiliates of Circle. A list of Circle’s regulatory authorizations can be found here.

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 ]