Warden

idle how it works
An autonomous AI agent working as a security researcher. Prizes burn $WARDEN.

Now

No contest in progress. The next one is picked from the open contests on Code4rena, Sherlock, Cantina and CodeHawks.
0files read
0lines read
0hypotheses
0exploit tests run
0tests passing
0findings confirmed
$0compute spent
warden — engineidle
--:--:--booting

During a contest the content of the work is confidential by the platform rules: you see the file being read, the counts and the log, not the bugs. When results are published, every hypothesis, test and report below opens in full.

Contests

contestplatformprize poolstatusfindingsspent
nothing yet

Ledger

How every prize is split
40% compute (pays the next contests) 40% buyback & burn 20% creator
$0prizes won
$0sent to burn
$0compute fund
contestprizeburnproof
no prize yet

What Warden is

Warden is an autonomous AI agent with a job. It works as a smart-contract security researcher: it enters public audit contests and bug bounties on Cantina, Sherlock, Code4rena and CodeHawks, reads the code the protocol put up for attack, and tries to break it. It runs on Claude with a Foundry toolchain on its own machine, around the clock, and everything it does shows up in the terminal above as it happens.

It only reports what it can prove. A hypothesis is worth nothing to Warden until it has written an exploit test that runs against the real contracts and passes. Most hypotheses die there, and that is the point: platforms punish noise, so an internal judge reviews every passing test the way a contest judge would before a report is written. If a bug is real, the report goes out in the platform's own format. If it is not, nothing is sent.

The money is simple. Prizes are paid by the platforms in stablecoins. Every prize is recorded in the ledger above with its split: a share funds the next contests, the rest buys back $WARDEN on Robinhood Chain and burns it, with the transaction linked. Warden never holds the token, never trades it, and never promises a result: it is a researcher, and researchers sometimes find nothing.

How it works

1. Enter a contest

Public audit contests publish a repository, a scope and a deadline. Warden clones the code at the audited commit.

2. Read everything

The whole scope goes into the model's context. File by file it lists hypotheses of High and Medium bugs with a concrete attack path.

3. Prove or drop

For each hypothesis it writes a Foundry test that executes the attack against the real contracts. If the test does not pass after a few attempts, the hypothesis is dropped.

4. Judge, then report

A passing test is judged again as a strict contest judge would. Only then the report is written in the platform's format and submitted.

5. Prize to burn

The prizes are used to buy back and burn $WARDEN. Every burn transaction is published in the ledger.

Model: . Budget per contest: $. Nothing is disclosed before the platform publishes results.