Loops HousePolicy Signer

NEAR HACKATHON
Links
Team
1 member- ALOwner
Ali Hazar
Overview
Policy Signer gives an AI agent a budget, not a wallet key: it pays alone below a limit and asks its owner above it. A prompt injection can make a key-holding agent send everything.
Via Chain Signatures a keyless NEAR contract controls the agent's EVM address; only that contract can request signatures for it. The agent's only key is a NEAR function-call key for one method, request: token, recipient, amount, fees within caps; never calldata. The contract builds the exact transaction, checks it against the owner's policy (allowlists; caps per transfer, day and agent; fee caps), then asks the NEAR MPC network to sign. The payload signed is the payload checked.
Outside the policy: refused with a named reason, logged on chain, nothing signed. Above a soft limit, or to a new recipient where allowed: queued until the owner approves that one transfer in a NEAR wallet. Same first and last four hex digits as an allowlisted recipient: refused as a look-alike, never queued.
The owner, one NEAR account, is the root of trust; its key can replace the code only after a public 48-hour notice. Policy and ownership changes wait 1 hour and can be cancelled: against a takeover of the owner account, that is detection, not recovery. Pause, removals and ticket approvals stay immediate.
Live on NEAR testnet, signing native ETH on Robinhood Chain testnet: transfers signed, one after owner approval; a staged hijack (own check skipped) refused on chain over the cap, to a look-alike and while paused; upgraded through its timelock; a delayed change scheduled and cancelled; a second agent added through the delay. Planner: rules; NEAR AI Cloud planner mock-tested. Unit-tested only: ERC-20 and Stock Token kinds. Testnet only, not audited.
Verify without keys: cargo test (100), a sandbox test of request, MPC sign and callback, agent npm test (36), read-only previews of the live contract (README).