Loops HouseBound Wallet

NEAR HACKATHON
Links
Team
1 member- RAOwner
Rahul
Overview
Bound Wallet is a policy-enforced smart wallet for AI agents on NEAR. The human sets the rules once; the agent cannot exceed them; every decision lands on chain.
The problem: a NEAR function-call key caps gas, not value. Its allowance is checked against prepaid gas and nothing else, so a key scoped to ft_transfer is "limited" by every description NEAR gives it and still moves an entire balance in one call. Agent marketplaces, autonomous treasuries and swarm bids all hand agents funds with no on-chain limit, and the OpenClaw registry compromise showed the harness is not a trust boundary.
Bound is a contract on a named sub-account. Each agent gets a function-call key that can call exactly one method, execute(). The contract then checks per-action and rolling-window caps in NEAR or USD, token, receiver and contract allowlists, rate limits, active hours, expiry, and an approval threshold. Below the threshold the agent is autonomous; above it the action queues for the owner, who approves from a dashboard or Telegram. Denials return instead of panicking, so every allow, deny and approval is a NEP-297 event and a per-agent counter: the raw material for agent reputation. A tripwire suspends an agent that trips repeatedly, and a kill switch pauses everything.
Live on mainnet since day one. A real policy-checked swap moved 1 NEAR to 4.2176 USDC on Base; a cap breach was denied on chain ($12.72 exceeds max_per_tx $10.00); the tripwire fired against a hostile account and suspended the agent, all verifiable in the decision log.
Ships with a TypeScript SDK, a CLI, an owner dashboard, an Agent ID reputation registry, and an MCP server, so Claude Code, Codex, OpenClaw or IronClaw get a wallet they cannot abuse from one config file. x402 is supported pay-then-prove: the payment is made under policy and the receipt proves it, because a sign-then-settle scheme can only ever call a view on the payer and a view cannot decrement a budget.