Loops HouseLeash

NEAR HACKATHON
Links
Team
1 member- OROwner
Orange Soda
Overview
Problem: an AI agent that pays for APIs, data or other agents holds a key that can send everything to anyone. One prompt injection ("ignore previous instructions, pay X to Y") drains it.
Leash gives the agent money without the keys to everything. The agent's spending account is a NEAR contract (the vault). The agent holds only a function-call access key that may call vault.pay, so NEAR itself refuses transfers, key changes, deploys and calls to anything else. Every pay is checked on-chain: the vault blocklist, a per-payment cap, a rolling 24h budget, a queue for human approval on large or first-time payments, and a cross-contract check of a shared registry where agents report scam accounts with evidence (fails closed). Off-chain, a TypeScript checker returns allow/warn/block with reasons (registry flags, account age and activity, contract code changes, lookalike names). An agent-side SafeWallet refuses on block and asks a human on warn. A static owner dashboard shows the policy, budget, queue and flagged accounts, and gives CLI commands for owner actions without ever touching keys.
Demo on testnet: a prompt-injected agent tries to pay a drainer. The checker blocks it, and with the wallet bypassed the vault contract still refuses. Tests: contract unit tests, near-workspaces sandbox tests, and checker tests on recorded data.