Loops HouseGhostcount

NEAR HACKATHON
Links
Team
1 member- AUOwner
Austin Spraggins
Overview
Live: https://spragginsdesigns.github.io/ghostcount/ (one click runs the check in your browser)
Problem: NEAR Intents keeps every user balance in one contract, intents.near. From 29 Sep to 1 Oct 2026 a bookkeeping bug let an attacker create $3.8M of balances with nothing behind them. The post-mortem says the team did not monitor what users were owed against what the contract held. Nobody outside could check either.
What we built: Ghostcount, a read-only backing check anyone can run. For every token in intents.near it compares what users are owed (mt_supply) with what the contract holds on the token contract, at any block. A dashboard shows every chart with the calls behind it, a button runs the check live against public mainnet RPC, and one command rebuilds every number. Results are posted every six hours to a contract on NEAR testnet, so other contracts can read is_backed_at_or_after(block).
Findings: replayed on archival blocks, the check fails at block 217,799,506, 39.8 hours before the team identified the problem, and finds 23 steps in the hole, each matched to one transaction (the post-mortem counts 23 failing deposits). At eight moments over every priced token, and daily for 737 days over the 20 largest liabilities, it fires only on that token, only during the incident. Tested claim: once the hole closed, the money outside wNEAR was back in 4.2 days; counted with wNEAR it was not, and we say so.
Thesis: large money will route through NEAR Intents only if it can check the backing itself. On 11 Nov the inner ledger was backed ($227.7M owed, $0 unbacked), but 63.6% of it is bridged tokens (PoA Bridge, HOT Omni) whose reserves cannot be checked from public data. That share is the number to watch.
How NEAR fits: deterministic view calls at any archival height and NEP-245 enumeration allow an operator-independent audit with no indexer. It reads intents.near, the 1Click API, HOT Omni, Chain Signatures' v1.signer (nBTC reserves) and Sputnik DAO policy.