Arc

MANDATE enters both Arc bounties, explicitly: Best Agentic Economy (via ERC-8004 identity/reputation and ERC-8183 job escrow, built from the Circle Agent Stack) and Best DeFi Stablecoin-Native Pool (via the treasury’s revolving credit facility and conditional, multi-step settlement).

USDC is gas and unit of account

Arc’s USDC is both the native gas token and an ERC-20, at the same address, with different decimals — 18 for the native path, 6 for the ERC-20 path. Verified empirically on-chain: the same account’s native balance and ERC-20 balance differ by exactly 10¹². Every conversion in this codebase goes through one named helper; nothing inlines the arithmetic.

The treasury as a credit facility

Agents never hold float beyond a small, hard-capped gas draw. AgentTreasury pays a counterparty directly from the pool via payTo or funds an ERC-8183 job via fundJob — checked against MandateAnchor first, then against the mandate’s own leaky-bucket rolling budget, then against the pool’s utilisation cap. Every dollar that leaves the pool accrues interest to the org until repay’d — a spending mandate and a credit limit are the same object.

Advanced programmable money flows

• Conditional payments — every spend gated by revocation, expiry, cap, and allowlist.
• On-chain rolling budgets — a leaky-bucket accumulator, not a database counter.
• Multi-step settlement — treasury → escrow (ERC-8183) → provider, in one call.

ERC-8004 and ERC-8183, composed rather than reimplemented

Identity, reputation, and job escrow all reuse Arc’s reference deployments directly. The reference Jobs contract’s hook extension point is admin-gated — this design was never built around it. ReputationRegistry.giveFeedback is third-party-only by the standard’s own design, so the demo’s evaluator is a distinct key from the job’s participants.