Loops HouseKey Doctor

NEAR HACKATHON
Team
1 member- TROwner
TranTu
Overview
Key Doctor helps a Sputnik DAO council protect, spend and grow its shared fund. Every money move stays a DAO proposal that members sign in their own wallets.
The problem: on NEAR mainnet, 80% of active Sputnik DAOs let one account approve a transfer, and half of their council members rate high risk. A takeover usually adds a new full-access key and then votes on a payout. A council that wants an AI agent to pay must give it a key that can spend everything, or vote on every small payment.
-
Protect. Key Doctor scores every key of every council member with fixed rules. On Call warns the council's Telegram before the final vote when a voter has a new full-access key, and it flags member, policy and code changes. The dashboard gives a cleanup plan: revoke or delete risky keys.
-
Agent Budget. Two signatures create a budget for an AI agent. A Guard contract joins the DAO and approves the agent's payments only within the per-payment, per-recipient and 24-hour limits the DAO set. Anything else waits for the owner, and Telegram reports it. Scheduled payouts and DCA on Rhea run as Guard plans. An unprivileged keeper triggers due steps. Agents connect through MCP and can run a preflight before they pay.
-
Yield. Rhea Lend rates for the DAO's idle stablecoins, capped at the free balance, shown next to the council's key status. The dashboard builds the supply and withdraw proposals, and the council votes. An optional TEE model on NEAR AI Cloud orders the code-built suggestions; code checks every number.
How NEAR fits: keys, their permissions and when they were added are public on chain, and so are Sputnik votes, so we link a new key to a vote with no indexer. A function-call key lets the agent call only the Guard. NEP-591 global contracts cut a budget's Guard storage from 3.6 to 0.01 NEAR.
Protect works on mainnet and testnet, including key cleanup signed in your wallet. Agent Budget and Yield proposals are testnet only for now.