Last Friday, I ran an Arc Studio workshop for 100+ developers building with AI agents, and one thing became clear. Many developers are building products where blockchain could be genuinely useful, but the complexity of building onchain is still holding them back. A recurring theme during the session was that many developers see smart contract complexity as a barrier to building onchain. That’s what excites me about Arc Studio. Helping developers use blockchain to innovate, without needing to become smart contract experts first. I left the session inspired by what becomes possible when that barrier comes down. Let's keep building. Try it out at studio[dot]arc[io]

There is one Arc Studio feature that, if you’re not using while building onchain, you’re debugging blind. It’s called Tracing. Let’s imagine you’re building an app that sends USDC. You click send and approve the transaction in your wallet, but your app is still loading. Now you’re not sure what’s going on. Did the wallet connect? Was the transaction submitted? Was it confirmed onchain? Did the contract emit the expected event? Instead of checking your browser console, wallet, and explorer separately, Tracing shows the full flow in one timeline. You can see every step, how long it took, where something failed, and the data your app sent and received. You could paste logs into an AI coding tool and ask it to debug them. But the real value of Tracing is that it automatically captures the full onchain flow first, so the AI has the right context to explain what happened. You can also click Ask Studio and let the AI explain the trace for you. Start building today at studio[dot]arc[dot]io

Everyone is now a smart contract engineer. With Arc Studio, all you have to do is describe what you want to build, and it will write the smart contracts, test them, and deploy them for you. A wonderful time to start building.

I loved every part of creating this! From the research to the scriptwriting to the video creation! The goal was to build a clear resource to help developers understand Arc’s architecture. Happy to see that it’s happening!

We’re working on a new series that explains how to build AI agents that are true economic actors with Circle Agent Stack. It will include practical tutorials you can follow with any AI agent harness. Can’t wait to share what we’ve been building. Stay tuned.

If you live in the UK, this is how to turn your fan into AC . - Put some salt in a water bottle - Freeze it properly - Attach it to the back of your fan - Put a towel at the base so water doesn’t fill your floor when the ice melts This can last for about 6 hours or more blowing cold air any direction. The salt helps it stay colder for longer because salt lowers the freezing point of water.

Today, we launched Circle Agent Stack, and I want to explain the core problem this solves. AI agents can browse, reason, write code, call tools, and complete tasks. But they still struggle with one very basic thing: paying for services on the internet. Let’s say an agent needs to call a paid API. That sounds simple. But the normal internet payment flow is built for humans. - Create account. - Add card. - Choose plan. - Go through checkout. - Approve payment. - Wait for access. That works for people. It does not work for autonomous software. An agent does not need a checkout page. It needs a wallet, a price, and a payment protocol. That is what Circle Agent Stack enables. With Agent Wallets, developers can give AI agents wallets funded with USDC. With Circle CLI and Circle Skills, agents in tools like Codex, Claude Code, and Cursor can discover services and transact programmatically. And with Nanopayments powered by Circle Gateway, agents can pay for APIs, data, compute, and services in real time. This matters because the natural pricing model for agentic services is usage-based. Agents should be able to pay for resources at the moment they need them, without being forced through a card form, checkout page, or manual approval flow. From a developer perspective, you can create an agent wallet, fund it with USDC, and let your agent start paying for services. From a seller perspective, your service can accept USDC from agents without forcing them through a human payment flow. The bigger shift is simple: APIs can become paid resources for agents. Software can pay software for useful work. That is agentic commerce. We are live today. Start building here