Loops Housenear-ai-guardian

NEAR HACKATHON
Links
Team
1 member- W3Owner
w3-9
Overview
A multisig signer may trust a proposal description or wallet screen even when the executable on-chain action sends funds to a different address or calls a different contract. AI Guardian adds an independent review step before the second signature.
We built a self-hosted AI co-signer for a 2-of-2 Sputnik DAO V2 multisig on NEAR Testnet. The Owner keeps their wallet key and one Council vote; Guardian has a separate local key and the other vote. Transfers and contract calls are real on-chain DAO proposals. The Owner signs a separate statement of intent and a configurable review policy. When review is triggered, Guardian reads the proposal's actual recipient, amount, contract target, method, arguments and deposit from NEAR, verifies the Owner's signed intent, and gathers recent DAO payouts and recipient activity when available. It sends that evidence and the policy to a user-configured AI provider.
The AI returns Approved, Rejected, or Needs user confirmation with a reason. Guardian casts an on-chain approval vote only after an Approved result. If it rejects, the proposal stays pending without Guardian's vote. A matching proposal can receive the Guardian vote, then the Owner's second vote meets the 2-of-2 threshold and executes it.
Our Testnet demo shows a transfer with a changed recipient and amount being rejected, contract-call target and method mismatches being rejected, and a matching transfer approved and executed. The public website is a read-only preview; the live Guardian service runs locally so its signing key and AI API credentials remain with the operator.