hey @circle@samconnerone
been heads-down on @useCompassAI, an autonomous yield agent for multi-chain USDC, built on Arc. testnet's live.
- what it is
one USDC balance. every chain's best yield. you set the risk band once (1-10) and whitelist which protocols the agent can touch, Compass routes your USDC across chains and venues 24/7, stays inside your rules forever. non-custodial. pull out anytime.
think of it as the autopilot you'd actually trust with your treasury, because you wrote the flight rules.
- why i'm building it
i've been moving USDC between Aave, Morpho, Spark, Pendle for two years. every rate change means another tx, another bridge, another night watching gas prices. and the moment i automate any of it, i'm staring at a custody decision i don't want to make.
most "AI yield" products today either:
โ custody your funds
โ wrap an LLM around a single contract
โ hide what the agent actually did. none of those are what i want. i wanted to build the one i'd use
- why it's different, three things
โ you write the rules, the agent obeys forever. risk band + protocol whitelist + chain whitelist, all enforced on-chain. the agent physically cannot touch what you didn't approve. this isn't "trust the AI" โ it's "trust the contract".
โ LLM out of the hot loop. every routing decision runs on a deterministic Rust evaluator โ pure functions, fully reproducible, every decision logged. the LLM only shows up when you chat with the agent (< 30% of ticks). means we can scale without LLM cost eating the yield, and every action is auditable post-hoc. built on @arc, properly. USDC pays its own gas (no paymaster, no second token). @circle Gateway gives us sub-second cross-chain settlement with one unified balance, which means "your USDC on Arc" really is the same dollar that ends up on Arbitrum 400ms later. this is what stablecoin infrastructure should have been from day one.
- the part i'm most proud of
the dashboard shows every move the agent made, in real time, with an on-chain tx for every route. you can see the agent shift from Morpho on Base to Pendle on Arb the moment rates flip. you can pause it. you can withdraw mid-route. you can read every reasoning trace.
most "AI agents for finance" feel like a black box you have to trust. Compass is the opposite, it's a glass box you watch run.
also open-sourced the minimal reference architecture at arc-cross-yield-agent if you want to see how the cross-chain plumbing works without the production hardening.
honest feedback please, especially from anyone who actually puts testnet USDC through it. curious whether the "set rules once, agent obeys forever" model feels like real custody to you, or whether there are gaps i haven't seen yet.
@samconnerone LLM only runs at two moments: when the user sets a strategy, and when the system hits a genuine edge case.
Everything else is deterministic. No per-tick inference, no token burn at scale.
by @useCompassAI
๐ Just dropped: New Compass Landing Page!
Cleaner design, smoother experience, and way better product showcase.
Whoโs already checked it out? Drop your thoughts
@arc@samconnerone@bobbilee
Compass is now live on Arc Open Source Showcase ๐
Excited to be building something cool on @arc.
Docs and site are all ready.
If you're into cross-yield, come give it a taste
Compass AI docs are live.
A non-custodial $USDC yield agent on @arc, the agent moves your capital between venues, inside rules you set on-chain.
https://t.co/n82E4AFTKO
Pause, never reroute mid-flight.
Once a BurnIntent is signed, it's atomic, either the bridge completes or USDC stays put on the source chain (Gateway guarantees this, no orphaned hops).
The agent never initiates a new route while another is in
flight. If the destination chain is unhealthy, the evaluator
just holds, funds remain spendable on the source chain or in the existing position. Liveness fail, not safety fail.
Next route fires once health checks pass.
hey @circle@samconnerone
been heads-down on @useCompassAI, an autonomous yield agent for multi-chain USDC, built on Arc. testnet's live.
- what it is
one USDC balance. every chain's best yield. you set the risk band once (1-10) and whitelist which protocols the agent can touch, Compass routes your USDC across chains and venues 24/7, stays inside your rules forever. non-custodial. pull out anytime.
think of it as the autopilot you'd actually trust with your treasury, because you wrote the flight rules.
- why i'm building it
i've been moving USDC between Aave, Morpho, Spark, Pendle for two years. every rate change means another tx, another bridge, another night watching gas prices. and the moment i automate any of it, i'm staring at a custody decision i don't want to make.
most "AI yield" products today either:
โ custody your funds
โ wrap an LLM around a single contract
โ hide what the agent actually did. none of those are what i want. i wanted to build the one i'd use
- why it's different, three things
โ you write the rules, the agent obeys forever. risk band + protocol whitelist + chain whitelist, all enforced on-chain. the agent physically cannot touch what you didn't approve. this isn't "trust the AI" โ it's "trust the contract".
โ LLM out of the hot loop. every routing decision runs on a deterministic Rust evaluator โ pure functions, fully reproducible, every decision logged. the LLM only shows up when you chat with the agent (< 30% of ticks). means we can scale without LLM cost eating the yield, and every action is auditable post-hoc. built on @arc, properly. USDC pays its own gas (no paymaster, no second token). @circle Gateway gives us sub-second cross-chain settlement with one unified balance, which means "your USDC on Arc" really is the same dollar that ends up on Arbitrum 400ms later. this is what stablecoin infrastructure should have been from day one.
- the part i'm most proud of
the dashboard shows every move the agent made, in real time, with an on-chain tx for every route. you can see the agent shift from Morpho on Base to Pendle on Arb the moment rates flip. you can pause it. you can withdraw mid-route. you can read every reasoning trace.
most "AI agents for finance" feel like a black box you have to trust. Compass is the opposite, it's a glass box you watch run.
also open-sourced the minimal reference architecture at arc-cross-yield-agent if you want to see how the cross-chain plumbing works without the production hardening.
honest feedback please, especially from anyone who actually puts testnet USDC through it. curious whether the "set rules once, agent obeys forever" model feels like real custody to you, or whether there are gaps i haven't seen yet.
Launch a cross-chain yield aggregator on @arc in minutes with arc-cross-yield-agents โ the core component spun out from @useCompassAI.
Out-of-the-box and production-ready.
If youโre a builder experimenting with Arc, this is a must-have. Donโt miss it!
@samconnerone@circle
Today we're open-sourcing arc-cross-yield-agents โ a reference dApp for builders shipping AI agents on @arc.
Built by the @useCompassAI team for the Agora Agents hackathon, released under MIT.
โ What it is
A minimal, fork-friendly implementation of a chat-driven yield agent on Arc. A user types "invest 5 USDC in Aave" โ the agent bridges USDC from Arc to Arbitrum via @circle Gateway and supplies it into Aave v3. One prompt. One cross-chain round trip. One position.
Claude-powered tool dispatch, streaming reasoning, structured tool trace UI. ~3 contracts, ~1500 LOC of Rust, one Next.js frontend. Designed to read end-to-end in an afternoon.
โ Why we built it
We've been building Compass โ a hardened AI yield agent for multi-chain USDC and along the way we kept hitting the same five walls every Arc agent builder will hit: gas tokens, cross-chain UX, smart-account scoping, deterministic execution, and "how do other builders fork this."
The circlefin/arc reference repos handle payments really well. They don't yet cover AI-agent-driven cross-chain flows. We figured the gap was worth filling โ properly, with code other teams can ship on top of.
โ Three things worth highlighting
1. Zero paymaster on Arc. USDC pays its own gas. The same dollar the user holds funds validation. The entire Arc-side smart account ships without a paymaster โ this is what account abstraction should have been on every chain from day one.
2. Same address on both chains. CREATE2 + matched deployer nonce โ the AgentAccount lives at the same address on Arc and Arbitrum. Gateway mints to "you" on the other side with no address-mapping table. One less footgun for the next builder.
3. Minimal by design. No Diamond, no session keys, no policy engine, no cron. Those belong in production โ they don't belong in a reference. The hardened version of all of them lives in Compass for teams who want to see how the production wiring looks.
Repo: https://t.co/NbLfPDTiCU
Production version: testnet[.]usecompassai[.]com
@samconnerone