Loops HousePenny

NEAR HACKATHON
Links
Team
1 member- TOOwner
Tobiloba Omotade
Overview
Agents like Grok Bot and Muse have already shown that people will let software take actions. The hard part is no longer capability. It is permission. The moment an agent can move money, send mail, or act in your name, you are asked to connect an account, hand over a session, or grant a scope you cannot inspect. For money, the choice is usually custody or nothing.
Penny started with a different question: what is the smallest amount of power an agent needs to do this one thing, and how do we prove the user approved exactly that? Penny is a crew of agents in iMessage. You text it like a friend: pay a bill, send Ada $20, put $50 somewhere safer, remind me to call mum. Penny routes the work to a specialist. The agent gets its own NEAR account, not yours. The key stays on your iPhone behind Face ID, or in your browser as a passkey. Every action becomes one card in the thread. Guard checks the plan before the card and again before relay, with per-agent budgets, caps, allowlists, expiry and revocation. The server verifies the signed action byte for byte before it relays. If Guard says no, no approval card is ever sent. Text freeze and every trusted key, card and passkey is switched off.
Penny lives in iMessage because that is where the request already happens, but iMessage is the surface, not the trust boundary. NEAR is the action layer: named accounts per user and agent, NEP-366 delegate actions so the phone signs and a relayer pays gas, a locked Guard contract for spending policy, and NEAR Intents for cross-chain swaps. Inference runs on NEAR AI Cloud with TEE attestation enforced. The demo runs on testnet with test funds. The Guard, cards, signatures and receipts are real; mainnet relay is off.