← arcurrent
Live on Arc Mainnet
Arcurrent

An open settlement primitive for agents, and the autonomous treasury agent that's already its first live user.

02 / 12 The problem

Treasury payments run on trust, not proof.

  1. No custody without a chaperone

    An agent that's supposed to act alone still needs a human to hold the keys or approve the transfer.

  2. No provable record

    A wrong payment is a support ticket and a spreadsheet, not a transaction anyone outside the company can check.

  3. No settlement fast enough to watch closely

    If checking a balance costs almost as much as the payment, nobody checks it often enough to catch problems early.

1–5 days
typical settlement time for a cross-border business wire through correspondent banking
03 / 12 The answer

A ledger-writing machine, not a script with a cron job.

Arcurrent reads what's owed, decides from the real treasury balance, the due date, and a reserve floor, and settles by creating and releasing a mandate on MandateEscrow, an open primitive any address can fund, fulfill, or read.

Nothing here is simulated. Every figure on the next slide is a real transaction hash on Arc mainnet, not a mock.

04 / 12 Proof

Two real settlements, five real transactions, on Arc mainnet.

Captured 2026‑09‑22, real mainnet USDC. Current counts are on the live dashboard and Mandates table.

Two obligations, $0.05 and $0.03 USDC, settled by creating and releasing mandates on MandateEscrow · not a pre-funded pool, straight from the treasury wallet's own balance.

$0.20treasury wallet balance after funding
↓ mandate #0: approve, create, release · $0.05 to the fulfiller
$0.14balance after mandate #0, gas included
↓ mandate #1: create, release · $0.03 to the fulfiller
$0.10balance after mandate #1, gas included
Approve Treasury wallet approves MandateEscrow to pull USDC (one-time, max allowance) 0x7bde…3786
Create #0 Mandate #0 created and funded, $0.05, fulfiller set 0xfe7a…a53e
Release #0 Mandate #0 released atomically, reputation ledger updated 0xb7fa…06b9f
Create #1 Mandate #1 created and funded, $0.03, fulfiller set 0x29eb…3430
Release #1 Mandate #1 released; webhook flips the obligation to "settled" within seconds 0x4df8…42c63

Fulfiller reputation after both: 2 completed, 0 refunded, $0.08 volume settled · read live from the contract, not this project's database.

Bonus proof, captured 2026‑09‑23: the one capability the two settlements above don't show, since both paid a single destination.

Split release Mandate #4 released in one transaction to two destinations at once, $0.04 to the fulfiller and $0.02 fee to a second address · atomic, not two separate transfers 0x9acb…1398
05 / 12 How it works

Four real primitives, one decision loop.

Developer-Controlled Wallets

The treasury and liquidity wallets are Circle-custodied. No private key lives in this codebase.

MandateEscrow

A permissionless contract on Arc mainnet: fund a mandate for anyone, prove fulfillment, release atomically, split payouts, refund on deadline. Reputation updates on-chain. Not project-owned · this agent is just its first live caller.

App Kit · Bridge (CCTP)

Circle's App Kit SDK, kit.bridge(): cross-chain USDC top-ups when a payment would breach the reserve floor. Proven on testnet; disabled on mainnet until a Live-environment source wallet is funded.

x402 nanopayments

The agent pays a sub-cent fee for the live FX rate it needs before acting on a foreign bill.

This is the pattern Circle's Agent Stack formalizes: wallets, an onchain program, cross-chain liquidity and a machine-payable service, wired into one loop. Built directly against those primitives rather than a starter kit, since the loop itself is the product.

06 / 12 Why Arc

Arcurrent: current, twice.

Gas paid in USDC, the same money moving through the system, not a second token to keep topped up. Settlement under a second, so a balance check every few minutes doesn't cost more than the payments it's protecting.

That's the whole bet: money that moves as fast as the decision to move it.

07 / 12 Why now

The money already moved on-chain. The agent didn't.

USDC already sits in real company treasuries as real settlement money. What's been missing isn't the rail, it's an agent trustworthy enough to be handed the keys and left alone.

Arc is the first L1 built specifically so that agent doesn't need a human chaperone: USDC-native gas, sub-second finality, and a Circle stack built for custody without a human touching a key.

08 / 12 Status

What's real, what's gated.

09 / 12 Fit

A primitive, not another single-purpose demo.

Relevance to Arc

Impossible on a chain with volatile gas or probabilistic finality: USDC-native gas and sub-second settlement are what make per-obligation mandates economical at all.

Technical credibility

Real contracts, real mainnet deployment, a real autonomous caller · not a testnet-only illustration.

Depth

Solves trust and accountability, atomic multi-party settlement, and portable reputation in one primitive, rather than one narrow feature.

Promise

Open by design: any other agent or hackathon builder can fund, fulfill, or read a mandate today, no permission needed.

10 / 12 What's next

Where this goes from here.

Other callersMandateEscrow is open today; the next real proof is a second, unrelated agent funding or fulfilling a mandate
StableFXAuto-settle non-USDC obligations once access lands
LiquidityA funded mainnet-side source chain, re-enabling the CCTP top-up path
PilotA real company's treasury, not a test wallet
11 / 12 The ask

What we're looking for.

01

The microgrant

Non-dilutive fuel to keep building the primitive out, not just the agent on top of it.

02

StableFX access

The one piece that's flagged, not faked. This closes the last gap between "correctly identifies" and "fully autonomous."

03

Introductions

To a real treasury with genuine recurring obligations to pilot against, and to other Arc builders whose agents could be MandateEscrow's second caller.

12 / 12 See it settle

Thank you.