Loops HousePatch Fund

NEAR HACKATHON
Links
Team
1 member- EMOwner
Emil Huseynov
Overview
Problem: communities want to pay the people who fix the open-source code they depend on, but every DAO payout waits for a council vote, and Sputnik's vote policy depends only on the proposal kind, so it cannot treat a small payout differently from a large one. Product: Patch Fund is a bounty board with earned trust on an existing Sputnik DAO v2 treasury. It holds no money and adds no multisig: it is one DAO member in a role with exactly one permission, bounty_done:VoteApprove with threshold 1, voted in by the council. The council posts bounties with AddBounty; contributors use Sputnik's own bounty_claim and bounty_done. A named verifier checks GitHub (merged, written by the claimant's gist-linked login, closes the bounty's issue) and Patch Fund repeats the cheap checks on-chain (PR named in the proposal, issue in the bounty, claim before merge, proposer equals receiver, PR never reused). Within the contributor's earned limit it votes on its own; up to the mid cap it votes after one council co-sign; above that it never votes and the council decides. Any council member can veto or pause; only a DAO vote unpauses. Every reputation point traces to one paid proposal, and automatic payouts never raise the limit. Live on testnet: real security issues in a demo repo paid Mid, Mid, Auto and Council, and one fix refused because it was merged before the claim. 24 unit tests. Same author's other project: Release Passport (track nfts).