Loops HouseChaperone

NEAR HACKATHON
Team
1 member- GOOwner
Godswill Idolor
Overview
AI agents are getting wallets, and a wallet key is all or nothing. In May 2026 a Morse-code reply on X made Grok and Bankrbot send $150K-$200K to an attacker; AIXBT lost about 55 ETH to two queued prompts. Better prompts do not fix this. Chaperone moves the limits where the model cannot reach them: a NEAR vault contract. The agent holds only a function-call key that can call request_spend on the vault: no deposits, no other contracts. Every request needs an ed25519 verdict from a counterparty risk checker (allow, warn, block; hosted at getchaperone.vercel.app/api) and must pass the owner's rules on-chain: per-payment cap, daily budget per agent, recipient allowlist, timelock for new recipients. Warn-band payments wait for the owner's wallet approval; revoke_all removes every agent key in one call. The vault account holds no full-access key: the deployer key was deleted and upgrades go through an owner-only method. With NEAR AI Cloud, the agent refuses to act unless the model's Intel TDX attestation binds a fresh nonce. Live on testnet (chaperone.testnet): a prompt-injected invoice tries to send 500 USDC and is refused with 11 reason codes; a forged verdict is refused; a real model resisted and the vault refused the fooled path anyway; the owner approved a held 16 USDC payment from the dashboard (getchaperone.vercel.app). Also: agent swaps through NEAR Intents under the same policy, an MCP server so any agent can use a Chaperone wallet, and a no-keys reproduction with pnpm demo:dry.