CKB script review
Attack your script before someone else does.
Give us the code hash of a lock or type script on CKB. We take a real transaction that uses it and try thousands of changes an attacker could make: moving value, swapping cells, editing witnesses, faking proofs. You see which ones your script let through.
01 · Free
Automatic scan
For any script already used on mainnet or testnet. The result is shown only to the key that holds the script's code.
Start a scan02 · By our team
Manual review
For scripts not deployed yet, types with their own rules, multisig owners, or a full report. We read the code and write the attacks for it.
Ask for a review03 · Always on
It keeps learning
Every case teaches the engine. AI agents study what it could not judge and propose new attacks; each one is proven on test scripts before it joins.
See what it learnedAutomatic scan
The engine runs on our machines and is not public. Scans run in turn, and one can take several minutes. The queue moves when our engine host is on, usually within a day.
Anyone can start a scan of any script, but only the owner sees what it found. Everyone else sees how many attacks were tried, never the result.
Scan
See the result
Sign this message with the CKB key that holds the script's code. Your key never leaves your machine.
How to sign it
With Node and @ckb-ccc/core installed, put the key in KEY and run:
The code of this script is held by a lock that cannot sign a message, such as a multisig or another script. Ask for a manual review and we will check that you own it.
Manual review
We read your code, write the honest transactions and the rules your script must keep, and run the engine with them. You get a report and, for each problem, a test that shows it and passes once it is fixed.
We answer by email with what we would look at, how long it takes and the price.
How it learns
Every scan is kept as a case. When the engine cannot replay a transaction, or finds something it cannot judge, we study the case with AI agents, write the missing attack or setting, and prove it on test scripts built with and without the flaw before it joins the engine.
The list is the engine's own history, newest first.