Loops HouseSelf-Verifying Smart Contract

NEAR HACKATHON
Links
Team
1 member- ROOwner
Robert Garrison
Overview
Problem: Smart contracts ship buggy code. Audits sample, they don't prove, and deployed contracts can't be recalled. No language makes every function carry a machine-checked proof that travels with the code and is re-checked on execution.
Built: REDΣSIGMA — a self-verifying smart contract language. Write @verified (pre:, post:, invariant:) clauses; they're parsed into the AST and discharged by a tri-state z3 verifier (Proven / Counterexample / Unverified —never a guess). The compiler lowers .redsigma source to real, wasmtime-validated WASM with embedded proof objects, and a NEAR test contract stores, deploys, and executes them. verify/execute_examples.py proves the compiled WASM actually runs correctly (4/4: increment → 1→2→3 with state persisting, 2^64−1 survives as unsigned, counter example off-by-one is real).
How NEAR fits: redsigma.s03-gate.testnet is live on testnet. It parses .redsigma source, runs the full verification pipeline, compiles to WASM, stores the deployed contract with its proof, and executes functions through the runtime with proof re-verification and invariant enforcement (state rolls back on violation). Live:get_contract_count → 1, counter get → 3.