Loops HouseSana Guard:Onchain Policy for AI Agents

NEAR HACKATHON
Links
Team
1 member- JUOwner
Jume
Overview
AI agents that hold a raw Solana key can be drained by a leaked key or a prompt injection. A sentence in the prompt is not enforcement.
Sana Guard is a policy-enforced agent wallet. A NEAR contract (guard.djume.testnet) holds per-vault policy and uses NEAR Chain Signatures (MPC, Ed25519) to sign Solana transactions for AI agents only when they pass that policy: per-tx limits, a rolling 24-hour cap, recipient and program allowlists, expiry, idempotency, priority-fee caps, and a kill switch. The agent never holds the Solana private key. Agents call request_sign with a function-call key limited to that method. Owners set policy with a Privy Solana wallet; a relay pays NEAR gas for owner actions and cannot request signatures.
This submission is NEAR testnet and Solana devnet. The live dashboard is https://guard.sana.bot. Vault 0 (https://guard.sana.bot/vaults/0) is public without a login and shows on-chain policy, balance, and the Attack lab. The demo shows a policy-violating transfer blocked on-chain: "Blocked by guard" / SG_E062_PER_TX_LIMIT_EXCEEDED, with no signature produced. A sample MPC-signed devnet transfer is at https://explorer.solana.com/tx/5w6yEG25bVffWMFERM4LF9oJVmtGutZqbC1WrA7bx43UWvEJcCeFueU9xDaYkNrLuRrVkySSjQZcm5FsuBY1CX1r?cluster=devnet.