View the actual CI artifact
The pinned workflow uploaded a protected.json and vulnerable.json test report. Compare those files with this presentation.
A practical sandbox to inspect contract WASM, analyze transaction receipts, and compare vulnerable and protected implementations with real execution evidence.
Recorded example: the vulnerable implementation ended with completed = 1 despite a failed inner receipt.
Verify GitHub CI ↗Go from compiled contract to receipt-level findings without losing the execution context.
Compare state changes against asynchronous execution outcomes.
Illustrative interface preview based on the verified Sandbox case study — not a live analysis result.
Every value below comes from a pinned GitHub Actions Sandbox execution artifact. Choose a contract and step through what actually happened.
See the exact source-code fragment that decides how the contract accounts for a failed remote call.
The state is updated before remote execution is confirmed.
Judge access requires no wallet and no paid service. Download the existing workflow artifact, or rerun the supplied plans in a fresh local NEAR Sandbox.
The pinned workflow uploaded a protected.json and vulnerable.json test report. Compare those files with this presentation.
Build the two contracts and execute each plan with near-workspaces. The first must pass; the vulnerable plan must report an invariant failure.
Reproduction guide ↗The workspace inspects real WASM locally and exports a plan. Actual execution of custom WASM still requires the isolated Sandbox CLI.
Go to contract workspace →cd sandbox npm install --no-audit --no-fund npm run build node scripts/scan-contract.mjs --wasm build/protected.wasm --plan plans/settlement-protected.json --output protected.json node scripts/scan-contract.mjs --wasm build/vulnerable.wasm --plan plans/settlement-vulnerable.json --output vulnerable.json
The vulnerable command intentionally exits with code 1 because its state assertion fails; this is the expected finding in the example.
The reports originate from local NEAR Sandbox contract execution inside GitHub Actions, not NEAR mainnet or NEAR testnet. The hashes in these reports identify sandbox-local transactions, not publicly searchable network transactions. StateRift does not automatically detect unknown vulnerabilities in arbitrary contracts. This is an educational, reproducible failure-analysis case study, not a completed security audit.