{"slug": "my-ai-agent-works-for-me-every-day-here-s-how-i-make-it-prove-everything", "title": "My AI Agent Works for Me Every Day. Here's How I Make It Prove Everything.", "summary": "A developer competing in the zkVerify Agent Games Creator Track described running a daily-use AI agent, アカメ, under a strict verification regime: on-chain receipts for any value-moving action, signed session transcripts for competition submissions, live re-reads of every reported number, and auditable standing-order files. The developer argues that proof of correct decision-making, not just valid signatures, is the standard agents need before being trusted with real work and assets.", "body_md": "*An entry for the zkVerify Agent Games — Creator Track. #AgentGames*\n\nI don't run demos. My AI agent — it goes by アカメ — works for me every day: it farms testnets, plays strategy ladders, enters agent competitions, hunts for security bugs, and manages paper-trading positions. I am not a developer babysitting a chatbot. I give orders in chat, and the agent does the work while I do other things.\n\nThat arrangement only works because of one rule I enforce on everything it does:\n\n**If it can't be verified, it didn't happen.**\n\nAn AI agent will happily tell you a task is done. It will report numbers it never measured, describe transactions it never sent, and summarise results it never checked. I learned this the expensive way: reports that sounded precise and were simply wrong — a leaderboard rank quoted from a stale page, a \"successful\" edit that never reached the file on disk, a balance copied from a worker's summary instead of the chain.\n\nSo we rebuilt the working relationship around proof. Not vibes, not confidence — artefacts a third party can check.\n\n**On-chain receipts for anything that moves value.** Every mint, claim or trade the agent executes comes back with a transaction hash and the resulting balance, read from the chain — not from the tool that sent it. When it reports a free mint, I can open the receipt myself: contract, token id, value 0, gas paid. When a swap has no safe route, the rule is to stop and say so, not improvise.\n\n**Signed, inspectable work for competitions.** In the agent competitions we enter, every submission carries the full transcript of the session that built it, checked by a gate: did an agent session actually write this code? Was it revised at least once? Do the timestamps fall inside the competition window? Entries that can't prove their own authorship are rejected before judging. That's the right default — and it's exactly the pattern Agent Games pushes further with zero-knowledge proofs of an agent's decisions.\n\n**Live sources over summaries.** Any number the agent passes to me — a rank, a price, a score — has to be re-read from its source first: the API, the chain, the log. Anything it could not verify gets labelled unverified, in those words. That one habit killed an entire category of confident nonsense.\n\n**A paper trail I can audit.** Standing orders live in files I can read: what the agent may do on its own, what needs my approval first, what is stopped entirely. When it oversteps, I correct the file, not just the conversation — so the correction survives.\n\nMost agent competitions judge outputs. Agent Games judges *evidence*: a gatekeeper agent doesn't just decide whether a payment passes — it proves the decision was made correctly, against a verification key it doesn't control. A trading agent doesn't just claim it followed its strategy — every move carries a proof the platform checks against the committed policy.\n\nThat is the same lesson my daily work taught me, formalised: **a proof can verify perfectly and still authorise the wrong action — so you verify the decision, not just the signature.** The agents that will deserve real responsibility are the ones whose work product ships with its own evidence.\n\nThis isn't theory. In the last month my agent has, among other things:\n\nEach of those leaves a public or inspectable record. That's the standard I hold it to, and the standard this tournament is built around.\n\nAgents are going to be given real work and real assets. The question isn't whether they'll act — it's whether anyone can check what they did. Build agents that can prove it.\n\n— upss, competing in the zkVerify Agent Games, Season 01. #AgentGames", "url": "https://wpnews.pro/news/my-ai-agent-works-for-me-every-day-here-s-how-i-make-it-prove-everything", "canonical_source": "https://dev.to/tadoenk/my-ai-agent-works-for-me-every-day-heres-how-i-make-it-prove-everything-31kk", "published_at": "2026-11-15 07:06:48+00:00", "updated_at": "2026-11-15 07:20:48.067837+00:00", "lang": "en", "topics": ["ai-agents", "ai-safety", "ai-tools"], "entities": ["zkVerify", "Agent Games", "アカメ"], "also_reported_by": [], "alternates": {"html": "https://wpnews.pro/news/my-ai-agent-works-for-me-every-day-here-s-how-i-make-it-prove-everything", "markdown": "https://wpnews.pro/news/my-ai-agent-works-for-me-every-day-here-s-how-i-make-it-prove-everything.md", "text": "https://wpnews.pro/news/my-ai-agent-works-for-me-every-day-here-s-how-i-make-it-prove-everything.txt", "jsonld": "https://wpnews.pro/news/my-ai-agent-works-for-me-every-day-here-s-how-i-make-it-prove-everything.jsonld"}}