Loops HouseExit-Proof

NEAR HACKATHON
Links
Team
1 member- MAOwner
Maksim
Overview
Tests and audits check examples. A formal proof covers every input and every order of events, and that is the standard "your money can always be withdrawn" deserves.
Exit Proof makes that guarantee checkable before you deposit. For any NEAR account it reads keys, code and upgrade paths and gives an exit stage: 0, the code can change at once; 1, only after a visible delay; 2, a Lean theorem proves a depositor can always withdraw, bound to the deployed code hash.
Proved on mainnet code: exit from the core staking pool (86.2% of staked NEAR) and from wNEAR; the delay bound of the near-plugins upgrade plugin; and that the NEAR Intents token ledger never credits more than it holds, replayed against 311 697 receipts of the deployed wasm with 0 disagreements.
Certificates sit in a keyless registry on NEAR mainnet. An agent asks over MCP before it deposits; a vault on testnet upgrades only to certified code.
Try it: formalized-si.github.io/exit-proof