Money
Sage on Arc
One account, on one chain, that anyone can fund. Sage can keep a wallet for you on Arc — Circle's chain, where USDC is the gas. Send USDC to it from any wallet or exchange, from anywhere. The agent launches work and pays people from it, inside a mandate it cannot widen. Withdraw to any address, any time. Nothing else to buy, hold, or find.
Where this stands today. Arc is on testnet, and Sage runs there with test USDC — the whole loop below is proven on it. Arc mainnet opens on 16 September 2026; the account, the mandate and the receipts move there with one registry entry and one factory deploy. Until then the account every founder gets is on GOAT Network, real USDC, and Starknet is the private rail; Arc is a second tab on your account page, labelled testnet, for anyone who wants to try it now.
Why Arc
- USDC is the gas. On every other chain a funded account still needed a second token — BTC on GOAT, ETH elsewhere — before it could move. On Arc the USDC you deposit pays for its own transactions. Funding is the whole setup.
- The same money everywhere. The account holds USDC; the vaults hold USDC; the receipts are in USDC; a worker is paid in USDC. No wrapped anything, no bridge in the middle of a payout.
- Stablecoin-native rails. Circle's tooling on Arc is built for exactly this: programmable dollars, payments, treasuries.
What the account is
A wallet held by Privy for you, born under a mandate: an on-chain policy that lets the agent create a campaign vault through Sage's factory, fund it up to your per-campaign cap, and activate it — and nothing else. Unspent money can only return to you. A withdrawal attaches a one-time permit for the exact address and amount you named, then the account re-locks to the mandate, whatever happened.
- Fund it — the address and a QR code on the Arc tab of your account page. On testnet, test USDC comes from Circle's faucet.
- Use it — post work, or let Sage run it: the agent proposes each move with its reason and launches inside your ceilings.
- Withdraw — to any address on the chain. The activity list is read from the chain itself, not from a table of ours.
What is proven on Arc testnet
- The V2 CampaignVault factory is deployed at
0xfAc019eF6d8B36FE33233244ff0b97f0D9e99B8c. - An account launched a gig from its own wallet — create, approve, fund, activate, four transactions signed inside the mandate — and a worker who submitted a public page was judged and paid on chain, with a receipt. Nobody touched a key.
- An account withdrew to another address through a scoped permit and re-locked.
Arc mainnet is not open yet. The day it opens, the same account, mandate and receipts move there with one registry entry and one factory deploy, and Arc becomes the default rail for new accounts. GOAT Network and Starknet stay exactly as they are: GOAT holds the first forty-one real payouts, Starknet is the private rail. Nothing about a campaign already running on either changes.
For teams and organisations
A workspace owner's account is the organisation's wallet. Members are paid from vaults the account funds; the owner sees every move, every receipt, and can withdraw what is unspent. A cooperative in Kingston, a programme funding forty MSMEs, a company paying contributors across the world — the same account, funded in USDC from wherever the money is.