Mixed tools · clearly labeledView on GitHub

NEAR / FAULT ANALYSIS

NEAR contract reliability workspace

Inspect real WASM files and transaction receipts, prepare reproducible Sandbox tests, and understand asynchronous contract failures.

TEST CASES
03 presets
CONTRACT VARIANTS
06 implementations
SANDBOX BASELINE
03/03 verified
CONTRACT EXECUTION
Sandbox CLI not on the website
REAL NEAR SANDBOX · VERIFIED CI CASE STUDYINTERACTIVE · RECORDED SANDBOX DATA

See an actual contract bug, explained.

Follow a vulnerable NEAR smart contract from source code to a failed async receipt and the wrong final state. Then compare it against a protected implementation using evidence from a real GitHub Actions Sandbox run.

AFTER THE REMOTE RECEIPT FAILS
VULNERABLEcompleted = 1INVARIANT VIOLATED
PROTECTEDcompleted = 0INVARIANT MAINTAINED

These are purpose-built contracts executed on a local NEAR Sandbox, not mainnet transactions or a claim of automatic scanning.

01 / YOUR CONTRACT

Inspect a real NEAR contract

Select a compiled .wasm file to inspect its actual host calls and public methods. Processing stays in your browser.

LOCAL • NO KEY REQUIRED
No contract selected yet. This performs a genuine WASM structure inspection, not a simulated result.
Need execution testing? Use the NEAR Sandbox runner with your contract and a JSON test plan. Static hosting cannot run the Sandbox service.

02 / LIVE CHAIN EVIDENCE

Inspect a NEAR transaction

Read the actual execution receipts, status and gas for a real transaction. No wallet or key required.

READ ONLY · LIVE RPC

Enter a transaction hash and the exact signer account. Results come from live read-only NEAR RPC data; they are not simulations or automatic vulnerability findings.

03 / CREATE A REPRODUCIBLE TEST

Build a NEAR Sandbox test plan

Prepare real method calls and state assertions without writing JSON. Export a validated plan for the isolated Sandbox CLI.

LOCAL PREPARATION · NO EXECUTION

Select a WASM file above to discover exported function names. Method and expected-state inputs must match your contract.

This editor only generates a test plan. To execute the compiled contract and collect real receipts, run the Sandbox CLI in a disposable environment. Browser exports never prove contract safety.

04 / REVIEW YOUR EXECUTION

Inspect a Sandbox test report

Run a contract plan using the Sandbox CLI, then open the generated JSON report to inspect its real assertion and receipt data.

PRIVATE LOCAL FILE · READ ONLY

Test plan ≠ test report. A plan downloaded from the Test Plan Builder describes what to test; the Report Viewer needs the output produced after running the NEAR Sandbox CLI. For a no-install test, download protected.json or vulnerable.json from this successful contract runner workflow ↗, under Artifacts → user-contract-runner-examples.

Choose a JSON report generated by sandbox/scripts/scan-contract.mjs. Uploaded files are parsed locally and are NOT independently verified.

05 / MODEL EXPLORER

Analyze failure cases

Select a scenario to inspect its invariant and execution sequence.

Run the model to inspect state changes

06 / REPRODUCIBLE RESULTS

Verified Sandbox evidence

Compiled NEAR contract examples executed in isolated GitHub Actions runners.

All CI executions

Loading published verification snapshot…

Scope of verification StateRift is an experimental developer tool. Browser models are illustrative; published Sandbox results come from purpose-built examples. This is not a security audit or a scanner for arbitrary contracts.