Loops HouseBACKED

NEAR HACKATHON
Links
Team
1 member- ROOwner
Rohan Kumar
Overview
Backed is proof of backing for NEAR protocols. It checks, from public chain state, that a protocol holds every token its own books say it owes, and it gives developers a Rust library that stops the bug that breaks this.
The problem: on NEAR, calls between contracts are asynchronous and nothing rolls back on its own. When a callback fails or trusts a reported amount, a contract's ledger can record tokens it does not hold. That one bug family caused three 2026 incidents worth over $22M: NEAR Intents ($3.8M, a resolve callback that failed on the log limit), Rhea Finance ($18.4M, crediting a claimed swap output instead of what arrived) and the SWEAT/HOT zero-day (a public refund callback). After the Intents exploit, NEAR engineers checked the damage with a one-off script.
What we built:
- A live check of every NEP-141 token in intents.near: owed (mt_supply) vs held (ft_balance_of), read at the same block so in-flight transfers cannot skew it. It runs daily with history and alerts. On Nov 9, 380 of 387 tokens were backed and 2 under-backed. We traced each gap to a transaction: two memecoins charge a sell tax and report it as refunded, and Intents credits a refund that never arrived.
- The backed library for near-sdk contracts: balances grow only from delivered amounts, callbacks are private and cannot panic, refunds are capped, and owed <= held is asserted on every change.
- A sandbox harness that replays all three attacks: the naive vault loses money, the Backed vault does not. It runs in CI.
- A checker contract that records backing on-chain with no trusted reporter, live on testnet and ready for mainnet.
- A web app, a CLI, a hosted MCP server in the official MCP Registry so AI agents check before they deposit, an agent skill, and a draft NEP for a standard backed_solvency view.
NEAR fit: the bug only exists because of NEAR's async model, and the check is trustless because both numbers are readable on NEAR at one block height.