StateRift RECEIPT INTELLIGENCE
BUILT FOR NEAR

Trace, analyze, and verify NEAR contract behavior.

A practical sandbox to inspect contract WASM, analyze transaction receipts, and compare vulnerable and protected implementations with real execution evidence.

NEAR SANDBOX RESULT
Failed inner receipt1
Protected completed0

Recorded example: the vulnerable implementation ended with completed = 1 despite a failed inner receipt.

Verify GitHub CI ↗
THE WORKSPACE / AT A GLANCE

Security evidence, made readable.

Go from compiled contract to receipt-level findings without losing the execution context.

Explore the workspace
STATERIFT / ANALYSIS OVERVIEWWORKFLOW PREVIEW
ANALYSIS TOOLS
◇ Contract inspector
▤ Transaction receipts
⬡ Fault models
⌘ Test plans
NEAR / SANDBOX
VERIFIED EXECUTION EXAMPLE

Receipt integrity analysis

Compare state changes against asynchronous execution outcomes.

Evidence backed
INNER RECEIPTFailedAsynchronous execution
VULNERABLE STATE1Completed despite failure
PROTECTED STATE0Invariant preserved
EXECUTION TRACE01 — 03
01Contract call dispatchedPASS
02Inner receipt executionFAILED
03Protected state invariantHELD

Illustrative interface preview based on the verified Sandbox case study — not a live analysis result.

POWERED BY NEAR
EnvironmentIsolated NEAR Sandbox
EvidenceGitHub Actions artifact
MechanismAsynchronous receipt failure
Security claimPurpose-built examples only
01 / INTERACTIVE EVIDENCE

Follow the failure, not the hype.

Every value below comes from a pinned GitHub Actions Sandbox execution artifact. Choose a contract and step through what actually happened.

Loading CI evidence…
SELECT IMPLEMENTATION
STEP 01 / 03

The state mutation

See the exact source-code fragment that decides how the contract accounts for a failed remote call.

VULNERABLE CONTRACT
Loading real code excerpt…
What matters

The state is updated before remote execution is confirmed.

1 of 3
02 / INDEPENDENT REPRODUCTION

Don't trust a screenshot. Reproduce the result.

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.

01

View the actual CI artifact

The pinned workflow uploaded a protected.json and vulnerable.json test report. Compare those files with this presentation.

Open source workflow ↗
02

Repeat the experiment

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 ↗
03

Use your own compiled contract

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 →
RUN TESTS LOCALLY · FROM REPO ROOT
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.

Scope of evidence

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.