Loops HouseEarnPatch

NEAR HACKATHON
Links
Team
1 member- CHOwner
Chizaram Chukwuka
Overview
The problem: Software improvements are often commissioned as one-off jobs. Merchants take the funding risk, developers receive little upside when a feature keeps generating revenue, and customers have limited influence over what gets built. Unlimited revenue-sharing agreements can create a different problem: obligations that never end.
What I built: EarnPatch is a working marketplace that links merchants, developers and customers around a single software upgrade. A merchant commissions a feature with acceptance criteria and capped royalty terms; a developer accepts, delivers and earns from qualifying uses after approval; customers purchase access to the finished feature. My SafeShare Export example actually protects CSV files and produces downloadable, spreadsheet-safe reports. I demonstrate it both in EarnPatch and inside Paperlane, an independent reporting app connected through EarnPatch Bridge. Finance adds customer-backed development commitments, conditional release/refunds and capped royalty accounting. In the simulated token flow, three purchases total 0.021 TestEPUSD: 0.003 for the developer and 0.018 for the merchant.
How NEAR fits in: Rust/near-sdk smart contracts implement the settlement mechanisms behind development commitments, purchases, refunds, royalties and withdrawals. The repository includes authentic, finalized NEAR Testnet transactions and a separate Nightly-approved product registration, cross-checked against the explorer receipt and finalized contract state. The live Railway app (https://earnpatch-production.up.railway.app/) lets judges try the workflow: its payments are simulated, its CSV processing is real, and the historical Testnet evidence is independently inspectable.