Loops HouseSpactVault

NEAR HACKATHON
Team
1 member- ILOwner
ileri
Overview
SpactVault gives an AI agent a budget instead of a wallet. The money sits in a NEAR contract that enforces the owner's rules on chain: payments under an instant limit go through, bigger ones wait until the owner approves that exact payment in their wallet, and anything over the cap or outside the allowlist is refused. The agent's only key is a NEAR function-call key for three vault methods, so a leaked or prompt-injected agent can ask to pay but cannot move funds, change the rules or approve itself. Approvals are bound to a hash of the stored request, so a backend that shows different terms produces a hash the vault rejects. Cross-chain payments go through NEAR Intents 1Click, always need the owner's approval, and bind the deposit address and the final recipient into that hash. On 2026-11-04 it ran on NEAR mainnet: Claude Code, through the project's MCP server, asked for 1 USDC to the owner's Base address, the owner approved in their NEAR wallet, and 0.997398 USDC arrived on Base 38 seconds later (1Click SUCCESS); every transaction is linked in the README. The demo video is a second mainnet run on 2026-11-05: the same flow to Base, then a 5 USDC request refused on chain with HARD_CAP_EXCEEDED, nothing paid. The vault was created from the website and has no access keys, so nobody can change its code. A Security Lab runs 18 attack cases on every commit and publishes the results, 17 of them against a real NEAR node. NEAR pieces: a keyless contract, function-call access keys, sub-accounts, NEP-141 USDC, NEAR Intents 1Click, and NEAR Connect wallets. Live at https://spactvault.xyz. Unaudited prototype; amounts are kept small.