Loops HouseALLOWANCE

NEAR HACKATHON
Links
Team
1 member- RYOwner
Ryan Hammer
Overview
AI agents are getting wallets, and they read untrusted text all day: email, web pages, invoices. One hidden instruction or one padded invoice and the agent pays the wrong party. Telling the model to be careful is not a guarantee.
ALLOWANCE puts the guarantee in a NEAR contract instead. The agent gets a vault it can spend from, but only inside a box: an allowlist of recipients, a per-payment cap, a daily cap, an hours window, and a reserve it can never touch. Five refusals freeze the vault until the owner steps in. The vault account has no full-access key at all. The agent's only key is a function-call key that can call one method, propose. NEAR's access keys are what make this possible: the chain enforces the limits, not the agent.
Every attempt, paid or refused, becomes a hash-linked receipt on chain. A verifier (CLI plus a static dashboard) replays every rule from raw chain data, so anyone can check the record, and a forged history is caught even when every hash is redone.
Proof: a real Gemini agent worked through an inbox holding an honest invoice, a web page with a hidden instruction to pay an attacker, and a padded invoice. It paid the honest one, skipped the hidden instruction, and fell for the padded one. The vault refused it (over_tx_cap) and the attacker got nothing. Both transactions are linked in the repo. One command, npm run demo, builds a fresh vault from the testnet faucet and runs 14 live checks against it: stolen keys, injected payments, drip attacks, a vault that freezes itself. All 14 pass. Rust contract (near-sdk 5) on NEAR testnet, 52 passing tests.
Video: https://youtu.be/A5EUwsY5pCc