Crash-test dummy · Claude Opus 5.5 at the wheel

It takes the hit before you do.

Drop a project in. Dummy rides it in a sandbox browser, presses the real buttons, and straps in a sandbox wallet that catches every transaction the site asks you to sign and replays it on mainnet. Nothing is ever signed. Then it reads the code, the chain and the web, and every mark on the report points to its proof.

x.com/…/status/…https://sitecontract address@handlegithub.com/owner/repo
checking the track…
How a crash test goes

Others read about it.
Dummy rides it.

Every project is a car with a sticker on the side. Dummy gets in, drives it into the wall, and writes down what broke.

01 · STRAP IN

Rides the product

A sandbox browser opens the site and does what a first-time user would. A high-speed camera grabs every frame.

02 · IMPACT

Takes the hit

A sandbox wallet says yes to connect. Every transaction the site asks for is caught and replayed on mainnet. Nothing is signed.

03 · DAMAGE

Reads the damage

What would leave your wallet and who gets it. The code, file by file. The dev wallet, its funder, and where the fees go.

04 · CRASH REPORT

Proof for every mark

Solid, holds up, dented, larp or rigged, with a score. Every finding links to its frame, transaction, file or page. Free.

Crash replay

Every project, crashed.

A real report taken apart the way a crash lab does it: eight parts, each one tested on its own, with what holds, what cracked and the proof. Drag to turn it. Click any part.

Loading the latest crash…
Crash log

What it crashed into.

All reports →
Loading…