Hey r/ethereum,

    During a 5-day hackathon on Arc L1, I built ArcWarden — an agent that protects other AI agents handling USDC onchain.

    The problem

    AI agents can execute transactions autonomously.

    If one gets compromised, it can drain a wallet instantly.

    There’s no native security layer — and existing solutions cost more than the transactions themselves.

    The idea

    ArcWarden is not a security tool.

    It’s an economic agent that lives inside the system it protects.

    It charges $0.001 USDC per decision

    It evaluates transactions before execution

    It returns: ALLOW / BLOCK / ESCALATE

    It pays for deeper analysis itself (Claude API)

    It logs decisions onchain

    Why this is different

    Instead of adding security from the outside,

    ArcWarden participates in the economy:

    → Agents pay ArcWarden

    → ArcWarden secures them

    → ArcWarden pays for intelligence

    → Everything is autonomous

    A closed agent-to-agent loop.

    What’s real (not just a demo)

    389 onchain transactions

    Real Circle wallets (multi-agent simulation)

    Smart contract logging blocked attacks

    ~1,600+ USDC protected during testing

    Contract: https://testnet.arcscan.app/address/0x17430A67e11535466cC5f17e736D5e4643B86ba1

    Honest note

    The demo was too technical — reviewers didn’t understand it.

    That’s on me. Still improving how I explain it.

    Stack

    Python · FastAPI · web3.py · Vyper · Circle DCW · x402 · SQLite · numpy

    If you're building in agentic systems or onchain automation,

    I’d really appreciate your feedback.

    GitHub: https://github.com/ibonon/Arcwarden

    — Eric Warma

    Solo builder · Burkina Faso

    I built an autonomous security agent for AI wallets — didn’t win the hackathon, but I think the idea matters
    byu/Any_Good_2682 inethereum



    Posted by Any_Good_2682

    1 Comment

    1. Otherwise_Wave9374 on

      This is a really interesting framing, making the security layer itself an economic agent. The ALLOW/BLOCK/ESCALATE triage matches how humans actually review transactions, and the idea that ArcWarden pays for deeper analysis when needed is clever.

      One thought, how do you handle “safe but unusual” transactions so you do not end up blocking legit activity? Like whitelists, per-agent spend limits, or learning a baseline over time.

      We have been tracking a bunch of agent security patterns (especially around wallets and tool execution) here if helpful: https://www.agentixlabs.com/

    Leave A Reply
    Share via
    Share via