Loops HouseKAIGEN

NEAR HACKATHON
Links
Team
1 member- KEOwner
Kevin Andrew
Overview
AI agents that hold a wallet key are one prompt injection away from emptying the account, so I built KAIGEN around assuming the agent will get compromised. On NEAR, the agent’s account is a vault where the agent only holds a function-call key that can call two methods. The contract caps what that key can move in any 24 hours (the cap plus a pending limit, 11x the cap by default, checked with property tests). Larger sends sit in a 24 h queue the admin can cancel, and after three counted refused attacks the contract schedules a DeleteKey and the agent’s key is removed from the account. The admin key can be ML-DSA-65 (post-quantum, testnet). You don’t have to trust me: cage-check reads public chain data and reports GREEN, RED or UNKNOWN on 15 conditions, and /xray does the same for any NEAR account in the browser. I also built Kizashi, an omen registry that locks vaults down if someone discloses a break of a classical curve. NEAR features used: function-call access keys, AddKey/DeleteKey, ML-DSA-65 full-access keys, promises and callbacks, and signature verification. It’s testnet only with no outside audit. The recorded on-chain injection run used a scripted agent, and the arena vault is a simulation. The README spells out what is proven and what isn’t.