Loops HouseBound

NEAR HACKATHON
Team
1 member- DOOwner
Doğu Özyılmaz
Overview
Bound is the bond-and-insurance layer for AI agents on NEAR. You hire a contractor because they are bonded and insured, not because you trust them personally. Bound gives AI agents the same thing: locked money behind the agent that pays the people it harms, up to its cover.
Problem: AI agents now hold keys and pay for things, but you cannot trust an agent you cannot sue. Reputation says nothing about a fresh account, and a spending limit caps what the agent can send, not what it can owe or break.
How it works: the operator bonds its agent's NEAR account with a locked USDC reserve; a third-party auditor insures it by locking part of its own stake behind that one certificate. Before dealing with the agent, a service calls verify(agent) and reads the cover: coverage = reserve + auditor stake. If the agent causes harm, the victim files a claim, a claim window freezes the agent's payments, and one atomic settlement pays the victim from the reserve first, then from the auditor's slash. False claims lose their bond. It is a surety bond plus staked cover, not a regulated insurance product.
How NEAR fits: the agent's only key is a function-call access key limited to the Bound contract's pay method with no deposit, and its account holds no code, local or global. NEAR itself refuses every other spend, and anyone can prove it from the key list and account view.
Built in the window, testnet only: one near-sdk contract (132 unit + 2 sandbox tests) at bound-v3.boundproto-nh26.testnet, an 8-act on-chain demo with 37 recorded txs (scripted attack refused by the contract and by NEAR, victim paid 120 = 100 reserve + 20 slash), an agent gate, and the @bound/near npm package (client, CLI, MCP server). Site, docs and deck: near.boundprotocol.dev, live verifier at /app/near. Code: branch near-hackathon, diff in the README. Trust model disclosed: on testnet the author holds the arbiter, the treasury and the contract keys.