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
Paste your script's code hash, an address that uses it, or its page on the explorer. We find a real transaction that uses it and try every attack the engine knows on it.
Only the key that published the script can open the report. Anyone else sees that the scan ran, never what it found.
Scans run in order while our engine is on, usually the same day.
- In the queue
- Running
- Done
Open the report
Your key never leaves your machine: you sign a one-time message, we check the signature.
1 · Run this with the key that published the script
How to do this with ckb-cli
Any computer works, as long as the key that published the script is in ckb-cli there.
- Have the key in ckb-cli. Pick what you have:
- Already in ckb-cli on this computer: ckb-cli account list shows the address above. Nothing to do.
- The ckb-cli account file from another computer (in .ckb-cli/keystore there): run ckb-cli account import-keystore --path and the file. It asks for the file's password, then a new one for this computer.
- The private key in a text file: no import. In the command, replace --from-account and the address with --privkey-path and the file's path.
- Paste the command you copied and press Enter. ckb-cli asks for the account's password. The key never leaves the computer.
- Copy the signature. It prints three lines. The one you need starts with signature: 0x. You can paste all three; we pick it out.
path: "" recoverable: true signature: 0x1852...7e3401
No ckb-cli? It is one file: download it for your system from github.com/nervosnetwork/ckb-cli/releases, or use the CCC way below.
Using CCC instead of ckb-cli
Put the private key in KEY and run, in a folder with @ckb-ccc/core installed:
2 · Paste the signature it prints
Open the report with us
This report cannot be opened with a signature here: the script's code sits under a multisig, another script, or a key nobody holds. Ask for it and we check with you that the script is yours, then send you the report.
Not on chain yet?
Nothing uses this script yet, so there is nothing real to replay. Code that is not deployed is where a review helps most: we read it, write the transactions it should allow and refuse, and attack them before you launch.
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.
The report is yours. We do not share it, or anything in it, unless you decide to make it public.
A review covers the scripts, versions and actions we agree in writing, and reports what we found in them. Code changed afterwards, or anything outside that scope, is not covered. It is not a guarantee that the scripts are free of flaws.
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 AI model (Anthropic's API) gets a summary of the case with every hash, address and amount taken out. What the engine learns from a case is a new kind of attack; the case itself stays private.
The list is the engine's own history, newest first.