Loops HouseResolve

NEAR HACKATHON
Links
Team
1 member- MAOwner
Manik Nur Hadi
Overview
When a customer pays for a service that is never delivered, the refund lives in three disconnected places: a support ticket, someone's judgement, and a manual payment from a company wallet. Afterwards, nobody can prove which complaint a payout was for, who approved it, or that exactly that amount reached exactly that customer. Letting an AI agent pay refunds on its own is worse: a complaint is untrusted text, and an agent holding a wallet key can be talked into anything.
Resolve is a traceable refund workflow on NEAR where the AI only suggests and money moves only through an on-chain multisig.
- An AI agent triages the complaint and drafts a refund amount and reason. It cannot choose the recipient, and the server caps its amount at the order total and a hard limit.
- A human operator reviews, can lower the amount, then approves or rejects. Every edit recomputes a SHA-256 hash of the exact payload, which is frozen on approval.
- A 2-of-3 Sputnik DAO proposal carries that hash in its description. Two council members vote, and the DAO itself executes the USDC (NEP-141) transfer back to the original payer. Resolve's server holds no private keys.
- Resolve reads the transaction and DAO proposal from NEAR RPC, checks the ft_transfer event (from DAO, to payer, approved amount), and only then marks the case verified. A public /verify page shows the proof without exposing complaint text.
Proof it works: a real refund on NEAR testnet (case RSV-4EY7P6). The AI proposed 1 USDC, the operator edited it to 0.5, two signers approved, and the DAO paid. All three transactions are linked on the live page, and 132 automated tests re-verify the recorded chain evidence. A no-wallet demo is available for judges.
Built for small businesses, online shops and service providers. Made for the Real-World Money track; the AI triage calls the author's existing Samsara Atelier service, everything else was built during the hackathon.