Loops HousePetty Cash

NEAR HACKATHON
Links
Team
1 member- KEOwner
Kevin Soto
Overview
A community DAO on Sputnik votes on a $40 pizza reimbursement the same way it votes on a $40,000 grant, because Sputnik's approval threshold does not depend on the amount. Organizers wait days to be paid back and the council votes on dozens of small payments.
Petty Cash adds budgets with rules to an existing Sputnik DAO without touching its multisig. The council approves a budget once with a normal proposal: who can spend, cap per payment, cap per period, categories, end date, token. A holder asks for a payment. Inside the rules, the Petty Cash contract files a Transfer proposal on the DAO, approves it with a single-member role that can only add and approve transfers, reads the proposal back, and marks it paid only if the DAO says Approved; the money goes straight from the DAO in a few seconds. Outside the rules, the same proposal is left for a normal council vote with the reason written in it. The contract never holds the budget, and every payment is recorded with its category, memo and DAO proposal, so the monthly report comes from chain data.
NEAR's role: Sputnik DAO keeps custody and approvals; function-call access keys let a holder, or an AI agent, call only spend; named accounts make the report readable.
Live on NEAR testnet with a demo community, Harbor Builders: try a payment and a council vote without a wallet, and run npm run verify to check every payment against the DAO with no keys.