Loops HousePROVEN

NEAR HACKATHON
Links
Team
1 member- YAOwner
Yashar
Overview
proven - the NEAR RPC you don't have to trust.
THE PROBLEM Every NEAR app reads the chain through an RPC it does not control: a wallet, an indexer, an agent paying for data. One compromised or buggy endpoint can answer with a transaction that never happened, a balance that is not yours, or a "final" block nobody signed.
NEAR ships the cryptography to stop that - light client proofs - but using it means writing a light client. NEAR's reference implementation is archived, and the spec page for the algorithm is marked out of date and, in the one place that matters, wrong.
WHAT IT IS proven is that missing client: it fetches the proofs and checks them, so every answer carries a verdict instead of an opinion.
- true: committed by a block whose header was signed by more than 2/3 of staked NEAR (self: the header hash was merely recomputed)
- unverified: nothing proven - no proof exists for that method, still pending, or the node refused. Honest, never a pass
- false: the answer contradicts the chain, and the proxy refuses to hand it back
FOUR SURFACES, ONE CORE A library, a CLI, a browser page that verifies inside the tab with no server of ours, and a drop-in verifying JSON-RPC proxy. Point an app at the proxy and change nothing else: the JSON is the upstream's, unchanged, near-api-js keeps working, and the app reads one header.
WHAT IS VERIFIED Transaction outcomes, with every receipt walked from the proven outcome; contract storage, against a trie proof anchored through the block's chunk headers; light client heads. Not verified, and the headers say so: bodies, receipt contents, native balances.
EVIDENCE, ALL AGAINST MAINNET 42 offline tests, 10 live proxy tests, and three tamper demos caught on camera: a rewritten outcome, stripped validator signatures, and a self-consistent forged validator set that only the pinned set exposes.