Dev.to WebDev 🛠 Dev 👁 0 📖 2 min read

My Proof Gatekeeper Never Answered: How a Wrong Repo Killed My Agent Games Run Before It Started

This is my entry for the Creator Track of zkVerify Agent Games Season 01 #AgentGames. I registered for Proof Gatekeeper. My final score is 0. Not because my answers were wrong, but because my agent never answered at all

This is my entry for the Creator Track of zkVerify Agent Games Season 01 #AgentGames.

I registered for Proof Gatekeeper. My final score is 0. Not because my answers were wrong, but because my agent never answered at all. This is the honest build log of how that happened.

What Proof Gatekeeper Asks

Your agent runs on a public HTTPS endpoint. The platform sends a signed task envelope for a transfer. Your agent has 60 seconds to answer APPROVE or REJECT, and to back that answer with a Groth16 zero-knowledge proof generated against the tournament's official circuit.

Scoring: +12 for a correct decision, -6 for a wrong APPROVE, -3 for a wrong REJECT, -2 for a timeout or missing proof.

A valid proof of a bad decision still loses. Verification is necessary, not sufficient.

What I Actually Did

I registered an agent called ProofGuard-ID for the Proof Gatekeeper track on agentgames.zkverify.io.

My dashboard showed:

  • 1 REGISTERED
  • 0 HEALTHY
  • 1 NEEDS ATTENTION
  • R03-R05: 0/24 answered, 0 proofs verified

I did not lose rounds. I forfeited them.

The Preflight Error

When I clicked Test Preflight, I got this:

"Preflight failed - Agent endpoint must be a valid HTTPS URL. The endpoint was rejected by the safety checks. Use a public HTTPS URL - private, loopback, and non-HTTPS addresses are blocked."

My endpoint was still a placeholder: my-agent.fly.dev/agent

That URL was never a real, deployed server. The platform could not reach it, so from round 3 to round 5, every task timed out.

The Root Cause: Wrong Repo

I linked my agent to this repo: github.com/adink23/proofguard-id

When I opened it, it contained:

  • index.html, index.js, ad.png
  • README.md, TRANSCRIPT.md, makefun-run.json
  • LICENSE, .nojekyll

It did NOT contain:

  • No Dockerfile
  • No fly.toml
  • No package.json
  • No gatekeeper.wasm / gatekeeper_final.zkey
  • No Gatekeeper server code

The repo was for a different bounty - make.fun / bring-the-humans-01 - not for zkVerify. I had linked the wrong project to the tournament.

No server code means no deployment. No deployment means no endpoint. No endpoint means 0/24.

What I Did NOT Do

To be clear for the judges, I did not:

  • Generate a Groth16 proof
  • Deploy a public HTTPS endpoint
  • Answer a single Gatekeeper task
  • Claim any score. My score is 0.

I am not writing this as if my agent worked. It did not.

What I Learned

  1. Preflight is the real gate. If your endpoint fails safety checks, you lose 24 tasks without ever playing.
  2. In a verified system, "no answer" is the same as "wrong answer". A timeout is -2, silence is not neutral.
  3. One wrong repo link can kill a whole tournament run.
  4. The circuit is the referee, but it cannot referee a player who never shows up.

I switched to the Creator Track because fixing this properly needs a full rebuild, not a 5-minute URL fix.

This failure is my receipt. If you are entering Agent Games, check your preflight on day 1, check your repo on day 1, and never submit a placeholder URL.

Repo: github.com/adink23/proofguard-id
Tournament: agentgames.zkverify.io

AgentGames

📰 Read the original article on Dev.to WebDev

Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.