ArcFlow - Trustless Financial Kernel

Direct AI wallet access is unsafe: a single hallucination or prompt injection can cause irreversible loss. ArcFlow solves this by acting as a deterministic firewall between Gemini 2.5 and the Arc Network, blocking faulty AI actions from draining wallets. Instead of giving the AI direct signing rights, ArcFlow routes payments through an auditable policy engine and a secure state machine that validates every transaction intent and rejects anything ambiguous or unsafe before it reaches the blockchain. ArcFlow combines Circle’s USDC with Arc’s payment rails to provide safe, programmable money: Gemini 2.5 Flash acts as the brain (a stateless planner that proposes actions via JSON), while ArcFlow is the guard, validating each proposal against strict, hard‑coded rules like max spend limits and whitelists. Only validated transactions are signed and broadcast to the Arc Testnet. This architecture enables autonomous agents—such as refund bots or commerce copilots—while ensuring funds never move outside clearly verifiable policies. Under the hood, I implemented this as a secure state machine using a production‑ready stack: Gemini 2.5 Flash via the Vercel AI SDK for structured planning, a custom TypeScript risk engine for policy enforcement, `ethers.js` for Arc Testnet interaction, and a Node.js backend on Vercel to keep keys secure server‑side. Circle Product Feedback (Required): I used the Arc Testnet, USDC, the Circle Faucet, and `ethers.js` in an environment where USDC is the native gas token, so agents can manage a single asset for both payments and gas. The developer experience was strong overall; the Faucet and ArcScan made on‑chain testing straightforward. I’d suggest surfacing RPC endpoint documentation more prominently and adding a simple “Check Balance” tool on the Faucet page to speed up debugging.