Loops HouseMergePay

NEAR HACKATHON
Links
Team
1 member- MOOwner
Mohamed Aaftaab
Overview
MergePay pays developers for the work that was actually accepted: the merged pull request. A company funds a pool for its GitHub repository. When a PR with a pay label merges, a pinned GitHub Actions workflow asks GitHub for an OIDC token naming the PR, its author and the repository, and submits it to a NEAR contract. The contract verifies GitHub's RS256 signature on-chain in Rust (about 27 TGas, within NEAR's 300 TGas limit). It also checks the issuer, repository, pinned workflow, event, pool cap and expiry, and that the PR hasn't been paid before. It then pays the NEAR account the author linked with their own GitHub-signed token. New GitHub keys wait 48 hours before the contract trusts them, and a daily workflow confirms the contract trusts every key GitHub signs with. The operator console is a static site with no backend: every figure is read from the contract and public NEAR services, and the Proof page re-verifies any payout's GitHub signature in the browser with WebCrypto. Bookkeepers get a monthly statement and a CSV tied to transactions. Live on NEAR testnet with real payouts for merged PRs; wNEAR stands in for USDC.