Follow the money. Check the decision.
AERIS connects live Arc USDC activity with personal wallet transfers and independently checked receipts.
Review AERIS in three steps
- Inspect live activity — open Data Health, select a transfer and compare its Arc explorer evidence.
- Prepare a personal transfer — connect your wallet, enter a recipient and amount, and review the USDC network fee.
- Check settlement — after approving a transfer in your wallet, match its recipient, amount and confirmed receipt. Export the receipt for independent review.
No wallet connection is required to observe the network. Public transfers use each visitor’s own wallet. Circle treasury tools are a separate operator workflow.
How the evidence worksObservation, analysis and verification
Observe → Analyze → Verify
Arc is the source of the product’s economic evidence: native USDC transfer events, contract calls, deployments, and wallet/contract classification. The observation window follows chain time, rather than a simulated clock.
- Observe
- Rolling 10-minute USDC window; coverage and stale-head diagnostics.
- Analyze
- Deterministic signals, policy checks, proactive investigations and evidence strength.
- Verify
- Transaction and block references, linked ledger selections, explorer evidence.
- Visualize
- Responsive 2D/3D views. Flows ≥1,000 USDC are visualized; ingestion observes smaller transfers too.
Circle wallet identityLive verification on Arc
AERIS Agent Wallet
CIRCLE WALLETSObserve a developer-controlled wallet on Arc. Verify its identity with Circle and its USDC balance against the chain.
The public server observes this wallet. Invoice payments are signed by Circle through the operator’s local runner.
Real data, explicit limits
When RPC access is unavailable, AERIS reports unavailable or partial data. Empty activity is never replaced by mock transactions.
What is demonstrated
| Capability | Current scope | Acceptance evidence |
|---|---|---|
| Arc intelligence | Implemented | Live RPC observation, ledger and evidence links; deployment health must be checked live. |
| Personal USDC transfers | Browser wallets and wallet mobile browsers | User wallet approval, fresh balance/fee checks and exact Arc receipt verification. No hosted custody or automatic spending. |
| History & pending requests | Arc recovery and portable notes | Validated backups, fresh receipts, bounded status polling and nonce-checked replacement/cancellation. |
| Mobile QR / Circle email wallets | Implemented; configuration pending | Reown project setup and Circle App ID/email delivery required before these connections are available. |
| Circle wallet observation | Configured; verified at runtime | Circle identity + current Arc block + native USDC balance. |
| Circle invoice payments | Local runner implemented; live settlement demonstration pending | Recipient allowlist, durable budget reservations, local approval, Circle EVM signing and exact Arc receipt verification. |
| Usage & pilots | To be measured | Real user feedback, investigation usage and pilot outcomes; no invented traction. |
Technical scope & sourceExecution, tests and limitations
USDC totals use verified transfer events only. Contract activity is a bounded sample from recent blocks, rather than a full historical index. Wallet identity does not prove a transfer’s intent; the agent distinguishes evidence from interpretation.
Public treasury spending remains disabled. User-controlled Circle payments require each user’s own approval challenge. The invoice runner executes on the operator’s computer with privately entered Circle credentials and a persistent journal. Browser settings become authority only after the operator saves the policy locally. Operator execution and a confirmed live receipt are still required to demonstrate an actual payment.