snip-36

# SNIP-36 ## Overview SNIP-36 allows executing a single `INVOKE_TXN_V3` off-chain against a reference Starknet block's state, then submitting a stwo-cairo proof on-chain. The proof extends the standard v3 transaction hash by appending a `proof_facts_hash`. Contracts verify this via `get_execution_info_v3_syscall`. **Core value:** Run arbitrary Cairo logic off-chain (heavy computation, privacy checks, game outcomes, attribute proofs) and commit only the verified result on-chain — without revealing private inputs. **Spec:** https://community.starknet.io/t/snip-36-in-protocol-proof-verification/116123 **Reference implementation:** https://github.com/starknet-innovation/snip-36-prover-backend --- ## Quick Start 1. Review the [operator checklist](references/operator-checklist.md). 2. Add a virtual `create_proof` function that emits one L2->L1 message. 3. Prove an unsigned virtual tx with `snip36 prove virtual-os`. 4. Submit `verify_result` with `{ proof, proofFacts }` and the decoded message. ## When to Use - The user asks for SNIP-36, virtual block proving, off-chain Starknet proof generation, or proof-backed on-chain verification. - The workflow needs heavy Cairo computation, privacy-preserving inputs, anonymous voting, secret whitelist checks, or replay-safe nullifier patterns. - The implementation needs a Cairo virtual function, proof server, starknet.js signing flow, and on-chain `verify_result` contract pattern. ## When NOT to Use - The user needs a normal Starkn...