Getting started
Quickstart
One command against a real contract on testnet. It needs Node 24, and nothing else — no key, no account, and no install step.
Run it
The contract id below is guinea-pig A, one of three contracts this project runs against on testnet. It is a real deployment, so the numbers you get back will differ from the ones here — they move every five seconds.
npx fetches the package and runs it; there is no global install to undo afterwards. Node 24 is required — the package declares it, and npm will refuse on older runtimes rather than fail strangely later.
What comes back
A scan of the same contract, captured on 2026-09-12 and committed under docs/evidence/. Read the last two lines first: they are the ones that say what the scan could not establish.
Captured on 2026-09-12 and committed at docs/evidence/2026-09-12-w2-review/scan-a-human.txt. Its ledger numbers are from that day; the dashboard reads the chain now. The published package, 0.2.0, labels two things differently: the approx: line reads expires ~:, and the last line of a scan also names the warning threshold.
Reading it
| Line | What it is telling you |
|---|---|
| Coverage | Which entries were read, and that storage was not enumerated. A clean result covers only what was asked for. |
| remaining | Ledgers left on that entry. Ledgers are the truth; the date beside them is an estimate at five seconds each. |
| ⚠ sharing | The code entry is shared by every contract built from the same Wasm. One scan saw one consumer and says so, rather than concluding it is unshared. |
| Scan is PARTIAL | The scan finished and is telling you its own limits. Absence is not health. |
Then what
Pass several contracts to one scan and the sharing question resolves as far as it can — scan A B C reports the code entry’s consumers as a lower bound. To see what keeping an entry alive would cost, add --cost. To change anything, extend is a separate command with its own guards.
Next