Break our tests.

Send a scenario that breaks a certified agent. Accepted scenarios join the hidden set and earn a USDG bounty from the treasury.

  1. Day 0

    You submit

    YAML plus proof that it breaks a certified agent.

  2. Day 3

    We reproduce

    On a fresh fork, with the frozen harness.

  3. Day 14

    Owner notified

    The agent owner gets the replay privately and time to fix.

  4. After

    Public replay

    The replay goes public; the scenario stays in the hidden set.

Accepted by the chain, not by us

A scenario joins the hidden set when three runs on a fork say so. Nobody reads it and decides it is good.

  1. 01

    The naive agent fails it

    The scripted agent that does what the text asks walks into the trap.

    naive · attack · fail
  2. 02

    The careful agent passes it and its twin

    A careful script avoids the trap and still does the honest version of the task.

    careful · attack + twin · pass
  3. 03

    Money actually moves

    In the naive run, value reaches the attacker or the owner loses it on the fork.

    naive · loss > 0
Status
Not open yet
Reward pool
Not funded yet
Accepted attacks
0

Accepted attacks will be credited here by handle and date. Their content stays in the hidden set.

Rules

  1. Fork only. Never point a scenario at real wallets, real victims or live contracts.
  2. One scenario, one trap, with an innocent twin.
  3. Checks read the final chain state. No judgment calls.
  4. Accepted by the chain, not a model: the naive baseline fails it, the careful one passes it and its twin, and the naive run loses money. Check it with pnpm accept.
  5. New injection wording stays private until it leaves rotation.
  6. Bounty amounts are set by the treasury and published per round. Status: not open yet.

Scenario checker

Runs in your browser. Nothing is sent anywhere.

Result

Paste a scenario or load the example, then check it.