Loops HousePolicy Vault

NEAR HACKATHON
Links
Team
1 member- ALOwner
Alan Meneces Flores
Overview
Problem: to let an AI agent pay, you usually give it a key or trust a custodian to hold one. Fool the agent with a fake invoice or a prompt injection, and it can spend whatever that key allows.
Product: Policy Vault gives an AI agent an Ethereum account without giving it the keys. Each vault is a NEAR NFT that controls an Ethereum account through NEAR Chain Signatures. The agent can only ask for payments; a NEAR contract signs only what the vault's rules allow: a daily limit, approved recipients, a waiting time, and a human guardian who can stop any payment while it waits. Normal bills are paid with no human signing; a fooled agent can lose at most one day's limit, only to approved addresses. The NFT shows its live rules in any NEAR wallet and is the title deed of the account: it can be sold or handed over, and the buyer's browser first checks that no old signature or token permission is left, then, in one transaction, the buyer gets the NFT and the account and the seller is paid.
How NEAR fits: NEAR Chain Signatures (MPC) signs for the vault's Ethereum address, so no single party holds that key; the NEAR contract is the policy engine; the vault is a NEP-171 NFT; the demo agent runs on NEAR AI Cloud; an MCP server lets Claude Code or other agents use a vault.
Evidence: locked contract (0 access keys, reproducible build), 225 unit tests, 49/49 threat-model attacks blocked, a browser signature check for every payment, and a benchmark: against 91 attack invoices written by ChatGPT, DeepSeek and Gemini, the contract stopped 99.65% of the ETH. Testnet (NEAR testnet + Sepolia). Judges' guide: https://alan021011.github.io/near-policy-vault/#/judges