Loops HouseIntents Watchtower

NEAR HACKATHON
Links
Team
1 member- SHOwner
Shekwolo
Overview
Problem: On 1 October 2026, about $3.8M left NEAR Intents through a bridge without a corresponding deposit. Users had no way to see the shortfall as it happened. A bridge should hold one coin for every token it issues, but users, apps and AI agents cannot check that backing before sending funds.
Product: Intents Watchtower monitors bridge backing for NEAR Intents. Every minute, three independent watchers compare token supply on NEAR with bridge treasuries on Bitcoin, Ethereum, Solana, BNB Chain and Litecoin. If tokens are issued without backing, or reserves fall short, the route turns red. Each signed verdict includes a safe transaction size, so callers can check how much they can send. The product includes a public status page in eleven languages, a TypeScript SDK and an MCP server that lets AI agents check before spending.
How NEAR fits: The watchers submit signed verdicts to a NEAR smart contract written in Rust. The contract verifies signatures and requires a quorum to mark a route safe. It raises alarms quickly and requires stronger confirmation before clearing them. Wallets, apps and agents can query is_safe(route) and check_intent(route, amount) through free view calls. One honest watcher can raise an alarm; a dishonest watcher cannot clear it alone.
Current status: Intents Watchtower is live at intentswatchtower.xyz, using mainnet data with its verdict contract deployed on NEAR testnet. Checks against the official treasury list show five of seven bridged assets as fully backed. Bitcoin and Litecoin are marked partly verified because published treasury balances are slightly below token supply. In a replay of the October incident pattern, the affected route turns red four minutes after the first unbacked credit, with 97.6% of the funds still to move.