Loops HouseMandate

NEAR HACKATHON
Links
Team
1 member- EHOwner
ehsan hemati
Overview
Mandate lets an AI agent trade a treasury without being able to drain it.
The problem: AI agents are starting to manage real money. An agent that holds keys can be wrong, manipulated or compromised, and nothing stops it.
What we built: the agent never holds a key. It can only propose a trade. A vault contract on NEAR checks every proposal on-chain against the owner's mandate: per-trade cap, daily turnover, asset list, slippage and freshness against oracle prices, position and drawdown limits, an allowlist of models allowed to decide, and a refusal of requests above the market. Only when every check passes does the vault build the exact intent and ask NEAR Chain Signatures to sign it. The owner is a DAO: loosening a rule, admitting a model or withdrawing waits 24 hours; tightening or pausing is immediate; three refused trades halt the agent.
How NEAR fits in: Chain Signatures sign for a keyless vault only after its own checks pass; NEAR Intents settles the signed trade; a Sputnik DAO owns the vault; an admitted Gemini model chooses among quotes the code prices.
Shown on NEAR testnet, every transaction linked: a 1 USDC withdrawal delivered after its full 24-hour delay; a trade settled on both ledgers; 60 USDC refused by a 50 USDC cap; a model admitted through the DAO after 24 hours; a model-decided trade executed and settled. The model's first decision valued $0.50 of NEAR at $50; it never executed, and the agent now refuses such requests.
Limits, stated plainly: testnet only, not audited. The counterparty is our own account, the oracle is a testnet stand-in and the Intents verifier is a fixture build. Mainnet is out of scope.
Site and live dashboard: mandatenear.xyz